Marketplace apps

Install, update and uninstall apps we publish, on a new server or one you already have.

Built, not open to the public yet

This feature is built and has been tested against simulated hosts and a test database. It has not yet been proven on real hardware, and nothing here can be ordered today.

Not there yet

Not yet run on real servers. The app recipes are not signed for release yet.
Only apps we publish; customers cannot upload their own.

What an app is

An app is a recipe we write and sign: a setup script that runs on your server, with a few choices you make first (a domain, an email address, a port). Only apps we publish are offered. There is no upload of your own recipes. The first apps are Docker, nginx, WordPress, WireGuard and Minecraft. No other count or list is promised.

Install on a new server

Choose an app on the Marketplace page, then a plan and region. The recipe runs the first time the server boots. The page shows progress from the server's console: installing, ready or failed.

Install on a server you already have

Plan. The panel checks everything first and shows the result: the server is running and not in rescue, it runs Debian or Ubuntu on x86_64 or aarch64, it has the disk and memory the app needs, nothing else is installing, and ports are free. It also advises taking a snapshot first.
Confirm. You acknowledge that the server will restart. A recent password check and a verified email are needed. One install runs at a time per server.
Run. The host verifies the recipe's signature, hands the server the setup script and restarts it. The server's console prints progress, and the Apps tab on the server page moves from pending to installing to ready or failed.

Passwords the app needs are generated on the server's host and shown to you once. Copy them when they are shown. Be aware that a generated password is not private to the control plane: it is written into the setup script, so it sits on the host in the seed disk image until the next seed replaces it, and in the host's own record until the panel confirms it holds the password. It is also on your server, in the setup script and cloud-init's data. The recipes delete the script when they finish. Change a generated password after you first sign in if that matters to you. Ejecting the seed after the first progress line is planned, not built. The progress lines come from your own server, so treat them as a hint, not proof.

Update

When we publish a newer version a recipe can update to, the Apps tab offers Update with notes on what changes. It follows the same plan, confirm and run steps.

Uninstall

Uninstall shows what is removed in every case and, if the app keeps data, what is removed only if you choose. The default keeps your data. Removing data needs a second confirmation. The uninstall script removes only what the install created.

Limits

Every change is a script run by restarting the server, not a transaction. If one fails part way, the server may be left half changed. The plan says so before you confirm, and a snapshot lets you go back.
There is no agent inside your server, so we cannot see what the app does after it is installed.
We do not monitor or patch an app after it is installed. Keeping it up to date is your job.