Add-ons

Add-ons

Add-ons are managed data services - Postgres and Redis - that you attach to a project. They run on the project's own isolated network, and their connection details are injected into your app as environment variables, so your code just reads a connection string and connects.

Adding a database or cache

  1. Open a project and create a Postgres or Redis add-on.
  2. orkestr provisions the service on the project's private network.
  3. Connection variables are injected into the app's environment on the next deploy.
  4. Redeploy (or wait for the next deploy) so your app picks up the new variables.

How connection details reach your app

When you attach an add-on, orkestr sets the relevant connection variables (for example a DATABASE_URL for Postgres or a Redis URL) on the project's environment. Read them like any other environment variable - no hardcoded hosts, and nothing to copy by hand.

Isolation and sizing

  • Each add-on runs on the project's isolated network and is not reachable by other tenants or other projects.
  • CPU, memory, and storage are sized by plan.
  • On free and Pro, idle add-ons can sleep to save resources and wake on demand; storage is enforced per plan.
  • A job running against the project can reach the same add-on, which is what makes migrations against real data straightforward.

Backups

Paid plans support manual backups of add-on data with retention, subject to per-day limits by tier, and you can toggle automatic backups. Backups let you snapshot before a risky migration and restore if needed.

  • Manual backups on demand (per-day limit depends on plan).
  • Automatic backups you can switch on per add-on.
  • Retention window scales with plan.
Plan limits
Starter: 1 add-on. Pro: 2. Team: 5. Sizing per tier is on the pricing page.

FAQ

Which databases are available?

Managed Postgres and Redis today.

Can two projects share one add-on?

Add-ons are scoped to a project and its private network. To share data between projects, connect them over the network with credentials, or use a project group.

Why can't my app connect right after adding an add-on?

Connection variables are injected at deploy time. Trigger a redeploy so the app picks them up.

How do I back up before a migration?

Take a manual backup of the add-on, then run your migration as a job; restore from the backup if anything goes wrong.