Installed apps

On the Installed Apps page, you can manage your apps. You can perform the following operations on an app:

• Start
• Stop
• Backup
• Update, which will create a backup and then install the latest version of the app.
• Delete, which removes the app and its artifacts; only its backups are preserved.

Public Apps

By default, all apps are private, meaning only authenticated Quollix users can access them. However, you can make an app public, allowing anyone to access it without authentication.

Typical use cases for public apps include:

• Public content without self-registration: Hosting public resources, such as blogs or wikis, whose content is created by users who have been invited by an admin.
• Open communities with self-registration: For servers where anyone can register and participate without needing admin approval.
• Client integration: Some desktop or mobile clients cannot connect to private Quollix apps since they cannot pass Quollix’s authentication layer. Making the app public removes this barrier.

Miscellaneous

• It is not possible to start two apps with the same name.
• Apps have a state that can be either Available or Uninitialized. Currently, the implementation is simple: once an app has been started, it immediately becomes Available. In the background, however, each app may still need time to download images and launch containers. In practice, it can therefore take a while before the app is actually ready.

Special Case: quollix / postgres

Quollix uses a Postgres database called postgres to store its data. It is technically convenient to treat postgres as an app because it behaves almost the same way operationally. This is why quollix / postgres is listed on the Installed Apps page by default. Since the database must always be running and available, your operations on the database app are limited to creating backups. Conversely, restoring backups on the Backups page restores Quollix data such as users, settings, and installed app metadata.

Access Policy

Making an app accessible to more users, e.g. publicly available, increases the risk of exposing potential vulnerabilities. Only grant app access only to users who genuinely need it.

Downloading and uploading apps

You can manually download and upload apps locally without relying on the official App Store. Backups will still be handled automatically. However, this approach increases your maintenance responsibility because updates must be performed manually. Enabling automatic updates via the app store later for an uploaded app may lead to incompatibilities if the configurations differ.

If the uploaded app does not exist yet, a new app will be created from the file. If the app already exists, the existing app will be updated. If enabled, a backup may be created before the update.