2.1k stars · PolyForm Shield 1.0.0 — source-available, NOT OSI open source · 2.5.1 (2026-08-31) · Track this in Scout
Sentry-compatible self-hosted error tracking, small enough to run beside everything else.
▶Repo detailsthe review · specs · pros & cons
What it is
- PolyForm Shield 1.0.0 is not open source. You may run it for your own business freely; you may not use it to build a competing error-tracking product. That is fine for most uses, and irrelevant to a product that is not itself an error tracker — but it belongs in the same notebook as n8n's fair-code and Remotion's licence, because it is another dependency you cannot fork if the company changes its mind
- Two thousand stars and a small team. The mitigation is unusually good here: it speaks the Sentry protocol, so if it stalls you change one DSN and point at something else — but check that before you rely on it
- An error tracker with no triage discipline becomes a firehose you stop opening. Mute the noisy ones in week one or it will go the way of every unread dashboard
Stars2.1k
LicencePolyForm Shield 1.0.0 — source-available, NOT OSI open source
Latest2.5.1 (2026-08-31)checked 7 Sep 2026
Written inPython
NeedsDocker
RunsSelf-hosted on your own server
Setup effort
2 / 5
Payoff
4 / 5
Good
- Sentry-compatible, so the SDKs, the documentation and Claude Code's knowledge all transfer — and so does your exit route
- Small enough to run beside everything else: single process, your existing PostgreSQL, no Redis and no worker cluster, unlike self-hosted Sentry
- Catches both halves of a web application — the React error the visitor sees and the FastAPI exception they never see — in one timeline
Watch for
- PolyForm Shield 1.0.0 is not open source. You may run it for your own business freely; you may not use it to build a competing error-tracking product. That is fine for most uses, and irrelevant to a product that is not itself an error tracker — but it belongs in the same notebook as n8n's fair-code and Remotion's licence, because it is another dependency you cannot fork if the company changes its mind
- Two thousand stars and a small team. The mitigation is unusually good here: it speaks the Sentry protocol, so if it stalls you change one DSN and point at something else — but check that before you rely on it
- An error tracker with no triage discipline becomes a firehose you stop opening. Mute the noisy ones in week one or it will go the way of every unread dashboard
Screenshots
