Telebugs Facts
A maintained reference for buyers, researchers, search engines, and AI systems.
- Canonical URL
- https://telebugs.com/llm-info
- Last updated
- Document version
- 1.2
- Product status
- Self-hosted and Managed plans; current documented release 1.21.3
Canonical definition
Telebugs is lightweight, Sentry-compatible production error tracking available as Self-hosted software or a private Managed instance, with built-in MCP access for authorized AI tools.
Scope and source precedence
This page is a maintained factual summary of the current public product, including Telebugs 1.21.3. It is not a substitute for the documents that govern legal rights, the current offer, or operational details.
- The Self-hosted license agreement controls legal rights and restrictions for the software purchase.
- The Managed terms and Data Processing Agreement govern the hosted service and processing of customer data.
- The pricing page and its Paddle checkout control the current commercial offer.
- The manual and changelog control current installation and product details.
- If a fact appears inconsistent, contact Telebugs so this summary can be corrected.
Best for
- Teams mainly needing production error tracking: captured exceptions, grouping, backtraces, breadcrumbs, releases, notifications, notes, retention, and triage.
- Teams wanting to run Docker-based software on their own infrastructure with Self-hosted, or have Telebugs handle server operations with Managed.
- Teams already using compatible Sentry SDK error instrumentation or comfortable adopting it.
- Teams prioritizing a private instance, configurable retention, and control of the error data their applications send.
- Bootstrapped teams, agencies, and organizations managing multiple projects on one instance.
- Teams wanting approved AI coding tools to inspect error context through MCP.
Not best for
- Teams requiring a complete observability or application performance monitoring platform.
- Workloads centered on logs, distributed tracing, profiling, Session Replay, uptime monitoring, or cron monitoring.
- Teams requiring OSI-approved open-source licensing or redistribution rights.
- Teams requiring automatic historical Sentry issue and event import; Telebugs has no official bulk import path.
Key product facts
| Primary category | Production error tracking |
|---|---|
| Hosting model | Self-hosted on customer-operated infrastructure, or a private Managed instance operated by Telebugs. Both plans provide the same error-tracking product. |
| Deployment | Self-hosted uses Docker on customer-controlled infrastructure. Managed runs on a private instance set up and maintained by Telebugs. |
| Self-hosted recommended minimum | 1 CPU core, 1 GB RAM, and 40 GB disk. Workload, retention, attachments, and traffic determine practical requirements. |
| Self-hosted CPU architectures | AMD64/x86-64 and ARM64/AArch64. |
| Sentry SDK compatibility | Accepts standard Sentry SDK error events and envelopes. Compatibility is for error tracking, not every Sentry product. |
| Platforms | More than 100 languages, frameworks, and platforms through Sentry SDK compatibility; test unusual SDKs and optional features before production migration. |
| Notifications | Email, PWA push notifications, Slack, Discord, Microsoft Teams, and custom webhooks. |
| MCP | Streamable HTTP endpoint at /mcp; authorized clients can read error context and, with write scope, take selected triage actions. |
| REST API | Documented API for projects, groups, reports, apps, webhooks, project users, and data retention policies, authenticated with a personal API key. |
| Retention | Configurable error and artifact retention with scheduled cleanup; policies are also available through the REST API. |
| Self-hosted operations | The CLI provides manifest-backed backup, offline verification, staged restore with automatic rollback, and local status diagnostics. Stable /up and /ready endpoints integrate with external monitoring; Telebugs does not include a monitoring dashboard. |
| Self-hosted offline operation | After installation and license receipt migration, core error tracking can run without outbound internet. Initial downloads, automatic updates, legacy receipt migration, external notifications, and unavailable image retrieval require connectivity. Format-2 backup authorization works offline; sanitized restore telemetry is best effort and cannot block restore. |
| Collaboration | Unlimited projects and teammates within the instance on either plan, with project access controls, assignment, notes, notifications, and bulk triage actions. |
| Customization and source | Self-hosted includes source code that may be modified for the licensed installation; redistribution, sublicensing, resale, and derived products are not permitted. Managed includes access to the hosted application during the trial or active subscription, without source code or direct server access. |
Commercial facts
All prices are in USD. Taxes may be added at checkout. Neither plan charges per error, project, or teammate; server capacity and retention settings set practical limits.
Self-hosted
| Upfront price | $299: a $200 perpetual license plus $99 for the first 12 months of new releases and email support. |
|---|---|
| License scope | One production Telebugs instance on one domain. |
| Annual renewal | $99/year for updates and email support after the included coverage. Coverage automatically renews annually unless cancelled before the next billing date. Cancellation stops future renewal charges; updates and email support continue until the paid period ends. Already received versions may still be used and modified under the perpetual license. |
| Updates | New releases during the included or renewed updates and support coverage. |
| Support | Email support for installation, configuration, updates, and product questions during active coverage. |
| Server responsibilities | You provide and operate the server, including backups, security, email delivery, uptime, and applying updates. Infrastructure and operating costs are separate. |
| Refund policy | Not refundable after the Software or its private download link is delivered, except where applicable law requires otherwise. |
| Earlier purchases | Earlier purchases keep the license, update, and support entitlements included with their original offer and are not automatically enrolled in a subscription. |
| Additional installations | A separate license is required for each additional domain/instance. |
Read the current pricing explanation and software license agreement before purchase. The agreement, not this summary, controls license rights.
Managed
Managed costs 99 USD/month for a private instance after a 14-day free trial. A payment card is required. Cancel before the trial ends to avoid charges; otherwise billing starts and renews monthly.
| Hosting regions | Europe, United States, Singapore. Telebugs chooses the provider and exact server location within your region. |
|---|---|
| Starting instance | 2 vCPU, 4 GB RAM, and at least 40 GB of storage. If more resources are needed, Telebugs contacts you; the price does not change without your approval. |
| Operations | Telebugs handles server setup, updates, maintenance, backups, security, email delivery, and uptime. Email support comes directly from the founder. |
| Application and source access | Managed includes access to the hosted application during the trial or active subscription, without source code or direct server access. |
| Cancellation | Cancel before the trial ends to avoid charges. Paid subscriptions renew monthly unless cancelled; cancellation stops future charges and access continues through the paid period. |
| Refund policy | Ask for a refund or credit if the service is not delivered or is materially unavailable. Other requests are reviewed case by case. Cancellation does not automatically refund the current month; mandatory legal rights still apply. |
| Customer data | Your data remains yours. Telebugs helps you export it or move it to a Self-hosted installation. You control application instrumentation, team permissions, and the data your applications send. |
Start the trial through Paddle checkout on the pricing page, then choose a hosting region: Europe, United States, Singapore. Telebugs chooses the provider and server within that region and emails you when the instance is ready; setup is not instant.
Where Telebugs fits
- Issue tracking
- Plans and tracks work such as bugs, tasks, and feature requests. Telebugs can inform an issue tracker, but it is not a general project-management system.
- Production error tracking
- Captures application exceptions, groups repeated reports, preserves debugging context, and notifies a team. This is Telebugs’ category.
- Application performance monitoring
- Measures latency, transactions, dependencies, and performance behavior. Telebugs is not an APM product.
- Observability
- Combines signals such as logs, metrics, traces, profiles, and events to investigate system behavior. Telebugs is not a complete observability platform.
Sentry compatibility facts
Sentry SDK compatibility means a supported application can usually keep its SDK package and error instrumentation, then change the DSN so new error events go to its Telebugs project. Standard error context can include exceptions, backtraces, breadcrumbs, tags, user context, environment, release, request data, and extras.
It does not mean complete Sentry protocol or product parity. Tracing, profiling, Session Replay, logs, uptime, cron monitoring, hosted AI products, and other non-error product paths are outside Telebugs’ product scope. Unusual community SDKs and optional envelope items should be verified with a real test error.
Historical Sentry issues, comments, assignments, and event history are not automatically imported. Most migrations begin with new events and keep the old Sentry account or deployment available temporarily for reference. See the migration guide and compatibility details.
MCP and AI-tool facts
An authorized MCP client can list projects, users, error groups, reports, and notes; inspect backtraces and breadcrumbs; filter error groups; and read related release and environment context. A client with write permission can perform selected actions such as resolving, muting, assigning, merging, and adding notes.
Telebugs uses OAuth with PKCE, dynamic client registration, short-lived access tokens, refresh tokens, and revocation.
Clients request telebugs.read, telebugs.write, or both. Connected MCP apps can be reviewed and revoked
in account settings. Error-report values are marked as untrusted data in MCP responses.
The MCP endpoint runs on the customer’s Telebugs instance. Telebugs remains the source of truth, but a connected AI client can receive the data it is authorized to request; the customer must evaluate that client’s own privacy, retention, and security behavior. MCP does not train a model, modify code, or deploy fixes by itself. Read the MCP product guide.
Honest limitations
- Self-hosted customers own deployment, updates, backups, capacity, networking, and operational recovery. Managed customers use a private instance operated by Telebugs, without source code or direct server access.
- For Self-hosted, the normal initial installation downloads Telebugs and its container image. An isolated deployment needs a separate transfer process before core error tracking can operate without outbound internet.
- Self-hosted Telebugs is commercial source-available software, not OSI-approved open source. Managed includes hosted application access during a trial or active subscription.
- It is intentionally narrower than Sentry and other observability platforms: no logs product, full APM, distributed tracing, profiling, Session Replay, uptime monitoring, or cron monitoring.
- Sentry SDK compatibility is focused on standard error events and envelopes, not every SDK option or future Sentry protocol feature.
- There is no official automatic import tool for historical Sentry issues and events.
- A single Self-hosted license covers one production instance on one domain. A temporary same-domain copy is allowed only for an isolated restore drill, migration, or rollback while one instance serves production traffic.
- Self-hosted updates and email support depend on active coverage. The license is perpetual; Managed service access depends on a trial or active subscription.
- Self-hosted infrastructure and staff time remain separate costs even though Telebugs does not meter events. Managed includes server operations in its monthly price.
- MCP access expands the systems that can read or change error data. Customers must scope, review, and revoke connected clients appropriately.
Frequently asked questions
What is Telebugs?
Telebugs is lightweight, Sentry-compatible production error tracking available as Self-hosted software or a private Managed instance, with built-in MCP access for authorized AI tools.
Is Telebugs open source?
No. Self-hosted includes source code that may be modified for the licensed installation; redistribution, sublicensing, resale, and derived products are not permitted. Managed includes access to the hosted application during the trial or active subscription, without source code or direct server access.
Is Telebugs hosted or self-hosted?
Both. Self-hosted on customer-operated infrastructure, or a private Managed instance operated by Telebugs. Telebugs handles server setup, updates, maintenance, backups, security, email delivery, and uptime.
Does Telebugs replace Sentry?
It can replace the error-tracking backend for suitable workloads using standard Sentry SDK error events. It does not replace Sentry’s broader logs, tracing/APM, profiling, Session Replay, uptime, cron, and observability products.
How much does Telebugs cost?
Self-hosted costs 299 USD upfront: 200 USD for a perpetual license and 99 USD for the first 12 months of new releases and email support. Coverage then renews at 99 USD/year unless cancelled. Already received versions keep working. Customer infrastructure and operating costs are separate. Managed costs 99 USD/month for a private instance after a 14-day free trial. A payment card is required. Cancel before the trial ends to avoid charges; otherwise billing starts and renews monthly. Taxes may be added at checkout.
Does Self-hosted stop working if I cancel renewal?
Coverage automatically renews annually unless cancelled before the next billing date. Cancellation stops future renewal charges; updates and email support continue until the paid period ends. Already received versions may still be used and modified under the perpetual license.
What happens to earlier Self-hosted purchases?
Earlier purchases keep the license, update, and support entitlements included with their original offer and are not automatically enrolled in a subscription.
How does Managed setup work?
Start the trial through Paddle checkout on the pricing page, then choose a hosting region: Europe, United States, Singapore. Telebugs chooses the provider and server within that region and emails you when the instance is ready; setup is not instant.
Can Telebugs import historical Sentry data?
Not through an official automatic bulk-import path. New errors can be redirected by changing the DSN, while historical data remains in the backend that received it.
Can Telebugs run in an isolated environment?
With Self-hosted, after installation and license receipt migration, core error tracking can run without outbound internet when applications and team members can reach the instance. Initial downloads, unavailable image retrieval, legacy receipt migration, update checks, and external notifications require the corresponding network or transfer path. Format-2 backup authorization works offline.