Tellagen

Keep incident response
in one clear record.

Coordinate the response after an alert. Investigate with evidence, track customer impact, and carry the record into review.

See sample record (opens in a new tab)
Real Tellagen product captures of the incident board, Diagnosis, and Postmortem views.
Incident workspaceResponse → review
Incident board · active response
Incident board anchoring the connected mobile response workflow
Diagnosis · evidence review
Focused mobile crop of confirmed diagnosis evidence
Postmortem · review record
Focused mobile crop of the postmortem review record

Run investigations from Codex or Claude

Start the run in Tellagen. Pick it up on your computer. Your local client uses only configured tools and credentials. Tellagen saves returned checks and findings. Responders decide what enters the timeline.

Credentials stay local

Tellagen stores source names and setup instructions. It does not store Grafana tokens, kubeconfigs, passwords, cookies, or OAuth credentials.

Your local client chooses the tools

The client uses only the tools, scopes, and credentials that you configure.

Responders approve incident changes

Tellagen saves returned checks, evidence, gaps, and findings. Responders decide which findings become timeline events or actions.

Privacy policyData processing agreement

Choose a plan for your response team.

Tellagen is invite-only. Request access. We will email you when workspace creation is available.

Compare plans
Free
Free forever
EUR 0

Free forever

For small response teams that need one incident record.

  • 5 responder seats and 25 viewer seats
  • Search incidents closed in the last 30 days
  • 20 Tellagen-hosted timeline suggestions per day
  • Local investigations from Codex or Claude
Team
Pay per responder seat
EUR 15/responder/month

EUR 12/responder/month billed annually

For teams that respond often and need more seats and history.

  • 50 responder seats and 250 viewer seats
  • Search your complete incident history
  • Unlimited Tellagen-hosted timeline suggestions
  • Unlimited active API keys

Questions before you create an incident workspace.

Existing tools keep their jobs. Local access stays local. Responders review what enters the record.

Where do local investigations run?

A responder starts a run in Tellagen. A local AI client such as Claude or Codex picks it up through MCP. MCP lets the client call configured tools. The client reads Grafana, Kubernetes, GitHub, documentation, or CLI sources that you enable. It sends checks, evidence, gaps, and findings to the incident.

What data and access does Tellagen keep?

Tellagen stores datasource names, sanitized URLs, declared scopes, environment variable names, and setup instructions. It does not store or return local credentials. Connected sources and investigations can add context. Responders accept, edit, or skip each suggestion before it enters the incident record.

Does Tellagen replace PagerDuty or our alerting platform?

No. PagerDuty and other alerting tools still page responders. Tellagen handles the work after the alert. It coordinates the response, records the timeline, tracks diagnosis and customer impact, and supports response actions and the post-incident record.

What happens after we request access?

Tellagen records your request. We will email you when workspace creation is available. After you receive an invitation, start on Free without a card. Connect Slack, alerting, and customer systems over time.

Have a workspace ready for the next incident.

Tellagen is invite-only. Request access. We will email you when workspace creation is available.