We calculate pricing based on the size of your environment you’re asking us to protect. We estimate size and complexity by applying a rough pricing metric against the specific modules our canaries are deployed into. Examples of these metrics for each module are outlined in the table below.

• Module

  Pricing metric
  Pricing metric

• Cloud (AWS, Azure)

  Environment size (servers, serverless functions)

• Workload (Kubernetes)

  Number of workloads (e.g. pods) protected

• Endpoint

  Number of endpoints protected

• Software Development lifecycle (CI/CD, Github)

  Number of builds protected

• Identity (Okta)

  Number of Okta users (i.e. headcount)

No, we price based on the size of the environments we deploy into. Effective use of security canaries relies on deploying enough canaries to cover your environment as it grows and evolves. An arbitrary limit on the number of canaries available may reduce the likelihood of detection. So our approach is to base pricing on the size of your environment, to ensure the canary deployment provides sufficient coverage to protect your systems.

Few attacks start in the most critical, production environments. Consequently, our recommendation is to deploy Tracebit across your organization, for early detection. However, the platform is designed to apply security canaries on a per account basis, so it is possible to protect only certain parts of your environment.

We’re a small team, primarily made up of our founders and founding team. You can request a live demo, or just ask for custom pricing - you’ll be talking with someone involved directly with the product.

There are a few ways to determine the coverage you’ll require. If you need help estimating the size of your environment, please submit the form above, and state “Please share resource guides” in the size of environment box above. We’ll email you instructions.