Skip to content

Hosting & deployment

The publish flow

What happens when you click Publish, end-to-end.

4 min read

Step by step

  1. SnapshotYour workspace is git-tagged at this moment as a release.
  2. BuildA Docker image is built from the snapshot. Cached layers make this fast — typically under 30s after the first build.
  3. PushThe image is pushed to the registry.
  4. RunA container starts on a runtime host with your real credentials injected as env vars.
  5. Health checkVibe waits for the container to respond on /health before routing traffic.
  6. RouteCaddy's host map is updated. Your subdomain (and any custom domain) now point at the new container.

Deploy messages

The publish dialog has a free-form message field. These messages show up in the Deploys tab and are useful when you need to track down which release caused a regression.

Where publishing sits in the bigger picture

Publishing moves one layer of your app — the interface — onto a host and gives it an address. It never touches the layer below: your tables, workflows and security rules are already live, and a publish neither migrates nor re-secures them.

One release can go to more than one host. All of them read the same backend.
How everything connectsThe whole stack drawn out — backend, interfaces, hosting, domains and the AI layer.
Ready to build

Skip the docs.
Just describe it.

Tadabase AI builds it, hosts it and keeps it running. Real backend, real domain, real app.

Start Building