Hosted apps

Click Add app at the top of the project's Services tab and choose what to deploy. A dialog asks for the app's name (2 to 20 lowercase letters, digits and dashes) and its details, shows the build and start as they happen, and ends with the app's address. A project can hold several apps, up to your plan's limit; every deployed app gets a card under Deployed services, and Manage opens its page:

• Images are pulled without credentials, so they must be public. Registries on localhost, IP addresses and internal host names are refused.
• Environment variables are entered as KEY=value lines and stored encrypted. PORT is set to the app's port unless you set it yourself.
• Each app gets a 1 GB volume, mounted at /data (or the template's own folder). It is kept across restarts and redeploys, and deleted with the app.
• Redeploy builds a GitHub app again from the latest commit of its branch. Builds stop after 10 minutes. Deploying on every push, custom domains and autoscaling are not available yet.
• An app's page has Overview, Logs, Environment and Settings tabs: restart, stop or redeploy, read the logs, edit variables, change the source and size, or delete it.

Every app is served at https://<name>-<project slug>.<apps domain>, shown on its card. HTTPS certificates are issued automatically. Requests reach the app's port through the platform's proxy; nothing else on the container is reachable from the internet.

curl -i https://web-my-shop-a1b2c3.apps.example.com/

Free projects can run 2 apps, Pro projects 5. Compute is charged only for hours the app runs: an app that is asleep, stopped or paused costs nothing. The volume is included, up to 1 GB on Free and 5 GB on Pro.

An app with no requests for an hour goes to sleep: its container stops and its data stays. The next request wakes it. The visitor sees a short “Waking up” page that reloads by itself, usually for a few seconds, and then the app.

• On Pro, switch on Always on for apps that must answer at once or run work in the background (n8n schedules, queues, bots). Always-on apps never sleep.
• Only requests through the app's address keep it awake. Work it does on its own, such as polling, does not.
• The platform runs a limited number of apps at once. When it is full, the app that has been idle the longest goes to sleep to make room; if none can, the waking page asks the visitor to try again shortly.
• Stop keeps an app down until you start it again; visitors see a “Stopped” page meanwhile.

• Memory and CPU are capped at the app's size, with no swap. An app that needs more memory is stopped by the system and restarted.
• At most 256 processes per app, no privileged mode, and all Linux capabilities dropped except the few images need to switch to their own user.
• Outgoing email ports (25, 465, 587) are blocked. Send email through the Email service or an email API.
• Docker keeps up to 10 MB of each app's logs.
• When credits run out, apps are paused like databases and Redis. After credits are added, always-on apps start again and the others wake on their next request.