> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apsio.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing

> Plans, what a captured session is, and what each plan keeps.

Prices are in US dollars. The [pricing page](https://apsio.io/pricing) also shows them in
Brazilian reais.

| | Trial | Solo | Pro | Enterprise |
| - | - | - | - | - |
| For | Everyone, 14 days, no card | One developer | Teams | Large teams |
| Price | \$0 | \$19 a month | \$79 a month | Annual contract |
| Captured sessions | 25k, capped | 10k included, capped | 50k included, then $0.50 per 1k ($0.40 from 5M, \$0.30 from 25M) | Volume price |
| Members | Unlimited | 1, plus tokens for the CLI, MCP and CI | Unlimited | Unlimited, with SSO and SCIM |
| Projects and apps | Unlimited | 1 project, with its apps | Unlimited | Unlimited |
| Detail retention | 14 days | 14 days | 30 days | Up to 13 months |
| Crashes and release health retention | 14 days | 90 days | 13 months | Custom |
| Annual | | \$190 a year | \$790 a year | |

## Captured sessions

A captured session is a session whose detail is kept by [sampling](/concepts/sampling):
its spans, logs and screens. Users are not metered.

Crashes, errors and the session summaries behind [release health](/concepts/sessions) are
sent from every session, captured or not. On Solo, 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.

To capture fewer sessions, lower the session sampling rate in the
[remote configuration](/remote-configuration).

## Caps and alerts

Each billing period counts captured sessions: the whole 14 days of the trial, then each
calendar month on a plan. The console shows the count against your cap, or against the
included sessions on Pro without one.

* **Caps.** The trial stops capturing detail at 25k sessions and Solo at 10k. On Pro you can
  set a spend cap, the most a month may cost; 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.

## When the trial ends

At the end of the trial, if no plan was chosen, collection stops: the SDKs get the kill
switch and the ingest endpoint answers `402`. Your data stays readable for 14 days, the
trial's retention, and choosing a plan resumes ingest at once.

## Annual plans and the price lock

* An annual plan costs 10 months for 12, paid up front.
* If you subscribe before general availability, you keep the price you started on for
  24 months.

## Solo

Solo is for one developer building an app without a team. You apply with your name, your
app's App Store or Google Play link, and a short statement that you build it alone. Until the
application is approved, the account stays on the trial. A Solo organization has exactly one
member; inviting someone else means moving to Pro.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.