For SaaS companies
Run your APIs, workers and databases in one place
Frontends, APIs, background jobs and their databases in one project — private networking between them, one health view, one invoice.
- web + api · Large × 3Public HTTPS; api reachable privately at http://api
- billing-run · cron jobDaily at 01:30 IST
- app-db · PostgreSQL · Dedicated 16 GBDedicated CPU, 480 connections
- queue · Valkey · durableSurvives restarts, backed up
A typical architecture
Your whole service in one project
Public where it must be, private everywhere else — with health, logs and metrics for every part of it.
Your customersBrowsers and API clients
Public · HTTPS
webLarge × 3 · public HTTPS address
apiLarge × 3 · public API address
Private · inside the project
app-db · PostgreSQL Dedicated 16 GBPrivate · 480 connections
queue · Valkey, durableKept on disk, survives restarts, backed up
sync · job, every 5 minutesCreated from the api app
exports · volume 50 GBAttached to the api app
- Public: one HTTP port per app, HTTPS managed
- Private: reachable only inside the project
Sound familiar?
What hurts as a SaaS grows
Your problem
“Workers and the API drift apart.”
On Drasken Cloud
Create a job from an app: same image, size and environment groups.
Your problem
“A bad release hit every customer.”
On Drasken Cloud
Every deploy is a release; go back to an earlier one from the app’s page.
Your problem
“We can’t tell which service is costing us.”
On Drasken Cloud
Usage and costs by project and by resource, before tax.
Why it fits
Production features without the platform team
- Private networking between apps and jobs inside a project
- Environment groups shared across apps and jobs
- Releases you can go back to; a failed deploy rolls back on its own
- Logs, metrics and health for every app and job, and slow queries for every database
Put your whole service in one project.
Create an account and bring your API, workers and database across one at a time.