As soon as your project contains server-bound components (backend, web app, homepage), it needs a server. The platform sets it up automatically – Docker, reverse proxy, and deploy access included – and then uses it for your projects’ deployments.
The three ways to a server
| Way | You need | Good when |
|---|---|---|
| Your own server (SSH) | A Linux server, SSH access | You already have a server or want full control |
| Cloud servers with your account | A Hetzner or Hostinger account with an API token | You want your own cloud servers; the platform handles creation and setup |
| Managed server | Just an active subscription | We set up the server for you – no cloud account of your own |
You’ll find all three under Servers → add server in the platform. Servers are managed at organization level (administrators only) and selected when creating or editing a project.
When do you need a server?
- Backends, web apps, and homepages/websites run on a server.
- Mobile apps without their own backend don’t need a server.
- Databases and services that belong to the backend run on the same server.
After the setup
Once the server is registered and assigned to a project, the platform deploys automatically: dev on every merge, prod with one click – see Git workflow & deployment. For your own domains, continue with the domain setup.