# Amba pricing

Last updated: 2026-10-03. Rates verified against the live billing engine 2026-06.

Amba pricing is per project: Free at $0 (1,000 MAU), Pro at $20 per month (25K MAU), Scale at $200 per month (250K MAU), and Enterprise by contract. Every tier includes all seven capability categories. Overages are linear and posted, and an optional spend ceiling caps the worst-case monthly bill.

## Tiers

| Tier | Price | Annual | MAU | Events/mo | Push/mo | Database | Media |
|---|---|---|---|---|---|---|---|
| Free | $0/mo | — | 1,000 | 10K | 1K | 100 MB | 250 MB |
| Pro | $20/mo | $16/mo | 25K | 250K | 50K | 1 GB | 1 GB |
| Scale | $200/mo | $160/mo | 250K | 2.5M | 500K | 5 GB | 25 GB |
| Enterprise | Custom | — | Custom | Custom | Custom | Custom | Custom |

- Free — $0. 1,000 MAU, 10K events/mo, 1K push/mo, 100 MB database, 250 MB media. Database capped at 0.25 compute units, 10 CU-hours of compute per month and 512 MB (at the compute cap it pauses until the month resets or the project upgrades). Sleeps after 14 days of inactivity (wakes on next request); max 2 free projects per account.
- Pro — $20/mo ($16/mo annual). 25K MAU, 250K events/mo, 50K push/mo, 1 GB database, 1 GB media. Email support; 7-day backups.
- Scale — $200/mo ($160/mo annual). 250K MAU, 2.5M events/mo, 500K push/mo, 5 GB database, 25 GB media. Priority support; 30-day backups.
- Enterprise — custom pricing. Custom limits; BAA, SSO, dedicated region, audit log, SLA. Contact: https://amba.dev/enterprise

Pricing is per project — one app, one project, one subscription. There is no per-seat charge; pricing never scales with team size.

## Overage rates (every tier)

| Meter | Rate | Notes |
|---|---|---|
| MAU | $0.50 per 1K MAU |  |
| Engagement events | $0.50 per 10K events |  |
| Push deliveries | $0.50 per 10K push deliveries |  |
| Database storage | $1.50 per GB-mo database storage |  |
| Media storage | $0.10 per GB-mo media storage |  |
| Telemetry events | $0.10 per 1M telemetry events | High-volume analytics ingest (track with { telemetry: true }). No included quota; no fan-out to segments, workflows, or push — which is why it costs a fraction of an engagement event. |
| Agent tool calls | $0.50 per 10K agent tool calls | Calls against a project's per-app MCP endpoint. No included quota; priced the same as engagement events. |

## Worked examples

Computed from the posted rates above:

- Pro project at 50,000 MAU: $20 base + 25,000 MAU over quota at $0.50 per 1K MAU = $12.50 overage → $32.50/mo.
- Scale project at 300,000 MAU and 3,000,000 events: $200 base + $25 MAU overage + $25 events overage → $250/mo.

## Enforcement

Two enforcement modes. Throttle (the default): a metered write past an included quota is refused with a machine-readable 402 — code, current usage, limit, and reset date — until the period resets or you upgrade. Overage billing: traffic keeps flowing and overage accrues linearly at the posted rates onto the next invoice. Either way you can set a monthly spend ceiling: at 100% the project degrades to read-only (metered writes return 402, reads keep working), with webhook warnings fired once per period at 80% and 100%.

Agents can read live tier, per-meter usage, projected overage, and the enforcement state from the billing status API (MCP tool: `amba_billing_status`) and set a ceiling with `amba_billing_set_ceiling` — useful to self-throttle before a heavy workload.

## Free-tier limits

New free projects keep every capability for building an app. The surfaces that run on Amba's domains, sending reputation, and compute are paid features or daily caps:

| Surface | Free tier |
| --- | --- |
| Custom domains, domain purchase | Paid plans |
| Email to any recipient, custom email templates | Paid plans |
| App builder | Paid plans |
| Sign-in email (magic link, email OTP) | 25 per day |
| Sign-in SMS codes | 10 per day |
| Push campaigns | 3 per day |
| Direct pushes (test, per-user) | 100 per day |
| Function invocations | 10,000 per day, 50 ms CPU each |
| Function schedules | 2, hourly or slower |
| Queue messages | 1,000 per day |
| New tracked links | 50 per day |
| Hosted site on `*.app.amba.host` | Serves with a "Built with Amba · preview" bar and noindex |

A refusal is a 402 `FREE_TIER_LIMIT_REACHED`; `details.limit` names the surface and `details.upgrade` is the one-call upgrade. Full reference: https://docs.amba.dev/billing#free-tier-limits

## Starting free from an agent

An agent-minted sandbox account (no email verification, no credit card) keeps its project, data, and keys. Claim it for its human owner as soon as you know who that is — `amba_developer_claim` (MCP), `POST /v1/auth/developer/claim {"email": …}`, or `amba claim <email>` — and the same account takes their address in place; nothing is re-provisioned. Each free project of an unclaimed sandbox account runs its own clock from when it was created (or became subject to the timeline): a claim notice from day 7, a hold on day 14 (reads work, writes return 403 `SANDBOX_CLAIM_REQUIRED`), and an archive on day 90 after a full 76-day hold. Archiving deletes nothing; claiming lifts all of it.

## Links

- Human pricing page: https://amba.dev/pricing
- Enterprise (custom limits, BAA, SSO, dedicated region, SLA): https://amba.dev/enterprise
- Agent index: https://amba.dev/llms.txt
- Full corpus, one file: https://amba.dev/llms-full.txt