Skip to content
Rebase LogoRebase

Deployment

What you deploy

Section titled “What you deploy”

A Rebase deployment is two separable pieces: the published runtime image (rebasepro/server) and the bundle rebase build produces from your project. There is no application image to build, and upgrading Rebase is a tag change rather than a rebuild. The same bundle runs on a laptop under Docker Compose, on Rebase Cloud, and on every platform below.

If this is your first deployment, read the deployment guide first: it covers what the server serves, the environment it needs, and how to name the first administrator before the first boot.

Run it for me

Section titled “Run it for me”
  • Rebase Cloud — the same Rebase, operated for you: rebase cloud deploy from your project, a database per project, backups and TLS included.

Run it yourself

Section titled “Run it yourself”
  • Self-hosting — the runtime image plus a Postgres database, on Docker Compose or a plain VPS. Start here.
  • Kubernetes — the official Helm chart, with a migration Job that owns the schema.
  • Splitting into several processes — one bundle as an API, a functions tier and a worker, so a heavy function stops competing with the data API.
  • Running more than one instance — the state each process keeps to itself, and the setting that shares it, before a second replica takes traffic.

Platform guides

Section titled “Platform guides”

Each of these is the same two pieces, wired to that provider’s managed Postgres and container runtime. All of them can be kept inside the EU.