Plans & pricing

​

Standard plan limits

​

What enterprise unlocks

• Audit logs — an immutable, account-wide trail of governance actions (keys, domains, inboxes, and webhooks created or deleted), each with its actor and source IP. Audit logs and per-key IP allowlisting both live under audit logs.
• API-key IP allowlisting — lock a key to trusted IPs or CIDR ranges, deny-by-default, so a leaked secret is useless from anywhere else.
• Pay-as-you-go billing — metered billing on negotiated per-unit rates, with optional commitment and overage instead of a fixed tier. See standard vs. enterprise billing.
• Higher limits — more inboxes, domains, monthly volume, and storage than the scale ceilings — plus priority support and a named account team.

​

What gets metered

​

How usage is counted

• Usage counters update continuously as work is accepted — a recipient accepted for delivery, a message received, bytes stored — not only at month’s end.
• A broadcast meters per recipient the same way a direct send does.
• A retried send carrying the same Idempotency-Key resolves to one accepted send and meters once — see idempotency.

​

Read your meter

curl https://api.dairo.app/v1/whoami \
  -H "Authorization: Bearer $DAIRO_API_KEY"

const me = await dairo.whoami();
console.log(me.plan, me.usage); // counters for the current billing period

me = dairo.whoami()
print(me.plan, me.usage)

dairo whoami

{
  "plan": "scale",
  "period": { "monthStart": "2026-06-01T00:00:00Z" },
  "limits": { "inboxes": 1000, "domains": 100, "emailsPerMonth": 500000, "storageBytes": 268435456000 },
  "usage": {
    "inboxes": 12,
    "domains": 3,
    "emailsThisMonth": 18420,
    "inboundEmailsThisMonth": 6120,
    "outboundEmailsThisMonth": 12300,
    "storageBytes": 4194304
  }
}

​

Standard vs. enterprise billing

• Where to see it. The dashboard’s Usage and Billing pages show current-period metered usage, a projected cost, and your invoice history. The billing portal downloads invoice PDFs and manages your payment method. Billing is a dashboard action, not part of the API — no API key required.
• Cadence. Metered usage accrues continuously and rolls up per calendar-month period (period.monthStart in whoami). Subscription charges and metered overage are invoiced at the end of each period, and counters reset to zero when the next one starts.
• Projected cost. The dashboard layers a cost projection over the raw counters — your current-period outbound count times the per-recipient rate, plus any plan base. It’s an estimate on every plan and becomes your actual metered charge on the enterprise pay-as-you-go tier. Exact rates are set by your plan or contract.
• What’s in a metered event. Each accepted unit is recorded as a single billable quantity, de-duplicated so an idempotent or retried send is never counted twice. No recipient addresses and no message content are ever included — only the billable count and minimal context.
• Managing your subscription. Cancel, reactivate, or change plan from the dashboard. A cancellation is scheduled for the end of the current period by default and is reversible until then, so you keep what you’ve paid for through the period.

​

Controlling spend

• Cap automated sending with send budgets. A budget is a hard ceiling Dairo enforces on an account, a key, or an agent. The next send that would cross the line is refused before it goes out — the first move for any automated sending.
• Make retries safe with idempotency. A retried send carrying the same Idempotency-Key resolves to one accepted send and meters once, so a retry storm can’t double your bill.

​

Moving to enterprise

​

Next steps