▒░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0%Configuring HTTPS, health checks and scaling…
✓ Your service is livehttps://api.yourdomain.com ↗
builder@mac ~ %
From commit to production, handled.
Deploy, inspect, and operate your backend from one dashboard. The right control is ready when the service needs it.
orders-apiProduction Live
mainf4c2a91 · checkout webhooks
Source connectedGitHub revision receivedPassed
Image builtNode.js · 31 secondsPassed
Health checkedGET /health · 200 OKHealthy
Every release, visible from commit to healthy.
Darwa keeps the source revision, build progress, health checks, and live endpoint together. You always know what is running, why it changed, and which release is healthy.
Trace every release back to its source commit
Route traffic after checks pass
Restore the last healthy release if needed
Runtime logsStreaming
INFOHealth check passed on /health
INFOConnection pool ready
WARNCold start completed in 814ms
INFOListening on 0.0.0.0:8080
INFOEnvironment loaded · production
The exact output you need, while it happens.
Stream build and runtime logs from the dashboard. Filter noisy output, inspect a specific release, and copy the exact evidence you need without ever leaving the service.
Requests, latency, errors, CPU, and memory stay attached to the service. Spot every change, compare it to a release, and scale with the full operational context in view.
Track traffic, latency, and errors in one view
Watch CPU and memory side by side
Connect metric changes back to each release
Environment variablesProduction
DATABASE_URL•••••••••••• Encrypted
REDIS_URL•••••••••••• Encrypted
API_SECRET•••••••••••• Encrypted
SENTRY_DSN•••••••••••• Encrypted
Production configuration without secrets in Git.
Add encrypted environment variables in the dashboard and inject them only when the service runs. Values remain masked after they are saved, shared, or updated by your team.
Encrypt configuration values securely at rest
Keep saved secrets masked by default
Update configuration without changing code
Production stays protected.You stay in control.
Your secrets stay protected.
Credentials stay encrypted, masked after save, and injected only while your service runs.
Variables & secretsProduction
DATABASE_URL•••••••••••• Encrypted
API_SECRET•••••••••••• Encrypted
REDIS_URL•••••••••••• Encrypted
Your releases stay healthy.
Health checks verify every release before traffic and preserve the last healthy version for recovery.
Health checks Healthy
All checks passedLast checked 18 seconds ago
GET /health200 OK
Response time124 ms
Your alerts stay actionable.
Monitoring watches health and resource pressure, then notifies your team with useful context.
Alerts2 rules active
Error rateAbove 2% for 5 minutesNotify team
CPU pressureAbove 85% for 10 minutesNotify team
Clear pricing by region.No estimates. No surprises.
Yes. Every service includes a Darwa hostname, managed TLS, deployment health checks, logs, and service monitoring.
Can I deploy with the Darwa CLI?
Yes. Link a local project to an existing service once, then use the CLI for quick releases and status checks.
Can a service scale with traffic?
Yes. Choose the capacity that fits today and adjust it as demand changes. Supported plans can scale without changing your application code.
Can I connect a custom domain?
Yes. Use the included Darwa hostname or connect your own domain with managed HTTPS and automatic TLS handling.
How are environment variables protected?
Values are encrypted, masked in the dashboard, kept out of your repository, and injected only when the service deploys.
Can services communicate privately?
Yes. Private services provide internal endpoints for traffic between services in your workspace without exposing them publicly.
Which regions can I deploy to?
Available regions appear in the live region selector. Pricing and capacity are shown for the region you choose.
How does Web Service billing work?
Pricing depends on the selected region and capacity. The pricing catalog shows the current estimate before you create the service.
What happens when a deployment fails?
Darwa runs health checks before routing traffic. An unhealthy release does not replace the healthy version, and release history remains available for recovery.