Deep.BI/Apache Druid
We keep patched Druid builds for five release lines at once, and one of our engineers created the Kubernetes operator that later moved into Apache Druid. The same engineers answer P0/P1 incidents in under 1 hour, any hour of the day.
100+ enterprises served, including
Atos, security and observability platform
"It has truly been a pleasure working with Deep.BI over the years. Their support for our security and observability platform, along with the underlying pipeline of Druid, Flink, Kafka, and NiFi, has been invaluable."
Ravi Raman, Global Head, AIsaac Product Engineering
Druid software we wrote
When a CVE lands or a fix can't wait for upstream, we patch the version you run, test it on your workload and hand you the build. Then we send the fix upstream. Everything stays Apache 2.0.
Patched-build targets on the 24/7 SLA + Maintenance plan and the Managed Service.
Patched builds we maintain
Merged into Apache Druid, for example
On 24/7 plans, every hour of the day, with no cap on incidents.
A slow Druid query can be a bad segment layout, an overloaded Historical, a Kubernetes limit or a dropped packet. We stay with it until we find the root cause.
Druid reads streams straight from Kafka and loads files in batch. We also support the systems that feed it and the tools that query it.
Swipe to see the full pipeline
Symptoms we see in production, and how we fix them.
One team from the first design to the next upgrade. Pick a stage.
We design ingestion, segment layout, rollup and tiering for your query patterns, and size Brokers, Historicals and MiddleManagers or Indexers to match.
Best forNew clusters and redesigns
We deploy Druid with the Kubernetes operator, on bare metal or in your cloud, and set up TLS, authentication and authorization before it carries production traffic.
Best forTeams going to production
Phased, with both clusters running side by side until the numbers match. Your 24/7 SLA starts before cutover. Deep Segment Reader reads existing Druid segments in Spark when data has to move or be backfilled.
Best forTeams leaving a vendor distribution
We tune segments, compaction, caching and query patterns on your workload before anyone adds hardware. Deep Predictive Cache adds an external cache layer for the dashboards that run the same queries all day.
Best forClusters that got slow or expensive
We plan and run Druid upgrades, test them against your workload first, and keep a rollback path open until the new version is stable. Our extensions are released for each Druid version, so they don't hold you back.
Best forTeams stuck on an old release
Compared on what matters after the contract is signed.
Swipe to compare
| Deep.BI | Run it in-house | Vendor distribution | |
|---|---|---|---|
| Engine | Upstream open source, plus custom fixes and features | Upstream open source | Vendor build on the vendor's release cycle |
| Cost as usage grows | Flat: set by node count, or by the hour pool | More headcount | Grows with your footprint |
| Fixes and CVEs | Patched builds under the SLA, fixes contributed upstream | Community timeline, no commitment | The vendor's release cycle |
| Problems across the pipeline | One team stays on it until the root cause is found | Separate expertise for every technology | Problems bounce between vendors |
| Leaving | End the support contract. The cluster keeps running. | No contract to exit | Migrate off the vendor build |
All four come with senior Druid engineers. They differ in who owns upgrades and who runs the cluster.
Swipe to compare plans
| 24/7 Enterprise SLA | 24/7 SLA + Maintenance | Managed Service | Support hours | |
|---|---|---|---|---|
| P0/P1 response | Under 1 h, 24/7 | Under 1 h, 24/7 | Under 1 h, 24/7 | Next business day, or under 1 h on the 24/7 option |
| Production incidents | No cap | No cap | No cap | From your hours |
| Upgrades and CVE fixes | From your hours | Included | Included | From your hours |
| Who runs the cluster | Your team | Your team, maintained by us | We do | Your team |
Or start with a fixed-price assessment
50 hours, $19,000. Move to a 24/7 plan within 90 days and we waive the onboarding fee.
On the 24/7 Enterprise SLA, the 24/7 SLA + Maintenance plan and the Managed Service, P0 and P1 incidents get a first response in under 1 hour, at any time of day, with no cap on production incidents. A senior Druid engineer handles the ticket from first response to resolution, and every incident ends with a root cause analysis. Support hours plans come with next business day response, or P0/P1 under 1 hour on the 24/7 option. Response targets are written into your agreement.
We support open-source Apache Druid, the Apache Software Foundation project under the Apache 2.0 license, on your cloud, on premises or on Kubernetes. If you run a vendor distribution today, we can support the move to open source and start your 24/7 SLA before cutover.
Yes. On the 24/7 SLA + Maintenance plan and the Managed Service, we monitor CVEs that affect Druid and its dependencies, assess the impact on your deployment and patch the version you run. We keep patched builds for five Druid release lines at once, so a security fix doesn't have to wait for an upgrade project. On the 24/7 Enterprise SLA, this work is billed from your pool of support hours.
All of them, including releases that are no longer current upstream. If you're on an older version, we keep it stable and patched while we plan the upgrade with you.
You end the support contract and your cluster keeps running. You run standard open-source Apache Druid on your own infrastructure, so there is no proprietary build or platform license to unwind. Notice periods and renewal terms are set out in your agreement.
Send your Druid version, cluster size and the problem using the form below. A Druid engineer reads it and replies.