Canonical public product facts
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.0
- Product status
- Commercially available; current documented release 1.18.0
Canonical definition
Telebugs is a lightweight, self-hosted production error tracking product for teams that want Sentry SDK compatibility, control of their error data, predictable one-time licensing, and authorized MCP access to production error context.
Scope and source precedence
This page is a maintained factual summary of the current public product, including Telebugs 1.18.0. It is not a substitute for the documents that govern legal rights, the current offer, or operational details.
- The license agreement controls legal rights and restrictions.
- The pricing page and 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, stack traces, breadcrumbs, releases, notifications, notes, retention, and triage.
- Teams able and willing to operate a Docker-based deployment on infrastructure they control.
- Teams already using compatible Sentry SDK error instrumentation or comfortable adopting it.
- Teams prioritizing direct control of production error data and retention.
- Bootstrapped teams, agencies, and organizations managing multiple projects on one licensed instance.
- Teams wanting approved AI coding tools to inspect error context through MCP.
Not best for
- Teams requiring a fully managed hosted service with no server operations.
- 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 unable or unwilling to own deployment, updates, backups, storage, networking, and access review.
- Teams requiring automatic historical Sentry issue and event import; Telebugs has no official bulk import path.
Key product facts
| Primary category | Self-hosted production error tracking |
|---|---|
| Hosting model | Customer-operated self-hosted software. Telebugs does not offer a managed Telebugs cloud service. |
| Deployment | Docker-based installation on customer-controlled infrastructure. The documented installer downloads and runs Telebugs as a Docker container. |
| Documented recommended minimum | 1 CPU core, 1 GB RAM, and 40 GB disk. Workload, retention, attachments, and traffic determine practical requirements. |
| 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. |
| Offline operation | After installation, core error tracking can run without outbound internet. The normal initial download and automatic update path require connectivity unless installation artifacts are transferred separately; update checks can be disabled and updates performed manually. |
| Collaboration | Multiple team members, project access controls, assignment, notes, notifications, and bulk triage actions. |
| Customization and source | Source code is provided after purchase and may be modified for the licensed installation; redistribution, sublicensing, resale, and derived products are not permitted. |
Commercial facts
| Price | $299 USD as a one-time purchase. Taxes can be added at checkout. |
|---|---|
| License scope | One Telebugs instance on one domain. |
| Projects | Unlimited within the licensed instance. |
| Teammates | Unlimited within the licensed instance. |
| Event billing | No Telebugs per-event charge. Server capacity, storage, retention, and ingest protection are practical limits. |
| Updates | All 1.x releases. |
| Support | Email support for ordinary installation, update, and product questions. |
| Refund policy | Not refundable after downloadable source software is delivered. |
| 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.
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, stack traces, 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
- Telebugs is self-hosted only. Customers own deployment, updates, backups, capacity, networking, and operational recovery.
- 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.
- Telebugs is commercial source-available software, not OSI-approved open source.
- 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 license covers one instance on one domain; more installations require more licenses.
- Infrastructure and staff time remain real costs even though Telebugs does not meter events.
- 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 a lightweight, self-hosted production error tracking product for teams that want Sentry SDK compatibility, control of their error data, predictable one-time licensing, and authorized MCP access to production error context.
Is Telebugs open source?
No. Telebugs is commercial software. Buyers receive source access and modification rights for their licensed installation, but the license does not permit redistribution, sublicensing, resale, or derived products.
Is Telebugs hosted or self-hosted?
Self-hosted. Customers install Telebugs on infrastructure they control. Telebugs does not currently offer a managed hosted Telebugs service.
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?
$299 USD once for one instance on one domain, plus the customer’s infrastructure and operating costs. Taxes may be added at checkout.
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?
After installation, core error tracking can run without outbound internet when applications and team members can reach the instance. The normal installer downloads Telebugs and its container image, so an isolated environment needs a separate transfer process. Disable update checks and plan manual updates.