Knowledge base

Servers hold projects, projects hold services. Here is how the pieces fit.

Pick a size and a region; the server is ready to deploy to in a few minutes.

Connect a repository, pick a branch, review, and deploy.

Go, Node.js, Python, Java, PHP, WordPress, static sites, any Dockerfile, and two databases.

Deploy a new commit, deploy on every push, and go back to an earlier revision.

Stop a service without losing it, and bring it back with the same settings.

Read what your app prints, and open a shell inside it.

Add, edit and import variables, keep secrets hidden, and decrypt encrypted files.

Use the default address, add your own domain, and turn on HTTPS.

Keep files across deploys with volumes, and reach them over SFTP.

Run more copies, cap resources, scale with load, and protect your app.

Add PostgreSQL or MySQL to a project and connect your apps to it.

Browse tables and run SQL on any of your databases, in the browser.

Publish a database to connect to it from your computer or another host.

Turn on dashboards for a server to see CPU, memory and storage over time.

Where to look, the usual causes, and how to get back to a working version.

Open a support ticket from the console.