Plans, limits, and retention

Understand Anectico's planned usage meters and history windows during early access.

Anectico measures usage in units a developer can connect to application behavior. Seats are not a usage meter.

Anectico is in early access. The table below describes the planned self-serve tiers shown on the pricing page; an early-access agreement or dashboard may show different limits. Settings → Account is the source of truth for an active organization.

Planned self-serve limits

Plan	Pooled events / month	Active metric series	Replay sessions / month	Retention	Hosted investigations
Free	1 million	1,000	1,000	7 days	—
Solo	20 million	10,000	10,000	30 days	—
Pro	150 million	50,000	50,000	90 days	—
Scale	500 million	100,000	250,000	180 days	2,000 / month

Current prices and included product capabilities are listed on the pricing page.

What counts as an event

One log line, trace span, error event, or diagnostic event counts as one pooled event. The event types share the same pool.

Metrics use active series because their cost depends on the number of distinct label combinations, not only the number of data points. At the active-series limit, existing series continue to ingest; only unseen metric names or label combinations are rejected. This rejection is non-retryable. The meter is organization-wide and its background snapshot may lag by a few minutes. Replays use completed recording sessions.

Retention

Retention is a rolling history window. Data outside the plan’s window is no longer available to search, timelines, API reads, MCP tools, or Customer Detective.

The window is organization-wide. Every project inherits the organization’s current plan or administrative override; projects cannot advertise or configure a separate retention period.

When a planned limit is reached

Anectico warns before a limit is exhausted. Under the planned policy, verbose logs degrade before spans, while errors continue to ingest and alerts continue to evaluate. New replay sessions can be paused. Clients should honor 429 responses and Retry-After; they should not retry in a tight loop.

Use Settings → Account to view current plan and usage.