One-click apps

One-click apps are ready-made apps you install in a project without writing code: a blog, an online shop, team chat, accounts and stock, reports, or a status page. Each install is your own copy, with its own database when it needs one, a free address with HTTPS at once, the project's backups, and an admin account made with your email. Updates are offered for you, with a backup taken first.

What's in the catalog

The app catalogue lists every app, with a guide for each: WordPress and its shop, school and events versions, Ghost, Nextcloud, Mattermost, Odoo, Metabase, Umami, Uptime Kuma, Gitea and a Laravel starter. Search it by name or by what you need ("blog", "shop", "chat"), or narrow it by category. Nothing matches? Choose Suggest an app: it reaches our team as a ticket.

Each card shows the limits the app runs well with, about what that costs a month, what it makes for you (like "+ MySQL database") and its licence. Limits are ceilings, not sizes: the app pays only for the memory and processor it really uses, counted every minute, and you can change them on the install page or later like any app's. See limits.

We host these apps; their makers make them, and each keeps its own licence. Every app comes from its makers' official release at an exact version, checked for known security problems and tried on a real server before our team publishes it. A new version reaches the catalogue no sooner than 7 days after its makers release it; a security fix as soon as it passes its checks. Each runs in its own sandbox, like any app of yours.

Install one

Asha wants Odoo for her shop's stock, in her project duka.

1. Open the project. On its Overview, under Add a service, choose From the catalog.

2. Type "stock" in the search, or choose Business, and pick Odoo.

3. Give it an App name, like books: up to 40 lowercase letters, numbers and dashes.

4. Type the Admin email you'll log in with, and answer the app's own questions if it has any.

5. Check its limits, the database it makes (books-db, made and connected by itself) and the monthly estimate, then choose Install.

A strong password is shown once: 20 random characters. Copy it, then choose I've saved it. You can change it in the app later. We keep it sealed only until the admin is made, then delete it.

The app's card shows each step: Starting its database, Starting the app, Making its admin, then Ready. Until its admin is made, nobody but you can reach it, so nobody can take over its first-run page. When it's ready, choose Open its admin page and log in with your email.

The estimate comes from what other installs of the same app really use. Until there are enough of them, it comes from similar apps in your project's location.

After it's installed

A one-click app is a normal app of your project. Its database is one of your project's databases, attached with its managed variables. Change its limits, add your own domain, read its logs, restore it from a backup or delete it, as with any app. See add a domain and backups.

A first backup of the project is taken as soon as the app is ready, and the project's regular backups (5 days a week) include it from then on.

Updates

When a newer, checked version of the same line is out, like a newer Odoo 19, the app's card shows Update to that version.

• An update backs up the project first, then deploys the new version. If it doesn't start, the version before keeps serving, and you're told.

• Security updates install by themselves, after the same backup. Switch off Install security updates by themselves on the app's card if you'd rather choose the moment.

• Going back: for 7 days after an update, Go back to the version before. The app's data stays as it is now; to undo what the update changed in it, restore the backup made before it.

• A known security hole: if the version you run is found to have one after it was published, you get one email and a message under the bell, and the card shows Update to the version that fixes it.

• A new line, like Odoo 19 to Odoo 20, is never an update: it changes your data in ways only you can decide, so it's a new install.

WordPress with WooCommerce is a WordPress site: WordPress keeps itself and its plugins up to date, as on any host. See WordPress.

End of support

When a version stops getting security fixes from its makers, we set its last day. Everyone using it is told 30 days before, and the card says when it stops getting updates. From that day it isn't offered for new installs or updates. Apps on it keep running, with no more security fixes, so plan a new install on a newer line.