Apps and jobs Coming soon
Run your app next to your databases
Deploy a container image as an always-on HTTPS service in the same region as its databases, with releases, rollback, scale to zero and cron jobs. Sizes from $5 a month, billed by the hour per replica. Apps are being built now.
Apps, jobs and sandboxes are in development. Everything on this page describes how they work at launch. Coming soon
How it works
Apps and jobs, step by step
- Step 01
Point at an image
Any image in a registry you authorise; tags are pinned to their digest when you deploy.
- Step 02
Wire up the database
Environment variables can reference an instance's credentials; they are resolved in the cell and never copied into the control plane.
- Step 03
Deploy and roll back
Every deploy is a release. Roll back to an earlier one in seconds.
- Step 04
Scale or sleep
Set minimum and maximum replicas, autoscale on CPU, or scale to zero when idle on paid plans.
What you get
-
Your container, our HTTPS
Each app gets its own hostname with a managed certificate, and custom domains.
Coming soon -
Private path to your databases
Apps reach their project's instances inside the cell, without leaving the network or paying egress.
Coming soon -
Releases and rollback
Every deploy and restart is recorded; any earlier release can be restored.
Coming soon -
One-off and cron jobs
Run migrations or nightly tasks in the app's image with its environment.
Coming soon -
Hourly sizes
c0 (0.25 vCPU, 512 MiB, ≈ $5/month), c1 (0.5 vCPU, 1 GiB, ≈ $10/month), c2 (1 vCPU, 2 GiB, ≈ $20/month), c3 (2 vCPU, 4 GiB, ≈ $40/month), billed per replica-hour.
Coming soon -
Sandboxes for agent code
Short-lived isolated runtimes for untrusted code such as AI agents, billed per second (x1 $0.05/hour, x2 $0.1/hour, x4 $0.2/hour).
Coming soon
Live today and coming next
Every part of this service and where it stands. The list changes as each piece ships, and the changelog announces it.
- Always-on apps from your container image Coming soon
- One-off and cron jobs Coming soon
Live: available on the platform today. Coming soon: being built now; prices and plan limits are already published. See every service on the platform overview.
Try it
How a deploy will look with the CLI.
zb apps create web --image ghcr.io/acme/web:1.4.2 --size c1 \
--env-instance DATABASE_URL=orders-db --wait
zb apps jobs create web nightly --schedule "0 3 * * *" -- node cleanup.js
zb apps rollback webPlan availability
Generated from the same plan catalogue that billing and the API use.
- Not available
Free
$0 /moApps start on Solo
- Coming soon
Solo
$25 /mo3 apps, 100 build minutes
- Coming soon
Team
$599 /mo20 apps, 1,000 build minutes
- Coming soon
Enterprise
CustomUnlimited apps; usage set in your contract
Compute is billed per replica-hour at the size price; build minutes above the allowance are $0.01 per minute. No customer code runs on the free tier.
Questions
When can I use them?
Apps, jobs and sandboxes are being built now. This page and the docs switch to Live when they ship, and the changelog announces it.
Why not on the free tier?
Customer code runs only on paid plans, on node pools separate from databases, which keeps the free tier safe from abuse.
Related features
- Coming soon
Functions
TypeScript functions at your project endpoint, triggered by HTTP, cron, queues or database changes.
Learn more about Functions - Live
Agent servers
Cloud dev machines for you and your coding agents, from $12 a month, with no compute charge while stopped.
Learn more about Agent servers - Live
Data API
REST and GraphQL over your Postgres tables, and SQL over HTTPS for every engine.
Learn more about Data API
Start today
Create your first database
A free instance, no card. Upgrade when you outgrow it; nothing converts silently.