# Tindra

> Error tracking, performance monitoring, profiling, logs, and uptime and cron monitoring. One Go binary, one Postgres database. Self-host it free under the Elastic License v3, or run it managed by Blendbyte GmbH on dedicated EU infrastructure from $9/month.

Tindra speaks the Sentry ingest protocol, so any Sentry SDK works after a DSN change. It is built for small and medium teams rather than million-event-per-second scale, which is why it installs as one container instead of dozens. Managed data stays in the EU and is never replicated outside it. Plans have no overage billing: when the monthly event limit is reached, events pause until the next cycle.

## Pages

- [Tindra](https://www.tindra.sh/): product overview, pricing, and comparison
- [Product](https://www.tindra.sh/product): what each feature does, in detail

## Getting Started

- [Introduction](https://www.tindra.sh/docs/getting-started/introduction): Tindra tracks errors, monitors performance, captures logs, and watches your uptime and cron jobs. One Go binary, one Postgres database. Genuinely...
- [Quick Start](https://www.tindra.sh/docs/getting-started/quick-start): Get your first error event into Tindra in under five minutes.
- [Self-Hosting](https://www.tindra.sh/docs/getting-started/self-hosting): Run Tindra on your own infrastructure. One binary, one Postgres database.
- [FAQ](https://www.tindra.sh/docs/faq): Frequently asked questions about Tindra: the name origin, why we built it, pricing, self-hosting requirements, managed hosting, and who Blendbyte is.
- [Billing FAQ](https://www.tindra.sh/docs/billing/faq): Common questions about Tindra plans, pricing, event limits, and billing. No overages. Events pause at the cap, never charge extra.

## Error Tracking

- [Overview](https://www.tindra.sh/docs/error-tracking/overview): Tindra captures unhandled exceptions, logged errors, and manually captured events from your applications.
- [Issues](https://www.tindra.sh/docs/error-tracking/issues): An issue is a group of events that share the same error fingerprint. Tindra groups them automatically so you can triage one problem at a time instead...
- [Environments](https://www.tindra.sh/docs/error-tracking/environments): Environments let you separate events from different deployment contexts. Production, staging, local development. So you can focus on what matters.
- [Releases](https://www.tindra.sh/docs/error-tracking/releases): Tag your events with a release version so you can track when a bug was introduced and whether it has been fixed.
- [Source Maps](https://www.tindra.sh/docs/error-tracking/source-maps): Minified JavaScript stacktraces are unreadable. Upload source maps so Tindra can show you the original file names and line numbers.

## Performance

- [Overview](https://www.tindra.sh/docs/performance/overview): Tindra captures transaction traces from your application so you can find slow endpoints, identify database bottlenecks, and understand where time is...
- [Transactions](https://www.tindra.sh/docs/performance/transactions): A transaction is a single traced operation from start to finish. Click any transaction in the performance list to see the full span waterfall.
- [Profiling](https://www.tindra.sh/docs/performance/profiling): Profiling in Tindra: turn on your Sentry SDK profiler and get a flame graph on every traced transaction. Setup for PHP, Python, Node, Ruby and the browser.
- [N+1 Detection](https://www.tindra.sh/docs/performance/n-plus-one): Tindra automatically detects N+1 query patterns in your transaction traces and opens them as issues, so they show up alongside your errors without any...
- [Web Vitals](https://www.tindra.sh/docs/performance/web-vitals): Tindra captures Core Web Vitals from your frontend pages so you can track real-user performance.

## Logs

- [Log Viewer](https://www.tindra.sh/docs/logs/log-viewer): Tindra captures structured log entries from your applications alongside errors and transactions. Logs are searchable, filterable, and correlated to...

## Monitors

- [Cron Monitors](https://www.tindra.sh/docs/monitors/cron-monitors): Cron monitors let you track whether your scheduled jobs and recurring tasks are actually running. Create a monitor, ping it from your cron job, and...
- [Uptime Monitors](https://www.tindra.sh/docs/monitors/uptime-monitors): Uptime monitors probe HTTP and HTTPS endpoints on a regular schedule and alert you when something goes down or recovers.

## Alerts

- [Alert Rules](https://www.tindra.sh/docs/alerts/alert-rules): Alert rules notify you when errors spike, a new issue appears, log volume crosses a threshold, or a monitor goes down. Get notified via email, Slack...

## Integrations

- [MCP Server](https://www.tindra.sh/docs/integrations/mcp): Tindra ships a built-in Model Context Protocol server. Connect any MCP-compatible AI client (Claude Desktop, Cursor, Windsurf, and others) and query...

## SDKs

- [Laravel](https://www.tindra.sh/docs/sdks/laravel): Tindra uses the official Sentry Laravel SDK. No Tindra-specific package required.
- [PHP](https://www.tindra.sh/docs/sdks/php): Set up error tracking, performance monitoring and profiling in a plain PHP application with the Sentry PHP SDK and a Tindra DSN.
- [JavaScript](https://www.tindra.sh/docs/sdks/javascript): Set up browser error tracking, source maps, Web Vitals and profiling with the Sentry JavaScript SDK and a Tindra DSN. Works with React, Vue and more.
- [Node.js](https://www.tindra.sh/docs/sdks/nodejs): Set up error tracking, tracing and profiling in Node.js with the Sentry SDK and a Tindra DSN. Covers Express, Fastify, Koa and plain Node.
- [Python](https://www.tindra.sh/docs/sdks/python): Tindra uses the official Sentry Python SDK. No Tindra-specific package required. Works with Django, Flask, FastAPI, and plain Python.
- [Ruby](https://www.tindra.sh/docs/sdks/ruby): Tindra uses the official Sentry Ruby SDK. No Tindra-specific gem required. Works with Rails, Sinatra, and plain Ruby.
- [Go](https://www.tindra.sh/docs/sdks/go): Tindra uses the official Sentry Go SDK. No Tindra-specific package required. Works with any Go HTTP framework or plain Go applications.
- [Other SDKs](https://www.tindra.sh/docs/sdks/other): Tindra accepts events from any Sentry-compatible SDK. If your language is not in the list below, the full Sentry SDK catalog works without modification.

## Administration

- [Configuration](https://www.tindra.sh/docs/administration/configuration): All Tindra configuration is done via environment variables. No config files.
- [Projects & Quotas](https://www.tindra.sh/docs/administration/projects): A project is one application or service sending data to Tindra. Each has its own DSN, settings, and storage figures. This page covers creating...
- [API Tokens](https://www.tindra.sh/docs/administration/api-tokens): API tokens are per-project bearer tokens for programmatic access to Tindra. Use them to authenticate CI pipelines, scripts, the MCP server, or any...
- [User Management](https://www.tindra.sh/docs/administration/users): Invite team members, assign roles, and control what each person can access in your Tindra organization. Members are shared across all projects.
- [Authentication](https://www.tindra.sh/docs/administration/authentication): Tindra supports password login and OAuth/OIDC single sign-on.
- [PII Scrubbing](https://www.tindra.sh/docs/administration/pii-scrubbing): Tindra scrubs personally identifiable information from events before they are stored. Scrubbing runs at ingest time. Data that matches a rule never...
- [Health Overview](https://www.tindra.sh/docs/administration/health-overview): The overview tab is a live snapshot of your Tindra instance: database size, data volumes, retention, and quota usage. Check it before disk fills up...
- [Audit Log](https://www.tindra.sh/docs/administration/audit-log): The audit log records changes made by members of your organization: project creation, member invitations, settings changes, and more.
- [Passthrough DSN](https://www.tindra.sh/docs/administration/passthrough-dsn): Passthrough DSN forwards every inbound event to a second DSN after Tindra processes it. Useful for running Tindra alongside another monitoring service...
- [Upgrades](https://www.tindra.sh/docs/administration/upgrades): Tindra upgrades are a two-step process: pull the new image, restart the container. Migrations run automatically on startup.
- [Backup](https://www.tindra.sh/docs/administration/backup): Tindra stores all persistent data in two places: a Postgres database and a data directory (DATA_DIR) for file attachments. A complete backup needs both.

## Optional

- [Full documentation](https://www.tindra.sh/llms-full.txt): every page above concatenated as markdown