This website uses cookies. By continuing to browse, you agree to our Privacy Policy.
  • Home
  • Pricing and Plans

Simple and scalable

Get started for free, upgrade when you love it
  • Individuals

  • Teams

  • Enterprise

(Free)

10 Nodes
1 User

Custom pricing

50 Nodes
25 Users

Custom pricing

Custom
Unlimited Users

Playbooks and Monitors

Auto-detection & alerting of K8s issues

check-icon

check-icon

check-icon

Dependency mapping

check-icon

check-icon

check-icon

Automated and guided investigation

check-icon

check-icon

check-icon

Assisted remediation

check-icon

check-icon

check-icon

Operations

Change tracking (intuitive timeline)

check-icon

check-icon

check-icon

Logs and metrics inspection

check-icon

check-icon

check-icon

Workload actions (SSH, Port Forwarding)

check-icon

check-icon

check-icon

Cost

Dynamic pod right sizing

-

-

check-icon

Cost allocation visibility

-

-

check-icon

Support & Access & Integrations

SLA

Kommunity

9x5

24x7

Tech Support

-

check-icon

check-icon

Dedicated Customer Success

-

-

check-icon

RBAC

-

check-icon

check-icon

SSO

-

-

check-icon

Integrations

-

check-icon

check-icon

Komodor API

-

check-icon

check-icon

Q&A

We calculate the pricing based on the average number of nodes in your clusters per annum. If you still have questions, please leave us a message and we will do our best to assist.

Yep, Komodor is fully SOC2 compliant.

Komodor only listens to changes – this means we only collect the metadata in order to track any changes that occur. We do not look at the underlying data and block out secrets automatically. You can also further customize your configuration to reduce any additional data or utilize Kubernetes RBAC to limit access to resources.

After a lot of research, we found this to be the best solution for the majority of our users. However, if this pricing model doesn’t fit your needs, please leave us a message and we will do our best to assist.

“Hands down, this is the best troubleshooting tool we have. We have teams using it so much now, that it’s starting to become part of their daily processes.”

Landon Orr, Staff Site Reliability Engineer
lacework
logz
votiro