A Sentry self-hosted alternative that explains the error.
A small team that already sends errors with the Sentry SDK, and would rather not run the Compose stack behind a 4 CPU and 16 GB RAM install. errclue keeps that SDK, groups the error, and writes one sentence about the cause. The product is a hosted beta.
Sign upWhat Sentry asks you to run
The requirements page asks for 4 CPU cores, 16 GB of RAM plus 16 GB of swap, and 20 GB of disk. It recommends 32 GB of RAM. Source: https://develop.sentry.dev/self-hosted/
Setting COMPOSE_PROFILES=errors-only lowers the install script's hard check to 2 CPU cores and 7000 MB of RAM (7 GB). Source: https://github.com/getsentry/self-hosted/blob/master/install/_min-requirements.sh
That profile is still Docker Compose. The kafka service in docker-compose.yml has no profile of its own, so it still starts. Source: https://github.com/getsentry/self-hosted/blob/master/docker-compose.yml
The default in .env is COMPOSE_PROFILES=feature-complete. The errors-only comment there points at the feature note. .env: https://github.com/getsentry/self-hosted/blob/master/.env Feature note: https://develop.sentry.dev/self-hosted/optional-features/errors-only/
A lower check does not retire the 16 GB requirement, and it does not make errclue a smaller copy of that stack. This beta is hosted. There is no public install, and this page gives errclue no memory figure.
Numbers above were checked on 2026-10-01.
The layer a small team usually wants
What a small team usually needs from an error tracker is grouping, the stack, one sentence they can act on, and one webhook.
errclue stores error and message events. Sessions, replays, and transactions are acknowledged and dropped. JavaScript frames are restored from a source map you upload. Rails and Python rely on the lines the SDK already sent. errclue does not read a Git repository, does not open a pull request, and does not run your tests.
This beta accepts the envelope on a Cloudflare Worker, indexes events in D1, and keeps the raw payload in R2. That is a description of the hosted beta, not an install guide.
Keep the SDK. Change the DSN.
- Keep the Sentry SDK you already run.
- Point its DSN at errclue.
- Send one test exception. The issue shows the grouped stack, nearby lines when the event has them, and one sentence about the cause.
The DSN shape and the init snippets for Rails, Node, Python, and browser JavaScript are in the migrate notes. A minified JavaScript stack needs a source map upload as well. Migrate from Sentry. Upload source maps for JavaScript.
What the issue shows
Illustration of the shape errclue shows on an issue. Not a recorded customer event. The same lines are on the homepage. Open the homepage.
user.subscription is likely nil for users mid-signup — there's no null check before .plan on line 41. Add a guard, or eager-load the subscription.
Sentry self-hosted and this beta
| Topic | Sentry self-hosted | errclue, this beta |
|---|---|---|
| SDK | Official Sentry SDK. | Compatible. Change the DSN. |
| Install floor | 4 CPU cores and 16 GB RAM plus 16 GB swap on the requirements page. The errors-only check is 2 CPU cores and 7 GB. | No install. This beta is hosted on Cloudflare. |
| What is stored | Depends on the profile. The full install includes performance data and replay. | Error and message events. Other envelope items are dropped. |
| Code context | Symbols, the repository, and Autofix. | Lines the SDK sends. JavaScript uses an uploaded source map. errclue does not read the repository. |
| AI | Seer and related tools, which can open a pull request. | A plain-English diagnosis, a confidence score from 0 to 100, and a severity. No pull request. |
| Alerts | Built in. | A Slack or Discord webhook. |
When Sentry is still the right install
Stay on Sentry self-hosted if you want session replay, full APM, or Seer opening a pull request. Stay if you already run the Compose stack and you want the rest of that platform.
errclue writes a diagnosis for a person. The issue page shows a confidence score from 0 to 100 and a severity of low, medium, or high. It does not open a pull request, and this beta has no public install.
How much RAM does Sentry self-hosted need?
The requirements page asks for 4 CPU cores, 16 GB of RAM plus 16 GB of swap, and recommends 32 GB of RAM. Source: https://develop.sentry.dev/self-hosted/ The install script's hard check drops to 2 CPU cores and 7000 MB (7 GB) when COMPOSE_PROFILES=errors-only. Source: https://github.com/getsentry/self-hosted/blob/master/install/_min-requirements.sh
Does errors-only remove the Compose stack?
No. errors-only turns features off inside the same Docker Compose install. Kafka still starts, because that service has no profile in docker-compose.yml. Source: https://github.com/getsentry/self-hosted/blob/master/docker-compose.yml The default .env profile is feature-complete. Source: https://github.com/getsentry/self-hosted/blob/master/.env
Can I keep my Sentry SDK?
Yes. Point the SDK you already run at an errclue DSN. errclue keeps error and message events. Sessions, replays, and transactions are acknowledged and dropped.
Who should stay on Sentry self-hosted?
Teams that want session replay, full APM, or Seer opening pull requests, and teams that already operate the Compose stack and want that platform. errclue does not open a pull request, and this beta has no public install.