Billing & retention

View current usage under Organization → Billing. Owners manage payment method, invoices, and upgrades. The public pricing page mirrors the Hobby → Small team → Pro → Enterprise ladder.

Upgrading preserves configuration — integrations, teams, and statistics toggles stay in place; limits and retention expand to match the new plan.

• Hobby (free tier) — 3 worker seats, 1 integration, 14-day history. Human workers only; no developer API or CSV exports. No credit card required.
• Small team — 10 included seats, 3 integrations, 90-day history, CSV exports, team monitoring views. Per-seat overage billed monthly in arrears.
• Pro — 25 included seats, all standard integrations, 12-month rolling aggregated history, developer API access, AI agents (when enabled), organization-wide retention controls, faster support SLA.
• Enterprise — custom seats, SAML/SCIM, invoice billing, configurable retention, private integrations, and negotiated MSAs.

Display names in the app may show “Free” for the Hobby tier while marketing uses “Hobby” — they refer to the same $0 plan.

Retention caps how far back queries, timelines, reports, and exports reach. Effective retention is min(org.retentionDays, plan.maxRetentionDays) for raw activity, with a separate aggregated window on Pro for long-range rollups.

• Hobby — 14 days of activity history.
• Small team — 90 days; CSV exports cover the same window.
• Pro — 12 months rolling on aggregated reports and scores (typical operational promise); raw event retention follows plan fields in the product catalog.
• Enterprise — configurable; contact sales for data residency and custom policies.

Cron jobs prune data beyond the cap. Deletion procedures are documented in the privacy policy.

• Workers — monitored people and agents count toward maxWorkers.
• Integrations — connected modules cap at plan allowance (Hobby: 1, Small team: 3, Pro: 10+ standard connectors).
• Teams — org-defined filter groups (3 on Hobby, 20 on typical paid tiers).
• AI agents — coming-soon add-on on paid tiers; Hobby remains human-only on the price sheet.

Billing surfaces show usage meters and recommended upgrade paths when you approach limits.

The developer platform (Ingest API, Apps statistics, hosted MCP, API keys) requires apiAccessEnabled on your plan — Pro and Enterprise by default. Small team and Hobby cannot create developer apps or org API keys even if UI navigation is visible in docs.

Server routes enforce the gate in developer/_guard.ts alongside org Admin role checks. Upgrade to Pro before following the developer quick start.

1. Open Organization → Billing as an Owner.
2. Compare plans in the upgrade section or on /pricing.
3. Checkout via Stripe for paid tiers; invoices and payment method updates live on the same page.
4. After upgrade, confirm retention and export windows under Organization → Exports.

• “Downgrade keeps all history.” Data beyond the new plan’s cap becomes ineligible for query and is pruned on schedule.
• “Exports bypass retention.” They include at most the retention window at export time.
• “API keys work on Hobby for testing.” Use a Pro trial or staging org with API access enabled — Hobby blocks the developer guard.