We use cookies to ensure that we give you the best experience on our website. By continuing to use the website you agree for the use of cookies for better website performance and a personalized experience.

Apache Druid support plans and pricing

Two ways to buy expert support for open-source Apache Druid: a pool of senior engineering hours, or a 24/7 plan with no cap on production incidents. Both cover every Druid version, on cloud, on-premise or Kubernetes, from engineers who have supported 300+ production clusters.

We quote every plan for your clusters after a short scoping call.

Get a quote for your clusters

Which model fits your team

Hour-based plans: priced on team capacity, not node count

You reserve senior Apache Druid engineers for the year and get an annual pool of hours. Incidents, upgrades, tuning and advisory work all draw from the same pool, so you decide where the time goes.

It fits small deployments that need expert help now and then, and large fleets run by a strong in-house team that wants Druid specialists behind it, where per-node pricing would not make sense.

  • Response: next business day, or P0/P1 under 1 hour, 24/7
  • Price: an annual availability fee plus the hour pool. Node count does not change the price.
  • Unused hours roll over to the next term when you renew.

24/7 plans: priced per node, no incident cap

For production clusters the business depends on. P0/P1 response under 1 hour, 24/7, and no cap on production incidents. Every incident gets a root cause analysis and a post-incident review. You pay a fixed annual fee for an agreed node count, so the price does not move with ticket volume.

Three levels, by how much of the platform you hand to us:

  • 24/7 Enterprise SLA. Incident response for clusters your team runs. Also works as a tier-2 layer behind your own on-call.
  • 24/7 SLA + Maintenance. Adds upgrades, CVE fixes and custom releases on the version you run. The plan we recommend for production.
  • Managed Service. We run the cluster day to day: monitoring, scaling, configuration and incidents.

Plan comparison

Swipe to see all plans →

Support hours plan
24/7 Enterprise SLA
24/7 SLA + Maintenance
Managed Service
How it's priced
Annual fee + hour pool
Per node, annual
Per node, annual
Per node, annual
P0/P1 response
Next business day, or under 1 hour, 24/7
Under 1 hour, 24/7
Under 1 hour, 24/7
Under 1 hour, 24/7
Production incidents
From your hours
No cap
No cap
No cap
Root cause analysis and post-incident review
From your hours
Included
Included
Included
Permanent fixes for defects
From your hours
Included
Included
Included
CVE monitoring and impact assessment
From your hours
From hours
Included
Included
CVE fixes and patched builds
From your hours
From hours
Included: Critical within 7 days of a public fix, High within 30 days, Medium and Low in the next scheduled upgrade
Included
Upgrades
From your hours
From hours
Included: one major and all minor upgrades per cluster per year
Included
Custom releases
From your hours
From hours
Included
Included
Day-to-day operations
Your team
Your team
Your team
Deep.BI
Monitoring, scaling, configuration
Your team
Your team
Your team
Deep.BI
Incident and SLA reporting, service reviews
From your hours
Included
Included
Included
Performance tuning projects, capacity planning
From your hours
Support hours
Support hours
Included within the agreed scope
Migrations, new features, training
From your hours
Support hours
Support hours
Support hours
Who runs the cluster
Your team
Your team
Your team, maintained by us
We do
Best for
Occasional expert help, or large fleets with a strong in-house team
Production clusters, or a tier-2 layer behind your on-call
Production clusters that must stay secure and current
Teams that want to hand off operations

Response targets are written into your agreement.

What "no cap" covers

On a 24/7 plan you raise as many production incidents as you need to, and every one gets a root cause analysis and a post-incident review. These are the Druid problems we work on most:

  • Kafka supervisors going unhealthy, and ingestion tasks failing with no obvious cause
  • A Coordinator that is stuck or has no leader, and a Router that cannot find the Broker after a restart
  • Broker and Historical processes running out of memory
  • Queries that used to return in under a second taking tens of seconds, and 504 timeouts on joins and unions
  • Segments spread unevenly across Historicals, and Historicals running out of disk
  • Autocompaction colliding with ingestion, and no safe way to purge unused segments
  • Silent data loss and silently wrong results, the failures you cannot see from the outside

What's not included is new work: architecture and design, proactive performance projects, capacity planning, migrations, new features and extensions, and training. That work is billed as support hours. We classify every ticket as an incident or a consulting request and tell you which, so you always know what draws from your hours.

Our engineers are senior Apache Druid specialists who work on complex production problems. We don't run a first-line help desk.

Your Druid version, maintained

On 24/7 SLA + Maintenance and Managed Service we maintain the Druid version you actually run, rather than asking you to upgrade before we can help.

  • CVE monitoring and impact assessment for the version you run
  • Backports of upstream Apache Druid fixes into the version line you are pinned to
  • Custom releases built for your environment
  • Fixes we write are contributed upstream to Apache Druid
  • Druid extensions we wrote ourselves, such as query routing to deep storage and exact distinct counts, plus patched builds of upstream extensions, kept current across Druid versions

Some are open source on GitHub. Others are private, built for a single client's clusters.

Critical CVEs get a patched build within 7 days of a public fix, High within 30 days, and Medium and Low in the next scheduled upgrade. On the plain 24/7 Enterprise SLA, this work is billed from your support hours.

Fixed-price starting points

Not ready for an annual plan? Start with a fixed-price block of hours. The prices are the same for Apache Druid, StarRocks and Apache Flink.

Swipe to see all columns →

Hours
Price
Typical use
Cluster assessment
50
$19,000
Configuration and performance review of one cluster, with written findings and a prioritized list of changes
Assessment and implementation
100
$36,000
The assessment, plus hands-on work to apply the changes we recommend

Hours can be used for any Druid work, on a best-effort response. Typical uses:

  • A configuration review before a major version upgrade, to find breaking changes before they reach production
  • Segment granularity and partitioning for the queries you actually run
  • JVM heap, direct memory and buffer sizing across Brokers, Historicals and MiddleManagers
  • A plan for killing unused segments and cleaning up deep storage
  • A stress test to measure what the cluster can take before you scale out
  • A disaster recovery review with a live failover test and measured RTO and RPO

Move to a 24/7 plan within 90 days and we waive the onboarding fee, because the assessment already did that work.

What your quote depends on

For an hour-based plan, the quote depends on the response time you need, the technologies covered and the size of the hour pool.

For a 24/7 plan, it depends on the number of Druid nodes, how many clusters you run, and which are production and which are dev or test.

The same contract can also cover StarRocks, Apache Flink and the pipelines around them, with one team across all of them.

Contracts and procurement

  • We sign NDA, MSA and SOW, and complete your security and vendor questionnaires with your procurement and legal teams.
  • Ending support doesn't strand your cluster. It keeps running on standard open-source Apache Druid on your own infrastructure. Notice and renewal terms are in the agreement.
  • Clients on SLA plans get incident and SLA reporting and regular service reviews.
  • Engineers in the USA, Europe, India, Brazil and the Philippines cover the clock.

FAQ

•

Why don't you publish plan prices?

•

Which Druid versions do you support?

•

Can you patch a CVE without forcing an upgrade?

•

How is this different from a commercial Druid distribution?

Tell us about your clusters

We'll recommend a plan and send a quote.

Let's help you

run Druid cheaper and quieter

Contact us:
Email:
druid@deep.bi

Get in touch and we'll reach back out to you soon!

Deep.BI needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Privacy Policy.
Thank you! Your submission has been received!
We’ll get back to you shortly!
Oops! Something went wrong while submitting the form.
Please try again.
Contact information:
Email:
druid@deep.bi