MaksIT publishes desktop software and also offers it as a service. The installed program stays on the machine of the person who uses it: Windows, Linux, and macOS when a build exists.

A desktop program here is an application you install and run yourself. It is not a browser page that stands in for the program. The installed program does not hold your files on a MaksIT host. Configuration, logs, and data stay where you put them. When a task needs a network, the program uses the servers and systems you already chose.

Windows, Linux, and macOS

Each program states the systems it supports. Windows and Linux are the usual pair. macOS is included when a build exists. The catalog page for a program lists those systems, the current release, and where to get the build.

Builds are published with the release. There is no separate installer hidden behind a request. If a system is not listed, that build is not offered.

Open source, published and maintained

The software is open source. Public code is in the GitHub repository named on the program’s page, under that repository’s license. The license is the one in the repository, not a summary on this page.

Publication means a release you can download and read from the repository. Maintenance means later releases continue on that same repository. Notes for a release live with the release. The catalog page points at the repository and at the place to download or buy the build.

Additional services

Besides publishing it, MaksIT offers the software as a service, free or paid. The service is described on its own terms. The installed program still runs on its own: the service is not required to use it.

What stays on the machine

Mail, schedules, cluster credentials, backups, and logs are examples of data a desktop program may touch. MaksIT does not receive that data as part of running the program, because the program runs locally. If you write for support, that message is ordinary correspondence.

The notice for a specific program is on that program’s page. Privacy notices, where a program has one, are linked from the program page and from the site privacy page.

Where to read a single program

This site is the catalog. Each page says what a program is for, which systems it runs on, and where to download or buy it. This article describes how desktop publication is organized. It does not repeat those pages.

Tools for clusters and systems are described on the cloud-native software page. Programs of both kinds are listed in the catalog.