Pricing & Billing

Key concepts

• Session: A continuous period of activity from a device. Sessions include navigation views, network spans, and errors/crashes. A new session typically starts when the app launches or after inactivity.
• Event: Any recorded telemetry item such as a span, log, or error captured by the SDK or backend. Events belong to sessions when initiated from mobile, or to backend traces when exported from servers.

What you’re billed for

• Events: Counted per telemetry item ingested (e.g., spans for network requests, custom spans, errors, logs).

Plans include a monthly pool of events. Overages are charged per additional unit.

Plans

• Free

  • Price: $0/month
  • Events: 1,000,000/month
  • Retention: 14 days
  • Team members: 1
  • Dashboards: 3
  • Support: Community

• Pro

  • Price: $50/month
  • Events: 50,000,000/month
  • Retention: 30 days
  • Team members: 10
  • Dashboards: 50
  • Support: Email

• Enterprise

  • Price: Custom
  • Events: Unlimited
  • Retention: 365 days
  • Team members: Unlimited
  • Dashboards: Unlimited
  • Support: 24/7 Phone

Estimating usage

• A typical session generates several events: 10–100 spans depending on screens and network calls.
• Heavy screens or chat/streaming features can increase event volume; use sampling or limit custom spans in non-critical paths.

Billing cycle and overages

• Monthly cycle; usage resets each month.
• Overages billed at end of cycle.

FAQs

• Do backend-only traces count as sessions? No. They count as events only. Sessions are created by the mobile SDK.
• Does a crash create extra events? Yes, the crash is recorded as an error event plus related spans.