A new organization starts with a 14-day trial of Pro while trials are open (otherwise it starts on
Free): no card, up to 50,000 captured
sessions and 5,000 sessions with replay, with hard caps and never an overage. When it ends, the organization moves to Free
unless you choose Pro. Free and the trial have no service levels; the
terms of service describe how availability is measured and the credits.
Who gets a trial
The trial goes with the email address you verified when you signed up.- One per company. Everyone who signs up with an address at your company’s domain shares
one trial, and a subdomain counts as its domain (
eng.acme.comisacme.com). An organization created after the trial was used starts on Free: ask the colleague who started it to invite you, or choose Pro. - One per person at a free email provider (Gmail, Outlook and the like) or a university: your next organization starts on Free.
- None from a temporary email address. Sign up with a permanent one.
Captured sessions
A captured session is a session whose detail is kept by sampling: its spans, logs and screens. Users are not metered. Crashes, errors and the session summaries behind release health are sent from every session, captured or not, within your plan’s fair use. On Free and during the trial, only the detail stops at the cap: crashes and summaries keep flowing, and there is never an overage. On Pro, sessions above the included 50k are billed per 1,000.Sessions with replay
A session with replay is a captured session that sent at least one replay segment. It is the second billed unit.- Free: 500 a month, hard cap. Above it, replay stops for the rest of the month; sessions are still captured.
- Pro: 5,000 included, then billed per 1,000.
- Trial: Pro’s numbers under a hard cap, never an overage.
- Enterprise: by contract.
Caps and alerts
Each billing period counts captured sessions and sessions with replay: the whole 14 days of the trial, then each calendar month. Settings › Plan and usage shows the count against your cap, or against the included sessions on Pro without one.- Caps. Free stops capturing detail at 5,000 sessions a month and the trial at 50,000. On Pro you can set a spend cap, the most a month may cost, in Settings › Plan and usage; it is optional, and there is none until an owner sets one. At the sessions it pays for, detail capture stops the same way. Only owners set it, and raising it resumes capture at once. Devices pick the change up at their next policy fetch, so a few more sessions may arrive after the cap; they are never billed beyond it.
- Alerts. Owners and admins get an email at 50%, 80% and 100% of the cap (or of the included sessions), and when a day’s sessions jump to ten times the daily average of the week before.
Fair use
Beyond the two billed units, each plan includes this much each calendar month (UTC). None of it is billed. Enterprise sets its own in the contract.
At or near a limit:
- Counted sessions. From 95% of the limit, session summaries are sampled at a rate that falls from 10% to 0.1% at the limit and stays there, and release health becomes an estimate; the console says so. Back under 90% of the limit, every summary is sent again. Detail capture is not affected. On Pro the limit rises with the month’s captured sessions.
- Crash and error records. 10% are sampled while the month stays over the limit, and the first of each issue on a device always passes: the SDK keeps the fingerprints it sent this month. So every issue is always captured, except under the cost brake below. On Pro the limit rises with captured sessions.
- Telemetry per session. The limit is an average, counted against at least 1,000 captured sessions. From 95% of what the month allows, logs, spans and metrics are sampled that same month, down to 0.1%, and owners and admins get a warning. Under 90%, every record is sent again.
- OTLP without a session. Records with no
session.idare refused with HTTP 403 (PERMISSION_DENIED, not retryable): on Free and the trial always, on Pro once the month’s 10 GB are used. Apsio’s SDKs always sendsession.id, so app data is never affected. See Send OTLP. - Stored symbols. New uploads are refused with HTTP 403 and a clear message. Nothing stored is deleted, and symbols no crash needs still expire on their own.
When the trial ends
At the end of the trial, if you did not choose Pro, the organization moves to Free: capture goes on within Free’s caps, so your apps keep sending crashes and sessions. Data older than Free’s retention is hidden and deleted on its original schedule, and choosing Pro makes what is still stored readable again.Retention when the plan changes
Each row is kept for the retention of the plan it was captured under: detail for the detail retention, crashes and the session summaries behind release health for theirs. Reads follow the current plan.- Moving to a plan that keeps data for less time. Data captured under a longer plan is hidden within a minute and deleted on its original schedule.
- Moving to a plan that keeps data for longer. What is captured from then on is kept longer. Data captured before keeps its original schedule, and what is still stored becomes readable again within the new plan’s retention.
- Erasure deletes everything when it runs, whatever the plan (see Privacy and security).