Can Sentry be vibe coded?
Receive bounded error events, group them, link releases, and notify one team
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Sentry, receive bounded error events, group them, link releases, and notify one team. The hard boundary is sdk ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, plus independent infrastructure and reliable alerting.
Jump to the build brief ↓Checked Jul 2026
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Receive bounded error events, group them, link releases, alert one team through one channel, and publish an honest status page.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations
- global probe network
- phone and SMS delivery
- massive retention
- Reliability at the vendor's scale is an operations problem, not a prompt.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
Why people still pay
People still pay for Sentry because monitoring must continue working during the exact outage it reports, which makes independent infrastructure and alert delivery the real product. The recurring cost buys probe geography, clocks, retries, deduplication, sampling, storage, paging, notification delivery, on-call rules, and its own uptime, not just the visible interface.
Reliability at the vendor's scale is an operations problem, not a prompt.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Sentry
Context
**Sentry** — Receive bounded error events, group them, link releases, and notify one team. It currently costs Variable pricing.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Sentry, receive bounded error events, group them, link releases, and notify one team. The hard boundary is sdk ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, plus independent infrastructure and reliable alerting.
This brief describes a focused, single-operator replacement for the part of Sentry that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Receive bounded error events, group them, link releases, alert one team through one channel, and publish an honest status page.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Server outside the monitored failure domain.
PostgreSQL.
Optional ClickHouse.
Public HTTPS.
Data and integrations
Email or webhook destination.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a personal replacement for Sentry in an empty repository.
Use Go, PostgreSQL, ClickHouse, a Next.js 15 dashboard, and Docker Compose; do not offer alternative stacks.
The core loop is: receive bounded error events, group them, link releases, alert one team through one channel, and publish an honest status page.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
Run checks from one independently hosted worker and store raw results plus incident state transitions.
Send deduplicated alerts to email or one webhook destination with recovery notifications.
Create services, maintenance windows, incidents, subscribers, and a public status page.
Add bounded event ingestion for application errors with sampling and sensitive-field scrubbing.
Provide health checks, retention settings, exports, backups, and a test-alert function.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a worldwide probe network.
Deliberately leave out phone, SMS, and managed on-call escalation.
Deliberately leave out unbounded logs, enterprise observability, and vendor-operated incident response.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations.
Global probe network.
Phone and SMS delivery.
Massive retention.
Reliability at the vendor's scale is an operations problem, not a prompt.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Uptime Kuma](https://github.com/louislam/uptime-kuma) — Popular open-source uptime monitoring dashboard with many check types
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/sentry
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Open-source prior art
Before you start
Can Sentry be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Sentry, receive bounded error events, group them, link releases, and notify one team. The hard boundary is sdk ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations, plus independent infrastructure and reliable alerting.
What can an AI coding agent reproduce from Sentry?
Receive bounded error events, group them, link releases, alert one team through one channel, and publish an honest status page. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Sentry replacement still be missing?
SDK ecosystem, grouping models, tracing, replay, global ingestion, and enterprise operations; global probe network; phone and SMS delivery; massive retention; Reliability at the vendor's scale is an operations problem, not a prompt.; Connectors, OAuth flows, and vendor API changes require constant upkeep.
What do I still own after building a Sentry alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.