Error tracking and performance monitoring: errors, traces, profiles, logs, uptime and cron.
Self‑host it in 30 seconds, or let us run a dedicated instance for you in the EU.
Error.The stack trace, the breadcrumbs, and the user it happened to.
Logs.Their structured logs. Same time range, same filters.
Trace.The request that broke, span by span.
Profile.The sampled flame graph. Which function, not just which query.
Pick an affected user and Tindra keeps them in view. Project, environment, user and
time filters follow you across issues, logs, traces and browser page loads.
Share the link and a teammate lands in the same spot.
Jane Doe, followed across her issues. Real product, seeded demo data.
The whole list. It fits on one poster.
Errors
Stack traces, breadcrumbs and release tagging, grouped into issues you resolve or ignore. Source maps get checked against real frames from your build.
Performance
Transactions, span waterfalls, Apdex and Web Vitals. Flame graphs from your SDK’s profiler, switched on or off per project. Profiles never count as events.
Structured logs
Search messages, inspect attributes, open the matching trace. Hit Alert on this and a focused search becomes a volume alert. See logs and alerts
Uptime and cron
HTTP and HTTPS probes with down and recovery alerts. Cron monitors that notice a missed run or a failed one.
Alerts
Rules that deliver to email, Slack, Discord, Microsoft Teams or a webhook. Delivery history is kept, and failed webhooks retry on their own.
MCP server
Built into the binary. Ask your AI assistant about stack frames, breadcrumbs and older occurrences. Project-scoped tokens stay read-only until you say otherwise.
Your own instance
Managed customers get a dedicated container and a dedicated Postgres. Not a row in a shared table, not a schema-per-tenant trick.
Sentry SDKs
Already on a Sentry SDK? Keep it and change the DSN. Guided setup waits until a test event is actually stored. Get your app connected
Your data stays in the EU. Not for backups. Not even by mistake.
Managed instances run entirely in the EU. Backups replicate to a second availability zone
in the same region. Object storage stays EU‑only. No US sub-processors.
Operated by Blendbyte GmbH, Berlin. We use Tindra in production ourselves.
Pick a number. It won’t change on you.
Every plan has a monthly event limit. Events are errors plus transactions. Logs, cron check-ins
and profiles don’t count. Hit the limit and ingestion pauses until the next cycle.
No overage, no auto-billing. Need more? Upgrade the plan.