As soon as a project contains a backend, a web app, or a homepage, it needs a server; databases and other services of a backend run there as well. Mobile apps without a backend of their own do not need a server.
The platform installs Docker, Traefik as the reverse proxy, a firewall, and HTTPS, and it creates the access the pipeline uses to deploy. The four options differ in how the platform gets onto the server.
The four ways to get a server
| Option | Requirement | Good fit when |
|---|---|---|
| Your own server (SSH) | A Linux server with SSH access | You already have a server or want to decide yourself where it runs |
| Cloud servers | A Hetzner or Hostinger account with an API token | You want cloud servers of your own without setting them up yourself |
| Managed server | An active platform subscription | You do not want an account with a cloud provider |
| Webspace (FTP/SFTP) | FTP or SFTP access to an existing webspace | The project consists of homepages only |
The webspace works without Docker because Hugo and Astro produce nothing but static files; as soon as a project contains an app or a backend, this option is no longer offered.
Creating a server and assigning it to a project
Open Servers in the sidebar and click Add server. There you choose the type and enter the details described on the respective subpage. Servers belong to the organization, and only administrators create or edit them.
When you create or edit a project, you choose the server it should run on; you can change this assignment later.
Once the server is assigned, the pipeline deploys on every change to main, as described under Git workflow and deployment. To make the project reachable under a name of your own, continue with the domain.