Skip to contentNewLaunching soon on Product Hunt (opens in a new tab)
DeployAll sections

Deploy

Deploy is where you publish your backend. Publishing runs readiness checks first, then records the backend as a numbered version and marks the project live. On Pro and higher you can roll back to an earlier published version.

In the console: Operate › DeployUpdated October 12, 2026

Walkthrough coming soonA 20-second tour of Deploy will play here.

Why you need it

Deploy is the checkpoint between building and calling something finished. Readiness checks catch problems before you sign off, such as a table without row-level security, a webhook without a signing secret, or a behaviour check that failed. Every publish is kept as a version, so you have a history of what went live and when, and a way back to an earlier one.

For example

  • Before launch, you open Deploy and clear the blockers the readiness check found.
  • You publish a new version after adding payments.
  • A published version caused a problem, so you roll back to the one before it.
  • Your agent asks to publish. The request waits for your approval, then runs exactly as asked.

How it works

  1. Readiness checks run first

    A blocker stops the publish and a warning does not. A refused publish names its blockers in the refusal.

  2. Publish

    The first publish takes the project from private to live as v1. Each later publish adds the next version.

  3. Versions are kept

    The Deploy page lists every published version, which one is current, and which ones you can roll back to.

  4. Roll back if you need to

    Pick an earlier version to make it current again. If a publish fails, the version before it stays current.

Try it

Once your coding agent is connected, ask it:

Ask your agent
Is my backend ready to publish? List anything that is blocking it.

Good to know

  • Your API answers before you publish, so you can build and test against it straight away. Publishing records a version; it does not switch the API on.
  • Deploy publishes your backend. Your frontend is hosted wherever you choose and calls the API.
  • When your agent asks to publish or roll back, the request waits for your approval in the console and then runs exactly as asked.
  • Rollback is included in Pro and higher. See Pricing.