DawnrosePay for what runs. Never more than your limit.
Paid plans include usage every month. Past that, usage comes out of credit you bought in advance, and your apps stop at your limit. We don’t charge your card for extra usage.
Start on the trial: $5 of usage with no card, and your apps stop when it runs out.
Your workspace’s usage, credit and plan are under Billing in the dashboard.
Hobby and Pro open when online payments do. Need more than the trial today? Email us and we can add credit to your workspace.
Plans
Trial
Try it on a real project
$5 of usage, once, with Google or GitHub
Start freeYour workspace’s plan is under Billing.
- Included
- $5, once
- After that
- Your apps stop, your data stays
- Spend limit
- The $5 credit
- Holds an app plus Postgres and Redis. Who gets the credit
- Projects
- 2
- Per service
- 1 vCPU, 1 GB
- Replicas per service
- 1
- Volume storage
- 1 GB
- Custom domains
- 1 per service
- Backups to S3
- Not included
- Pull request previews
- Not included
Hobby
Side projects and small apps
Includes $5 of usage every month
Get Hobby- Included each month
- $5
- After that
- Prepaid credit, then your apps stop
- Spend limit
- $20, up to $200
- A small app with Postgres uses about $13 a month: $5 included, the rest from credit.
- Projects
- 20
- Per service
- 8 vCPU, 8 GB
- Replicas per service
- 3
- Volume storage
- 50 GB
- Custom domains
- 2 per service
- Backups to S3
- Up to 20 GB
- Pull request previews
- Included
Pro
Teams and production
Includes $20 of usage every month
Get Pro- Included each month
- $20
- After that
- Prepaid credit, then your apps stop
- Spend limit
- $100, up to $2,000
- That same small app stays inside the $20 included. Up to 100 projects.
- Projects
- 100
- Per service
- 32 vCPU, 32 GB
- Replicas per service
- 20
- Volume storage
- 250 GB
- Custom domains
- 20 per service
- Backups to S3
- Up to 100 GB
- Pull request previews
- Included
On every plan: MCP access for your agent, HTTPS, private networking, templates, the activity log and a limit on spend.
The trial runs up to about 2 GB of memory at once: an app at the default 1 GB, plus Postgres (512 MB) and Redis (256 MB), each with a 0.5 GB volume.
What a month costs.
You pay for what your services use, not for the limits you set. A sleeping service has no running containers, so it uses no CPU or memory.
- $20per vCPU a monthMeasured by the second
- $10per GB of memory a monthMeasured by the second
- $0.15per GB of volume a monthMeasured by the hour, backups included
- $0.05per GB of outbound dataEverything leaving your containers. Traffic between services on the same server isn’t billed
These prices are for EU Central and EU North. In US East usage costs 1.75 times as much, because servers there cost more.
Estimate a month
Average use across the whole workspace, not the limits you set.
- TrialYour $5.00 of credit lasts about 11 days of this. Then your apps stop.
- Hobby$5.00 plan and $8.15 of prepaid credit$13.15
- ProCovered by the $20.00 included$20.00
Try it on the trial: about 11 days of this. Hobby holds it for $13.15 a month once online payments open.
What happens when usage grows.
Your agent can scale things up. It can’t spend past the line you drew.
Included usage
$5 a month on Hobby, $20 on Pro. It comes with the plan.
Prepaid credit
Past the included amount, usage comes out of credit you bought, $5 to $1,000 at a time. With none, your apps stop here.
Your spend limit
$20 on Hobby and $100 on Pro by default. Raise it as far as $200 and $2,000. Warnings go out at 50%, 75% and 90% of the period’s budget.
Your apps stop
Your data stays. Add credit or raise the limit and they come back within minutes.
A worked month on Hobby
A small app and Postgres, averaging 0.25 vCPU and 0.75 GB of memory, with a 1 GB volume and 10 GB of outbound data.
With credit in the account, it runs all month. With none, it stops around day 11, when usage passes $5. Its data stays, and it starts again when you add credit or the next billing period begins.
| CPU, 0.25 vCPU | $5.00 |
|---|---|
| Memory, 0.75 GB | $7.50 |
| Volume, 1 GB | $0.15 |
| Outbound data, 10 GB | $0.50 |
| Usage | $13.15 |
| Covered by the Hobby plan | $5.00 |
| From your prepaid credit | $8.15 |
| You pay for the month | $13.15 |
What each plan allows, side by side.
| Limit | Trial$0Start free | Hobby$5 a monthGet notifiedGet Hobby | Pro$20 a monthGet notifiedGet Pro |
|---|---|---|---|
| Projects and services | |||
| Projects | 2 | 20 | 100 |
| Services per project | 5 | 30 | 100 |
| Services in the workspace | 10 | 200 | 1,000 |
| Environments per project | 2 | 10 | 50 |
| Pull request environments | No | Yes | Yes |
| One service | |||
| vCPU | 1 | 8 | 32 |
| Memory | 1 GB | 8 GB | 32 GB |
| vCPU when none is chosen | 1 | 2 | 2 |
| Memory when none is chosenReserved in full on its server | 1 GB | 2 GB | 4 GB |
| Replicas | 1 | 3 | 20 |
| Disk per replica, outside a volumeVolumes have their own budget | 2 GB | 10 GB | 40 GB |
| Processes per replica | 512 | 2,048 | 4,096 |
| Longest healthcheck wait | 2 min | 10 min | 30 min |
| Longest overlap during a rolloutHow long the old version may keep running next to the new one | 1 min | 2 min | 10 min |
| Longest cron run | 15 min | 1 h | 6 h |
| The whole workspace, at once | |||
| Replicas | 5 | 30 | 200 |
| vCPU | 5 | 48 | 256 |
| Memory | 5 GBAbout 2 GB on the $5 credit | 96 GB | 512 GB |
| Memory you can always reserveMore needs a balance that covers it for 7 days | 2 GB | 4 GB | 8 GB |
| Storage and backups | |||
| Volume storage | 1 GB | 50 GB | 250 GB |
| Encrypted backups to S3On demand or on a schedule | No | Yes | Yes |
| Backup storage | No | 20 GB | 100 GB |
| Variables in one service or environment | 256 KB | 256 KB | 256 KB |
| Variables in the workspace | 2 MB | 32 MB | 128 MB |
| Deployment records, variables and activityWhat the workspace may take in our database | 32 MB | 256 MB | 1 GB |
| Spend | |||
| Usage included | $5, once | $5 a month | $20 a month |
| Default spend limit | The credit | $20 | $100 |
| Highest spend limit | The credit | $200 | $2,000 |
| Team, support and uptime | |||
| Team members | No plan limit | No plan limit | No plan limit |
| Regions | One region for now | One region for now | One region for now |
| Support | |||
| Uptime commitment | No SLA yet | No SLA yet | No SLA yet |
| Builds and deploys | |||
| Deploys per hour | 20 | 120 | 600 |
| Builds at once | 1 | 2 | 4 |
| Build serversA build can take a little longer to start while one is prepared | Shared pool | Your workspace’s own | Your workspace’s own |
| Longest build | 15 min | 30 min | 60 min |
| Build minutes per periodA billing period: the plan’s month, or 30 days on the Trial | 120 | 1,000 | 6,000 |
| Each build gets | 1 vCPU, 2 GB | 2 vCPU, 4 GB | 4 vCPU, 8 GB |
| Build disk | 5 GB | 20 GB | 50 GB |
| Largest image | 3 GB | 10 GB | 25 GB |
| Largest source | 1 GB | 4 GB | 4 GB |
| Largest upload | 100 MB | 500 MB | 500 MB |
| Images kept on one serverBeyond what’s running | 3 | 10 | 30 |
| Image storage on one serverBeyond what’s running. Old rollback targets give way first | 6 GB | 30 GB | 100 GB |
| Images and sources moved per hourThrough our control plane. Counts toward outbound data | 10 GB | 100 GB | 400 GB |
| Deployments kept per serviceOlder finished ones are removed | Newest 100 | Newest 100 | Newest 100 |
| Uploads kept for redeploysThe oldest go first when you need the room | 2 GB | 10 GB | 50 GB |
| Networking | |||
| Generated domains per service | 2 | 5 | 10 |
| Custom domains per service | 1 | 2 | 20 |
| Custom domains in total | 3 | 30 | 300 |
| Wildcard domains | No | Yes | Yes |
| New certificates per week | 5 | 30 | 200 |
| Public TCP ports | 3 | 20 | 100 |
| Environments on one serverEach takes one private network there | 4 | 20 | 100 |
| Traffic out per periodEverything your workspace sends counts here: what leaves your containers, uploads and GitHub sources moved for builds, and sometimes traffic between your own services. The bill counts only data leaving your containers. Past this the workspace is suspended | 50 GB | 2 TB | 20 TB |
| Outbound speed | 5 MB/s per server | 25 MB/s per container | 25 MB/s per container |
| New TCP connections a second | 20 per server | 100 per container500 per server | 100 per container2,000 per server |
| Open connections on one serverAcross all your containers there | 2,000 | 20,000 | 100,000 |
| Mail submission portsPort 25 is closed on every plan | No | No | Yes |
| SSH, RDP and SMB ports, going outPorts 22, 23, 135, 139, 445, 3389 and 5900 | Closed | 2 new connections a second | 2 new connections a second |
| Logs and metrics | |||
| Metrics history | 1 day | 7 days | 30 days |
| Build and deploy logs, kept for | 7 days | 14 days | 30 days |
| Build and deploy logs, total size | 0.5 GB | 5 GB | 20 GB |
| Activity log, kept for | 14 days | 30 days | 90 days |
| Activity log, total size | 4 MB | 16 MB | 64 MB |
Billing questions
Can an agent run up a big bill?
No. The trial stops at its $5 of credit. On a paid plan your apps stop when usage passes what the plan includes and you have no credit left, or at your spend limit: $20 on Hobby and $100 on Pro until you change it. We don’t charge your card for extra usage.
What counts as usage?
CPU and memory by the second, volumes and backups by the hour, and outbound data by the GB. Outbound data is everything leaving your containers, direct connections and WebSockets included. Traffic between services on the same server isn’t billed. A stopped service uses no CPU or memory, but its volume still counts. Builds count too: a build’s CPU and memory are metered the same way while it runs.
Will my app go down if credit runs out?
Yes. Past what the plan includes, with no credit left, the workspace is suspended within a few minutes and its services stop. The same happens at your spend limit, if that comes first. You get warnings at 50%, 75% and 90% of the period’s budget before that. Add credit or raise the limit and it comes back within a few minutes. On a paid plan it also comes back when the next billing period begins. Services start again on their next request. If others took the memory a sleeping service held on its server while you were suspended, that one is stopped instead and says so: deploy it again and it’s placed where there’s room. A service with a volume stays on its server.
What happens to my data while suspended?
It stays. Containers are stopped, not removed, and volumes, databases and backups are kept. Nothing deletes them automatically. Visitors to your domains get an error, and deploys are refused. Stored volumes and backups keep counting as usage at $0.15 per GB a month.
What happens when the trial’s $5 runs out?
Your apps stop and deploys are refused. Your data stays. To carry on, buy credit or pick a plan under Billing in the dashboard. Online payments aren’t open yet, so for now email us and we can add credit to your workspace.
Do I need a card to start?
No, if you sign up with Google or GitHub: the trial includes $5 of usage, once, with no card. GitHub accounts younger than 30 days don’t get the trial credit. It’s also limited each day, so on a very busy day a new account may start without it. Accounts made with an email and password don’t get the trial credit, and need credit or a plan before they can deploy. While online payments are closed, sign up with Google or GitHub: an account made with an email and password can’t deploy yet.
Why can’t I reserve as much memory as my plan allows?
Memory is set aside on a server whether it’s used or not. A workspace can hold what its balance would pay for over 7 days at $10 per GB a month, or a small app’s worth (2 GB on Trial, 4 GB on Hobby, 8 GB on Pro), whichever is more. Redeploying what already runs, or rolling back, works when money is low.
Is there an uptime guarantee?
No SLA yet. We don’t offer one, and we don’t publish an uptime figure or a status page yet.
What doesn’t Dawnrose do yet?
A few things people ask for. There are no GPUs, so it isn’t the place for model training or GPU inference. You sign in with Google, GitHub or an email and password: there’s no SAML or single sign-on for your company’s directory. There’s no SLA yet. And closing an account goes through support@dawnrose.ai, not a button.
Start on the trial. Stop at your limit.
$ claude mcp add --transport http dawnrose \
https://app.dawnrose.ai/mcp \
--header "Authorization: Bearer YOUR_TOKEN"