Easily deploy your project.
Run your web app or API with its database, workers, and storage, and deploy every change through one repeatable workflow.
project: purchase-requestsprocesses: web: port: 8080 worker: command: ["node", "worker.js"]A customer portal with its database and a worker.
A booking app, a webhook receiver, an integration worker, or an early SaaS project.
Step 1
Deploy the app and its API
From code, Git, or a container image.
Step 2
Connect its resources
Postgres, Valkey, volumes, and a background worker.
Step 3
Ship the second release
Follow the logs, and roll back if it needs to be reversed.
What a project can use
Web and API processes
With or without a browser interface.
Workers
Background processing as its own process.
PostgreSQL
For the data your app keeps.
Valkey
For caching and queues.
Volumes
Persistent storage for files.
Logs and releases
See what runs, and every release that got there.
Practical questions
Does my project need a web interface?
No. An API or a background worker is a project of its own.
Can I run a SaaS on it?
Yes, as an application. Subscriptions, tenant isolation inside your app, and customer authorization are your app's to provide.
Is there a scheduler for jobs?
Run your processing as a worker. Check the documentation for the workflows that are supported today.
Try it with a project you are already developing.
Deploy it, connect what it needs, and publish the next version.