Plans & tiers

Plutus has five tiers: Hobby, Starter, Growth, Scale, and Enterprise. Each tier sets a monthly spend-tracking limit, an event limit, a data retention window, and (on the lower tiers) a cap on how many cost/event source connections an account can have.

Tier limits

Tier	Price	Spend limit	Event limit	Retention	Cost connections	Event connections
Hobby	Free	$10,000/mo	250,000/mo	30 days	5	3
Starter	$29/mo	$30,000/mo	1,000,000/mo	60 days	10	6
Growth	$149/mo	$250,000/mo	5,000,000/mo	90 days	Unlimited	Unlimited
Scale	$499/mo	$1,000,000/mo	20,000,000/mo	365 days	Unlimited	Unlimited
Enterprise	Custom	Custom	Custom	1,095 days (3 years)	Unlimited	Unlimited

“Events” are the business-events that populate the timeline overlay (deploys, incidents, invite lifecycle events, and so on) plus telemetry pushed through the usage-ingestion API — not cost data. “Spend limit” is the account’s own tracked cloud/SaaS spend for the current billing cycle, not what Plutus charges you.

Retention applies to cost data and usage telemetry — see Data retention for how the purge itself works. Data older than the window is deleted automatically; it isn’t archived or downloadable afterward. Retention only ever moves in one direction when you change plans: downgrading doesn’t retroactively delete data outside the new window immediately, but the next retention pass will trim to it.

Your account’s current tier, spend, and event usage are on the Plan & Billing page in Settings — see Upgrading & billing. Exact current numbers there are the source of truth if this page and the app ever disagree.

What happens if you go over a limit

Two of the limits above are enforced automatically. A third thing — account suspension — looks similar from the outside but is unrelated: it’s a manual action, never something usage triggers on its own. These are three separate mechanisms:

	Triggered by	Automatic?	Reversible?
Event limit overage	ingested events exceed the tier’s event limit	yes, every billing cycle	yes, at the next cycle
Spend limit ladder	tracked spend exceeds the tier’s spend limit	yes, checked daily	yes, automatically
Account suspension	a Plutus staff decision	no — staff only	only by staff

Going over the event limit doesn’t block anything

Exceeding your tier’s event limit doesn’t stop event ingestion or recording, and Plutus doesn’t charge for the overage. It’s counted, and once you’re over, a banner on the dashboard tells you so and links to upgrade. The reasoning is one-sided: silently dropping events would mean losing telemetry you can’t recreate, which is worse than temporarily carrying usage above what the plan technically allows.

Going over the spend limit: a warning, then a pause on new data — never a deletion

Exceeding your tier’s spend limit escalates through three states:

1. Under the limit — nothing to report.
2. Warned — the first daily check that finds your account over its spend limit. You’re notified. Nothing about your account changes yet — syncing and app access work exactly as before.
3. Enforced — the account is still over the limit 14 days after the warning. New data stops being collected: scheduled cost/event syncs stop running, and the usage-ingestion API starts rejecting pushed data. Nothing that’s already synced is deleted, and reading your existing data in the app is unaffected.

The 14-day grace period is intentionally generous — it’s long enough to review the overage and either bring spend down or upgrade before anything stops.

Recovery is automatic. As soon as a daily check finds your tracked spend back under the limit, the account returns to the “under the limit” state and syncing resumes on its own — no support ticket needed. Going over again later starts a fresh 14-day grace period, not a continuation of the old one.

If you’re in the middle of resolving an overage — say, actively working with support on a plan change — support can pause the escalation so the account stays at “warned” indefinitely instead of reaching “enforced” on a fixed clock.

Account suspension is a manual, staff-only action

An account can also be suspended or archived, but this is never automatic — it’s a decision made by Plutus staff, and only staff can reverse it. A suspended or archived account can’t be used at all: every request, including just loading a page, is rejected until staff restores it. This is different from — and more restrictive than — the “enforced” spend-limit state above, which only stops new data collection and never blocks reading your existing dashboard.

Summary: what still works at each stage

State	View existing data	New syncs run	Usage-ingestion API
Over event limit (any tier)	yes	yes	accepts data
Spend limit: warned	yes	yes	accepts data
Spend limit: enforced	yes	no	rejects data
Suspended / archived	no	no	rejects data

If you push usage data through the ingestion API while your account is enforced or suspended, the request is rejected with an error rather than silently accepted and dropped — so a pipeline posting on a schedule can detect the failure and retry later instead of believing it succeeded.