Plans & limits
mAPI-ng ships four plans. Free is the default every organization starts on;
Pro and Team are self-serve subscriptions; Enterprise is a contract sale with
limits tuned per customer. All plans include the full RED dashboard and
unlimited services, so upgrading only raises ingest capacity, retention, and
team size.
| Plan | Price | Telemetry upload rate | Burst | Series cardinality | Retention | Seats |
|---|---|---|---|---|---|---|
| Free | $0 forever | 100 req/s | 200 | 10k | 30 days | 1 |
| Pro | $49/mo | 500 req/s | 1,000 | 100k | 90 days | 5 |
| Team | $199/mo | 2,000 req/s | 4,000 | 500k | 180 days | 20 |
| Enterprise | Custom | 10k+ req/s | 20k+ | 5M+ | 365 days | 1,000 |
Max ingest payload is 4 MiB on every plan. Supported self-hosting (an
operator-run deployment backed by an SLA) is an Enterprise feature; every
plan can still be self-hosted without support, see below.
What counts against a limit
- Telemetry upload rate is enforced per tenant as a token bucket sized to
your plan's upload req/s and burst allowance. It meters summary uploads,
which are batched (~every 10s), not your application's request rate, so the
ceiling sits far above your app's traffic. Uploads over the limit are
dropped, not billed as overage: raise the ceiling by upgrading rather than
paying more on the same plan. - Series cardinality counts distinct
(service, endpoint, method)
combinations tracked for your tenant. Once you hit your plan's cap, new
series stop being recorded until you upgrade or retire old ones. - Retention is how long raw metrics stay queryable before they age out
of the raw tier. See Architecture for how rollups
extend history beyond the raw window. - Seats are your organization's members plus outstanding pending
invites, counted together so you can't over-invite past the cap. See
Team & invites.
Changing plans
Upgrade or downgrade from the Setup page; see Billing &
subscriptions for how checkout and cancellation work. A plan
change takes effect once Stripe confirms the subscription update, not
immediately on click.
Self-hosting instead
The whole core, client, proto, and server, is MIT-licensed. You can run the
full stack yourself for free, with the same limits as whichever plan you
provision in your own plan_limits table. Enterprise adds a supported,
SLA-backed version of that same self-hosted deployment. See
Self-hosting and Licensing for
details.