Self-hosted Sentry
Errors, performance, code coverage, and more. That breadth makes sense if you need it all. Otherwise, it is extra weight.
-
“Rock-solid after switching from Sentry”
-
“No need to set up 50 parallel services”
-
“It pretty much pays for itself”
Self-hosted error tracking
without the Sentry stack
Replace self-hosted Sentry’s many services with one Telebugs container. Less infrastructure, fewer moving parts, and simpler upgrades.
One error tracker for your whole stack. Keep the Sentry SDKs you already use.
Trusted by teams at
What is Telebugs?
Telebugs is a refreshingly simple, installable error tracking system and a drop-in Sentry alternative that collects, groups, and notifies you about errors in your applications.
Run it on your server and point the Sentry SDKs you already use at it. Your applications keep reporting errors the same way. The difference is where those reports go, who controls the data, and how much software you have to run.
Self-hosted Sentry is a lot to carry
Telebugs
Move to focused error tracking. Less to learn. Less to run. Less to think about. The smaller scope is not a limitation. It is the point.
Change one DSN. Keep your Sentry SDK.
Reports go to your Telebugs server instead of Sentry. Your application keeps reporting errors the same way.
The Sentry SDK is redirected from Sentry to Telebugs by changing the DSN.
See one error instead of hundreds of duplicates.
Telebugs groups related reports and puts the busiest problems first.
Know when something breaks.
Get push, email, Slack, Discord, Teams, or webhook alerts. Notification rules keep the noise under control.
See what happened.
Backtrace, breadcrumbs, request details, local variables, environment, and custom context stay together.
Fix it yourself. Or let AI help.
Dig into the report in Telebugs, or let an approved AI coding agent inspect it over MCP.
Resolve it. Telebugs keeps watch
Once resolved, the error is out of sight. If it happens again, Telebugs reopens it and tells your team.
Hey everyone,
I’m Kyrylo, the founder of Telebugs.
I’ve spent more than 10 years building error-tracking software: first for other companies, now for my own.
I started as an intern at BugSnag and spent most of my career at Airbrake. Both taught me what great error tracking looks like. But if you wanted to keep your data on your own hardware, your options got complicated fast.
The obvious choice was self-hosted Sentry.
But Sentry brings a whole fleet of services with it. Services you have to install, monitor, upgrade, and babysit.
I couldn’t accept that keeping your production error data on your own servers meant operating an entire observability platform. And I knew I couldn’t be the only one stuck with the same problem.
All I wanted was to know what broke, have enough information to fix it, use something that looked polished, and keep the data on my own server.
I couldn’t find that.
So I made it.
That’s Telebugs.
I hope it helps teams that have been looking for the same thing.
Where Telebugs fits
-
For product teams Make production errors visible to the people who can fix them. Give developers one shared place to triage errors across every application they own.
-
Inside your environment Regulated teams keep production data on infrastructure they control, along with their own access, retention, and backup policies.
-
Across your client projects Agencies and consultants can keep every client’s data separate in one installation. Each project gets its own space and can be handed over when the time comes.
-
On a small team Bootstrapped companies already operate plenty of systems. Telebugs delivers serious error tracking without becoming another sprawling platform to maintain.
One container, one server
Telebugs runs as a single Docker container on a modest server. To get started, you’ll need:
- A domain name. You’ll need to configure your DNS to point to the IP address of the server where Telebugs will run.
- A server with internet access and Docker support. This can be your own machine, a virtual private server (VPS) like DigitalOcean, or a cloud service like AWS. The minimum specs are 1GB of RAM and 1 CPU core.
- Some basic technical skills. We’ll give you a single terminal command to run on your server, and it’ll handle everything from setup to generating an SSL certificate (including installing Docker if it's not already present).
See the complete installation.
From a fresh server to a running Telebugs instance in 11 minutes.
Bash scripts, bye-bye.
Hello, Telebugs CLI
~ ❯ telebugs setup ••••••••
████████╗███████╗██╗ ███████╗██████╗ ██╗ ██╗ ██████╗ ███████╗
╚══██╔══╝██╔════╝██║ ██╔════╝██╔══██╗██║ ██║██╔════╝ ██╔════╝
██║ █████╗ ██║ █████╗ ██████╔╝██║ ██║██║ ███╗███████╗
██║ ██╔══╝ ██║ ██╔══╝ ██╔══██╗██║ ██║██║ ██║╚════██║
██║ ███████╗███████╗███████╗██████╔╝╚██████╔╝╚██████╔╝███████║
╚═╝ ╚══════╝╚══════╝╚══════╝╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝
Preparing [ ✓ ]
Downloading [ ✓ ]
Starting [ ✓ ]
Telebugs is ready!Okay, Telebugs is installed.
Six months from now, you shouldn’t have to remember how Telebugs is put together. Type telebugs and get on with it. The CLI keeps the fiddly, easy-to-forget work in one place.
Updates run nightly by default. telebugs auto-update changes the hour or turns them off; telebugs update installs one now and keeps the previous version.
Locked out? telebugs password reset <email> securely resets a user’s password.
Moving servers? telebugs data backup creates and verifies an archive. Restore it elsewhere with your data, configuration, secrets, and Telebugs version.
That’s the Telebugs CLI: manage your installation without becoming its caretaker.
~ ❯ ssh admin@telebugs
admin@telebugs:~$ telebugs
Install and manage your Telebugs instance
Usage:
telebugs [command]
Manage application data:
data Manage application data
Manage passwords:
password Manage passwords
Manage automatic updates:
auto-update Manage automatic updates
Manage versions:
rollback Rollback Telebugs to the previous version
update Update Telebugs to the latest version (use --tag for a specific image tag)
Additional Commands:
help Help about any command
setup Re-run the initial setup of Telebugs
start Start Telebugs
status Check whether Telebugs can ingest errors and send notifications
stop Stop Telebugs
Flags:
-h, --help help for telebugs
Use "telebugs [command] --help" for more information about a command.
admin@telebugs:~$One container sounds nice.
But can it keep up?
But of course. On 2 vCPU and 4 GB RAM,
Telebugs
sustains
about 50 fully processed reports per second—about 4.3 million reports per day.
Under the hood, it’s built with Ruby on Rails. SQLite handles application data, caching, and background jobs, so there is no PostgreSQL, Redis, or separate queue broker to operate. It runs on AMD64 and ARM64, with one persistent volume to back up.
Want the details?
The manual covers installation, configuration, integrations, upgrades, and everyday operation.
Open the manual
What teams say after switching
Telebugs has been great to work with — much easier than Sentry. Going from ~60 containers, 20Gb RAM, 12 vCPUs with Sentry on-prem … to a simpler, faster tool with 4Gb of RAM and 2 vCPUs has been frankly liberating. I really appreciate the simplicity and speed.
Working with Kyrylo and Telebugs has been a real pleasure. One of my customers had a fairly complex setup, but everything was resolved quickly and with great care. Kyrylo responded fast, often within hours. Telebugs is now in use across more than 20 projects and has become a valuable part of our workflow.
Telebugs has been incredibly reliable for my error tracking — super solid, easy to set up, and it just works. When I spotted a small bug, Kyrylo fixed it and pushed an update the same day. I appreciate the focus on keeping it lightweight and efficient. Highly recommend!
Telebugs to me is more of an investment than a purchase. It already paid itself back in the countless hours saved trying to figure out what broke where in a number of projects. The effortless integration with Sentry SDKs is a massive advantage over other solutions.
Telebugs is perfect for us as our error telemetry does not leave our premises and while tools like Sentry can be configured to limit the amount of data sent, we love the fact that we are sure data will not leave our environment. We are happy with the pricing model too.
After more than 10 years running production systems, I’ve tried countless error tracking tools. Telebugs is the first one that finally feels like a sensible self-hosted solution without unnecessary complexity. Kyrylo has also been incredibly responsive whenever questions come up. I’m very happy with it and would gladly recommend it to other teams.
Telebugs has been a great addition to our workflow. It's fast, simple to use, and does exactly what you need without overcomplicating things. I especially liked how easy it was to set up the webhooks. And whenever I had a question, Kyrylo was incredibly responsive and helpful. It's clear he genuinely cares about the product and the people using it. Highly recommend!
Telebugs solves two key problems for us well: data privacy, as we no longer share error logs with any external service, and hosting costs, since you pay once and use it across multiple products and internal systems. Plus Kyrylo is very open to constructive feedback and delivers fast improvements.
We switched from Sentry: Telebugs was a breeze to install and has been rock-solid ever since. Being in control of the data and hosting was of utmost importance to us, and eliminating the need to have a US company in our GDPR subprocessor list.
There’s more where those came from. Keep reading what teams say about Telebugs.
Frequently asked questions
What do I give up compared with Sentry?
Telebugs focuses on error tracking: exceptions, grouping, backtraces, breadcrumbs, releases, source maps, alerts, and debugging context. It does not replace Sentry’s performance monitoring, logs, session replay, code coverage, or broader observability features. If you need all of those, Sentry may fit better. If errors are the job, Telebugs keeps the job smaller.
Does any error data leave my servers?
Telebugs does not require hosted processing. Your applications send errors to the instance you run. Optional webhooks, email, update checks, external notifications, and MCP clients communicate only when you configure them. After installation and license receipt migration, core error tracking can run without outbound internet, including on an air-gapped network, provided your applications and team can reach the instance. Initial downloads, updates, and external notifications need a planned network or transfer path.
Do I need to be a Docker expert to run Telebugs?
No. Telebugs needs a server that can run Docker, but the CLI
manages the container for you. On a standard Linux server, setup
can install Docker if needed. After that, you use the same
telebugs command to start, stop, check status, update,
and back up the instance. You should still be comfortable with
SSH, DNS, and basic server administration. See the
installation expectations
for the full division of responsibilities.
How much can one Telebugs installation cover?
One licensed instance can contain unlimited projects and unlimited teammates on its licensed domain. One administrator installs and manages it; everyone else uses Telebugs through a browser or phone. Point each application at the same instance and keep its errors in a separate project.
How do updates work? Do they cost extra?
When internet access is available, Telebugs can check once a day for updates and install eligible 1.x releases automatically. You can disable automatic updates and update manually if your environment requires tighter network control. Updates within the same major version (like 1.0 to 1.1) are free. A future major version may be a separate paid upgrade, and you can decide whether to take it.
What happens if I get stuck?
Email support is included for ordinary installation, update, and product questions. You’ll talk directly with Kyrylo, the person who builds Telebugs. If something is unclear, email [email protected].
Do you offer refunds?
Because Telebugs is downloadable source software, purchases are not refundable after delivery. Explore the read-only public demo for a quick look, or request a private demo if your team needs hands-on evaluation.