Use cases · APIs and backend services
Ship the APIDo not stand up another stack
The API runs next to the app. You keep building. We keep it up.
request
GET /checkout
response
200 · 42ms
Before
Staging and production stop matching.
Ports, Redis, and keys drift until a request fails only in production.
staging
PORT3000
REDIS_URIredis://local
STRIPEsk_test
production
PORT8080
REDIS_URImissing
STRIPEsk_live
Process
The API, the worker, and cron. Same production.
Pick the process type. Variables, logs, and deploys stay attached.
Observe
Logs stay on the service.
Follow a request id without SSH or a second dashboard.
runtime logs
8f2cGET /checkout 200 42ms
8f2ccharge.created
91abGET /health 200 4ms
3ee1POST /webhooks 202 18ms
Recover
Release history is the rollback.
Previous builds stay on the service. Roll back without hunting a script.
api
Ship the API.Keep building.
GET /checkout → 200
Use dFlow when the backend the product depends on should follow the same release path.