Applications

An application is one container plus its configuration: image, run command, environment variables, ports, volumes and resource allocation.

Running and stopped#

An app is either running or stopped. The status you see reflects the container, not your code — a process that has crashed and been restarted, or one that is alive but doing nothing useful, still shows as running.

Stopping an app is safe and reversible. Volumes and configuration are untouched, and starting it again restores it.

Some things stop apps for you:

• Exceeding your account's total disk limit stops every app in the account until total volume size drops back below it.
• Running out of balance stops apps.
• The end of a new account's trial run stops that first app. Add credit and start it again to keep it running. See Balance and payments.

Restarts are normal#

Your process will be restarted regularly — by deploys, by configuration changes, and by crashes. Design for it rather than around it:

• Keep anything that must survive on a volume.
• Make work idempotent, so repeating an interrupted operation is harmless.
• Record what you have finished, not what you are about to start.

If your process exits, it is started again automatically. That means a permanently broken app can restart in a loop indefinitely while still reporting as running — check the logs rather than the status.

Resource allocation#

CPU and RAM come from presets on the app's Performance tab.

• RAM is a hard cap. Exceed it and the process is killed immediately (exit code 137) and restarted.
• CPU is a time budget, not a slower core — you get a share of CPU time per short window, and when it's used up your container is paused until the next one. The symptom is latency spikes rather than uniform slowness.

Changing either recreates the container. See Limits.

Deleting an app#

Deletion requires the app to be stopped first, and it is not something you can undo yourself — recovering a deleted application requires an administrator. Download anything you need from its volumes before deleting.

Apps that stay stopped for a long time may be flagged as stale, with warnings sent before anything happens.

One owner#

An application belongs to a single account. There are no teams, shared access, or read-only seats — collaborate through your repository and deploy from CI so nobody else needs panel access.