Pricing
Triage is priced on the number of message providers you connect — not per seat, and never per message. Every licence is an annual term for a self-hosted deployment, so your messages never leave your infrastructure.
Community
For a single broker, run for as long as you like.
1 connected provider
- Inspect, transform, and replay by hand
- Dashboard and queue browser
- Destination and exchange graph
- Alerting
- AI diagnosis
- Replay automation
- Object storage
Team
For platform teams that want the babysitting automated away.
Up to 3 connected providers
- Everything in Community
- Alert sinks (Slack, webhook, email)
- Full replay audit trail
- AI diagnosis with your own LLM provider
- Replay rules and scheduled automation
- Priority email support
- Object storage
- Federation
- Cloud KMS key providers
Business
For estates where failures land in buckets as well as queues.
Up to 8 connected providers
- Everything in Team
- Poison-object remediation in S3, GCS, and Azure Blob
- Storage alert and replay rules, including storage-to-storage
- Federation
- Cloud KMS key providers
Enterprise
For multi-region estates and regulated environments.
Unlimited connected providers
- Everything in Business
- Federation across Triage instances
- Cloud KMS key providers (AWS, GCP, Azure)
- SSO / OIDC with role mapping
- Support SLA and custom connectors
- Implementation services and onboarding
Want to try the paid features first? Start a free 14-day evaluation with everything unlocked — no card required.
Licensing questions
What counts as a connected provider?
Each message broker or storage backend Triage is configured against — an SQS account, a RabbitMQ cluster, an Anypoint MQ organisation, an S3-compatible bucket — counts once, no matter how many queues sit behind it or how many messages pass through. Queue and message counts are deliberately not part of the price: a healthy system has an empty DLQ, and nobody should pay more during the incident where the tool earns its keep.
Do non-production instances burn a provider slot?
No. The licence is issued per organisation and covers unlimited Triage instances, so staging and dev deployments do not count against your provider limit or need a separate key.
What happens when the licence expires?
Triage keeps running. An expired licence logs an error and shows a banner, but it never locks replay — a DLQ tool that stops working on a lapsed renewal fails at exactly the moment you need it. Renewal is a conversation, not a kill switch.
Is my data sent anywhere?
No. Triage is entirely self-hosted. The licence key is a signed offline token — Triage never phones home, and your message payloads never leave your infrastructure.
How is the free Community tier different from the evaluation?
The 14-day evaluation unlocks every feature so you can test the whole product, including storage, federation, and KMS. Community is permanent but capped at one provider with manual inspect and replay only — the automation features (alerting, audit trail, AI diagnosis, replay rules) start at Team.
Can we pay by invoice?
Yes on Enterprise, and on request for Business. Get in touch and we will arrange purchase order and invoicing terms.