Changelog. What changed, newest first.

A new app shows its next step in the header: every step at a glance, one unfolded at a time. You can hide the guide, and show it again from the settings of the app.

When an app keeps crashing, the team gets a notification, and the overview shows what each replica is doing.

Commands that run once for every deployment, before the new version takes traffic. The place for database migrations. If one fails, the running app is not changed. See Deploy commands.

The documentation is online: a quick start, an Express guide, a page for every setting, and a prompt that checks your app with your AI coding assistant before you deploy.

Set an install command when the automatic one does not fit, and put several build commands on lines of their own. See Build settings.

When the packages of an app run scheduled jobs or queue workers, the dashboard says so: they do not run while the app sleeps.

The sign-in page links the terms of service and the privacy policy. A new account keeps the time it accepted them, and which version.

An app takes up to 200 variables, 32 KB for one value and 256 KB for all of them together. Names that start with PLATFORM_ are kept for the platform. See Environment variables.

Every variable has a Build switch, off until you turn it on. With it on, the variable is set while the app is installed and built: for a token that a private package needs, or a value the build puts into the built files. See Environment variables.

A sleeping app can keep its memory, so it answers the next request without starting again. See Sleep and wake.

Projects that use Yarn 2 or newer now build.

The activity page lists what members changed, and names the setting that changed. It is for the owner and the admins. Alerts such as a crash arrive as notifications.

The log of a deployment is kept for 90 days after the deployment ended.

With a build command, everything in package.json is installed for the build, and the packages in devDependencies are removed after it.

A deployment that is running while the platform itself is updated is picked up again and finishes. Deploy commands that were still running are waited for, not run a second time.

When you create an app, the Node version, the package manager and the build and start commands are read from your code. Detect from repository on the settings page reads them again.

Docs in the sidebar opens the documentation, and Support opens the contact page. The variables of an app, its build settings, its deploy commands and its custom domains each link the page that explains them.

The build log and the runtime log say what happened in plain words.

A new app starts with Keep one replica always on switched on. Switch it off to let the app sleep when it is idle.

Pushes that arrive while a deployment is still waiting join it, so the newest code is built once.

A browser stays signed in for 30 days after a sign-in, instead of 400. After that you sign in again with a code.

Every answer of the dashboard tells the browser to come back over HTTPS only and not to show the page inside a frame on another site. The cookies that sign you in are sent over HTTPS only. See the security page.

Before an app is stopped, it gets the signal SIGTERM and 30 seconds to finish the requests that are open.

When you change on GitHub which repositories the platform may read, the dashboard reads the list again on your way back. Before, it showed an error.

After the branch of an app is changed, a redeploy builds the newest commit of the new branch. Before, it built the commit that was live once more.

A sign-in is remembered. Before, you were asked for a new code once 120 minutes had passed without activity.

The repository is downloaded inside the build environment of the app itself.

A deployment that is running shows how long it has been going.

Each app keeps the packages it downloaded in a cache of its own between builds.

The app menu says what Restart and Pause do before you choose one.

Cancelling a deployment stops its build where it is.

A deployment whose work stopped without a result is ended within minutes, and the app is free for the next one.

Three plans, a trial with usage credit and no card, and usage counted per second. The billing page shows what each app used in the current cycle and every line of each statement. See Pricing.

Owners and admins reveal the value of a variable one at a time, and each reveal is noted in the activity.

If the GitHub connection is removed, the apps stay. Reconnecting brings them back.

The sign-in code has six boxes and is sent as soon as all six digits are in.

While an app sleeps, no compute is counted.

Connect a GitHub repository, and every push to your branch builds the app and puts it online. Custom domains with automatic HTTPS, a primary domain that the others redirect to, and a platform URL that can be switched off. Instance sizes and regions, live runtime logs, and environment variables that can be edited one by one or as .env text.