StatOSS compared with Sentry
Sentry sells error monitoring, tracing, replays, profiling and logs from $26 a month. StatOSS takes the same SDKs for errors and logs, next to a status page, from free.
import * as StatOSS from "@statoss/sdk";
StatOSS.init({
dsn: "https://<key>@ingest.statoss.com/<app number>",
environment: "production",
});Side by side
| StatOSS | Sentry | |
|---|---|---|
| Free errors | 5,000 a month, kept 30 days | Developer: 5k errors, 1 user, 30-day lookback |
| Paid | Hobby $4: 50,000, kept 30 days, one person. Pro $15: 500,000, kept 90 days, 3 people, $5 each after | Team $26 a month: 50k errors, unlimited users, up to 90-day lookback. Business $80 a month: SAML and SCIM |
| Past the allowance | Answered 429 with Retry-After | Pay as you go, $0.0003625 per error from 50K to 100K, down to $0.00015 past 20M |
| Logs | Add-on: $5 a month with 15 GB, then $0.25 a GB | 5 GB included, $0.50 per GB more |
| Uptime and cron | 1 to 100 monitors with a status page, every plan | 1 uptime monitor and 1 cron monitor; $1.00 per uptime alert and $0.78 per cron monitor more on Team |
| Tracing, replays, profiling | Taken and not stored | 5M spans, 50 replays, profiling pay as you go |
| SDKs | Any Sentry SDK, @statoss/sdk, the Python statoss package | Sentry's own |
| Status page | Included | None on its pricing page |
Facts about the other product were read from its own site on 11 October 2026. Prices and limits change; check theirs before deciding, and tell [email protected] if something here is out of date.
When Sentry is the better pick
Tracing, session replay, profiling, Seer, SAML and SCIM: Sentry has them and StatOSS does not.
Where StatOSS fits: a team that wants its errors and its status page on one bill, with the Sentry SDKs it already has, at $4 or $15 a month.
Moving over
Make an app, copy its DSN where Sentry's goes, and releases and source maps upload with sentry-cli or npx @statoss/cli. The send errors docs have the steps.