Quickstart

From a repository to a running app on its own URL — the whole loop, in one sitting.

1. 1

   Connect GitHub

   In Integrations, install the GitHub App for the repositories you want to deploy from. A public repository deploys with no installation at all — which is also why its commit list can be absent later, on Versions.

2. 2

   Point at a repository

   Pick a repository and a branch. Detection reads it and fills in the install, build, and start commands, along with the port.

   When detection can't read the repository, it shows nothing rather than an error, and it never blocks Deploy — fill the fields in yourself and continue.
3. 3

   Add a database, if it needs one

   One tick adds a Postgres database inside the app. Most frameworks read it from DATABASE_URL; Laravel reads it from six separate DB_* variables instead, and detection sets whichever one your framework expects. See Database.

4. 4

   Choose who can open it

   Private is only you; everyone else hits a sign-in wall. Workspace adds everyone in your workspace plus anyone you invite by email. Anyone with the link needs no sign-in — and that URL is guessable from the app's name, so it is the one level that is not a privacy setting. Details on Access.

5. 5

   Deploy

   The app is queued, then reachable at its own hostname.

   The hostname is allocated, not derived from the name you typed — if it's taken, you get a suffix like finances-a7bd. Read the URL off the screen once the app is created rather than predicting it.

Templates

A template pre-fills the create form with a working service — everything stays editable before you deploy. The current templates are n8n, Uptime Kuma, and Whoami.

Next

For how the service, its ports, and the database fit together inside one app, see How apps work.