Getting started

This short guide will guide you through deploying an app.

After creating your account, you will need to add a credit card. Your usage is prorated to the day so you will only be billed for the time used.

Then, click the "Deploy an app" button. Create an app and give it a name.

A unique subdomain will be assigned to your app. This subdomain cannot be changed without deleting and recreating your app.

Source code

Backery works in a close to plug-and-play manner. You shouldn't have to do extensive configuration to deploy your app.

There are, however a few language-specific requirements, like the package.json file for Node or composer.json for PHP. Find more informations on your language on the menu on your left.

Except if your app is a Node.js app (in case Backery will execute npm start), you will need a Procfile file at the root of your app, which defines how to start your app.

Example of a Procfile

web: node run forever


Once your app is created, you can now add a database for storage in the database tab. The database will be accessible via an URI stored in an environment variable given to you after creation. Supported databases are MongoDB, Redis, Postgres, MySQL, MariaDB, CouchDB.

After adding a database, regular backups are automatically scheduled (with the frequency depending on your plan). You can then easily roll them back to a previous version simply by the click of a button.


You have two options for uploading your source code and deploying it:

To use deployments via Git, you need to add the supplied Git repository URL to your repo like this:

git remote add backery<application id>

Commit files

git add .
git commit -m 'initial commit'

Then push to the remote

git push backery master

Pushing to the Git repo will trigger the build process after a few seconds.

However, uploading an archive through the dashboard will not trigger a deployment. After upload, click on the "Deploy" button of your release to trigger the build.

You can then follow the build process in the "Logs" section.


On your local machine, your app’s web server can listen on any open port.

On Backery it must listen on a specific port indicated by the PORT environment variable.

Make sure your app is listening on the port number specified by PORT.

Access your app

If you have followed all the previous steps and the logs don't indicate any error with your application or the build process, your app should now be ready and accessible on the unique URL assigned.

You might have to wait a few hours for DNS propagation and try again. If you still can't access your app, we are right here to help you. Contact us via the livechat or at .

You might now want to link a custom domain.