See what changed after every deploy
Tessaline collects request timings and errors from your services and lines them up with your releases. When an endpoint slows down, the chart points at the version that did it.
14 days free. No card needed to start.
Ask questions in plain SQL
Every request, error and release is a table you can query. Save a query and it becomes a chart on your dashboard.
SELECT route,
percentile(duration_ms, 0.95) AS p95,
p95_change(route) AS change
FROM requests
WHERE service = 'checkout-api'
AND released_after('2.14.0')
GROUP BY route
ORDER BY change DESC
LIMIT 3;| Route | p95 | Change |
|---|---|---|
| /api/orders | 412 ms | +118 ms |
| /api/search | 268 ms | +54 ms |
| /login | 190 ms | +9 ms |
What you get
Everything is built around one question: what changed, and when.
- Release markers
- Every chart shows when each version went live, so a regression always has an obvious suspect.
- Error grouping
- Similar exceptions fold into one issue with a count, the first release it appeared in and the routes it affects.
- Alerts with context
- An alert names the route, the change against last week and the release that was running at the time.
- OpenTelemetry in, CSV out
- Send what your services already emit. Take any result back out as a file or through the API.
- Retention you set
- Keep raw events from 7 to 400 days and daily summaries for as long as you like.
- Access for the whole team
- Read-only links for stakeholders, full access for engineers and an audit log for admins.
Pricing
Pay for the number of services you watch. Every plan includes release markers and SQL queries.
| StarterFree | Team€49 per month | Business€190 per month | |
|---|---|---|---|
| Services | 1 | 10 | Unlimited |
| Raw event retention | 7 days | 30 days | 90 days |
| Alerts | Email, Slack, webhooks | All channels and on-call routing | |
| Single sign-on | Not included | Not included | Included |
| Start free | Start trial | Contact sales |
Questions
Do I need to change my code?
No. Run our collector next to your service, or point the OpenTelemetry data you already produce at Tessaline. Most teams see their first chart within an hour.
How do release markers work?
Tessaline reads the version from your deploy pipeline or from the service itself and marks the moment the new version started serving traffic.
Where is my data stored?
In data centers in Frankfurt. Data stays in the EU and is deleted when your retention period ends.
Can I export my data?
Yes. Any query result downloads as CSV, and raw events are available through the API for as long as you keep them.
What happens when the trial ends?
You move to the Starter plan unless you choose another one. Nothing is deleted.