Plans & Pricing

Mittr splits plan-level constraints into three orthogonal categories. Knowing which is which makes upgrade decisions obvious instead of feeling like a maze.

The numeric dimensions you actually pay for. There are three:

Meter	What it caps	Overage
Messages per month	Total deliveries across all endpoints	Per-tier rate on paid plans (Starter $1.00 / Growth $0.50 / Scale $0.20 per 1k); hard-cap on Free
Rate limit	Sustained requests per second	None — burst above the cap returns 429
Retention	Days events / delivery attempts / audit logs are kept	None — old data purged per category

Hit the message cap and the runtime keeps delivering on a paid plan; the excess is metered onto your next invoice. On Free, the delivery worker hard-caps at quota until the next month rolls.

Boolean access flags. A handler either has the right or it doesn’t. ✓ = included, ✗ = locked.

Feature	Free	Starter	Growth	Scale
OAuth SSO (Google / GitHub)	✓	✓	✓	✓
MFA (TOTP + backup codes)	✓	✓	✓	✓
Audit log	✗	✓	✓	✓
Transformations	✗	✓	✓	✓
Session policies (TTL, concurrent cap, IP allowlist)	✗	✗	✓	✓
GDPR data-subject tools (export + erasure)	✗	✗	✓	✓
SAML 2.0 SSO	✗	✗	✗	✓
SCIM v2 user provisioning	✗	✗	✗	✓
Extended audit retention (1 year+)	✗	✗	✗	✓
Support SLA	none	24-hr	24-hr	4-hr

Locked features are hidden from the dashboard sidebar and tabs — operators don’t see “upgrade required” teasers, the affordance isn’t there. Server-side, locked endpoints return 402 Payment Required with the upgrade URL in the response body.

Mittr enforces a system-wide hard cap of 10,000 of any one configuration kind: endpoints, event types, alert rules, connectors, inbound endpoints, team members. This is independent of plan tier — it exists to protect the database from runaway clients and is far above what any reasonable workspace will configure.

Hit the guard and you get a 429 Too Many Requests distinct from the 402 you’d get on a plan-cap breach. If you genuinely need more than 10k of something, talk to support — it’s a conversation, not a billing decision.

Tier	Monthly	Messages	Rate (req/s)	Retention	Highlights
Free	$0	3k	10	7 days	OAuth SSO, MFA
Starter	$29	50k	100	30 days	+ Audit log, Transformations, 24h business SLA
Growth	$99	500k	500	90 days	+ Session policies, GDPR tools, 8h business SLA
Scale	$499	5M	2,000	365 days	+ SAML SSO, SCIM, Extended audit, 4h business (M-F EAT)

Annual billing saves ~17% on every paid tier.

Prices are in USD. Paddle (our Merchant of Record) applies the right tax for your billing location at checkout — either added on top (US, Canada) or already included in the listed price (most of Europe, Australia, New Zealand), per local convention. Paddle remits the collected tax to your local authority.

Committed volume, security review, custom retention windows, compliance attestations (HIPAA / PCI / SOC 2), dedicated infrastructure, or a 1-hour SLA all live in a custom contract — not the self-serve catalog. Email [email protected] and we’ll scope the deal around what your team actually needs.

The dashboard’s Billing page (at app.mittr.io/dashboard/billing) renders the full compare grid with your current tier highlighted. Upgrades take effect as soon as the payment clears.

Downgrades route to a support email ([email protected]) for the first 6 months of the new pricing model — the runtime needs to quiet down feature gates retroactively without losing access to historical data, and we’re keeping that path human-supervised until we’ve seen enough cases to automate it confidently.

Earlier versions of Mittr gated resource counts per tier: “Starter gets 25 endpoints, Growth gets 50, Scale unlimited.” That model is gone. Cardinality is now a DoS concern, not a pricing concern, and tiers reflect what an operator actually gets value from at higher plans (auth, audit depth, compliance, support tier).

If you migrated from the old model with non-default values in your clients.*_retention_days columns, those settings carry forward unchanged — the per-tenant override always wins over the plan default.