Dawnrose

Product Safety and control

You stay in charge.

An agent can’t run up a surprise bill: your apps stop at your limit, and we don’t charge your card for extra usage. It works in the open, and only as far as you let it.

shopActivity, spend and tokens
  1. Claude Code deployed web from a41c9e2
  2. Claude Code set DATABASE_URL on worker
  3. Cursor raised web memory to 2 GB
  4. VYou rolled back api to deployment #41
  5. VYou sealed STRIPE_KEY on api
  6. Claude Code added shop.example.com to web

Spend this period

$7.40 of your $50 limit

Tokens

  • Claude CodeAgent token, this workspaceRevoke
  • Deploy from CIProject token, shop onlyRevoke

delete_service webClaude CodeRefused

It’s marked destructive, so the agent’s client asks you first, and without confirm: true the server says no.

Sample data

What your agent can do, and what only you can.

An agent token works within its owner’s role, and the server keeps a few things for a person signed in to the dashboard.

ActionYour agent, with a tokenYou, signed in
Deploy, roll back and scaleYesYes
Read logs, metrics and the activity logYesYes
Delete a service, volume or backupAfter its client asks you, with confirm: trueYes
Raise the spend limitNoYes, as owner
Buy credit or change the planNoYes
Invite people or change rolesNoYes
Create personal tokensNoYes

Guardrails that don’t get in the way.

  • Spend limits on every plan

    When usage reaches your limit, workloads stop instead of the bill growing.

    $7.40 of your $50 limit this period

    Past what the plan includes, usage comes out of credit you bought. At the limit, workloads stop.

  • Tokens you control

    Each agent token reaches one workspace. Revoke it in a click.

    • Claude CodeAgent token, this workspaceRevoke
    • CursorAgent token, this workspaceRevoke
    • Deploy from CIProject token, shop onlyRevoke
  • Deletes are marked destructive

    So MCP clients such as Claude Code and Cursor ask you before an agent deletes a service, a volume or a project, and the server refuses it without an explicit confirm. A deleted service’s backups are kept for 7 days.

    1. delete_service webrefused
    2. delete_service web confirm: truedeleted

    Your agent’s client asks you before it sends the second. web’s backups are kept for 7 days.

  • An activity log

    Every action with who did it, person or agent, and what changed, kept for 14 to 90 days depending on your plan.

  • Sealed secrets

    Secrets you seal can be used by your services but never read back.

  • Isolated by default

    Every app runs in a gVisor sandbox, on a private network shared only with its environment.

Let it work. Keep the limit.

Paste into your terminal, with the token from your dashboard
$ claude mcp add --transport http dawnrose \
    https://app.dawnrose.ai/mcp \
    --header "Authorization: Bearer YOUR_TOKEN"