Pricing

Every price, on one page.

Per service, per month, billed per second. Monitoring, backups, image optimization, and the AI features are part of the price rather than an add-on you discover later.

Start on the free tierMigrating from elsewhere?

Machine-readable pricing: JSON · plain text

Live catalog
Backend-managed pricing
no frontend price constants
Per second
Compute billing
monthly equivalent shown
Regional
Location-aware rates
compare before deployment
Transparent
Unavailable means unavailable
no stale fallback estimates
Compute

Web services

Regional compute pricing is temporarily unavailable. No estimated or stale prices are shown.

Product details →
PlanCPU / memoryCapacityRegionPer month
Live catalog unavailable

Please try again shortly. Darwa does not replace unavailable API prices with estimates.

No cold startsCustom domains + SSLLogs, metrics, health checksPreview environmentsAI diagnosisAuto-rollback on error spike
Migrate to Darwa

Engineers who plan and complete the move with you.

Bring your services across from any provider. A Darwa engineer works alongside your team through cutover — including DNS, queues, application services, and database replication.

Talk to the migration team

Migration scope and any commercial support are confirmed in writing before work begins.

01Architecture reviewWe read your current setup and send back a written plan with the risks named, before anything moves.
02Parallel runYour services run on both platforms against the same traffic until the numbers match.
03Data migrationDatabases replicated with logical replication, storage copied in the background, cutover measured in minutes.
04Cutover with us on the callDNS, queues, and workers switched with an engineer present and a tested rollback path.
05Cost review after 30 daysWe compare your first month against your old invoice and right-size anything oversized.
Billing

The questions that decide it

Where do the prices come from?

The tables above are assembled from Darwa’s protected backend pricing endpoints. If a catalog is unavailable, the page shows an unavailable state instead of a frontend estimate.

How is compute billed?

The live catalog supplies the monthly rate. Eligible compute products are metered per second and the page shows the catalog’s monthly equivalent.

What happens if I use more storage or transfer?

The page displays the current per-unit storage and transfer rates returned by the backend catalog for the selected currency.

What do the worker plans describe?

Worker plans describe workload fit, billing behavior, deployment zone, and the final regional rate.

Are unavailable prices estimated?

No. Missing backend data produces a clear unavailable state. The frontend does not substitute remembered or estimated amounts.

How do longer commitments work?

Where a product offers multiple terms, those terms and their introductory and renewal rates come from that product’s backend catalog.

Get started

Start free. Pay when it is carrying real traffic.

Create an accountTalk to us first