pricing

Three tiers. One price dimension: your cluster count.

Detect, auto-remediate, and report on every Kafka cluster you run. No per-seat counting, no per-event metering, no surprise overage lines.

Solo

One cluster, every playbook live.

$499

per cluster · billed monthly

  • 1 cluster, 14 default playbooks
  • Slack + PagerDuty delivery
  • Helm install in minutes
  • All Kafka distributions supported

Team

Most popular

Detect, auto-remediate, and report across the fleet.

$899

per cluster · billed monthly

  • Multi-cluster management
  • Cluster-wide Slack + PagerDuty routing
  • Consolidated weekly incident digest
  • Single sign-on (SSO)
  • Full audit log

Enterprise

Custom guardrails for regulated Kafka.

$1,499

per cluster · billed monthly

  • Custom playbook authoring
  • Regional data isolation
  • Dedicated customer success manager
  • SOC 2 evidence pack
  • 99.9% uptime SLA

Contact sales

We'll reply within one business day.

Every tier includes: full 14 default playbooks, every incident report, Slack + PagerDuty integrations, all Kafka distributions (Confluent / MSK / Strimzi / Apache), and a Helm install in minutes.

compare

Every capability, side by side.

A spec-level look at what is and isn’t included in each tier. Use it to pick the right plan without mapping marketing copy to your fleet.

Swipe horizontally to compare all three plans.

Cairn feature comparison for Solo, Team, and Enterprise plans.
CapabilitySoloTeamMost popularEnterprise
Kafka cluster coverageKafka clusters covered by one Cairn plan.1 cluster10 clustersUnlimited clusters
Kafka distributionsSupported across Confluent Platform, AWS MSK, Redpanda, Strimzi, and Apache Kafka.All supportedAll supportedAll supported
Incident reportsPlain-English reporting is generated when a remediation loop closes.Every incident reportEvery incident reportEvery incident report
AI remediation & playbooksCairn applies guardrailed playbooks before escalating a real decision.14 default playbooks14 default playbooks14 + custom authoring
Log retention windowHow long an incident’s raw logs stay queryable in the console.7 days30 days180 days
Alert channelsSlack + PagerDutySlack, PagerDuty, email, webhookSlack, PagerDuty, email, webhook, OpsGenie
Custom runbooksAuthor your own auto-remediation playbooks in YAML.Not includedNot includedIncluded
SSO / SAMLNot includedIncludedIncluded
SLA tierBest-effort99.5% uptime99.9% uptime
Support response timeReply window for product and rollout questions.≤ 1 business day≤ 1 business day< 1 hour, 24/7
Incident report retentionLong-term archive of incident reports for compliance.30 days1 year3 years
API rate limit60 req / min600 req / minCustom