Two ways to buy expert StarRocks support. An hour-based plan gives you a pool of senior engineering time at a fixed annual fee, whatever the size of your fleet. A 24/7 plan is priced per node and has no cap on production incidents. Both cover open-source StarRocks, every version, on cloud, on-prem or Kubernetes.
We quote every plan for your clusters after a short scoping call.
Get a quote for your clustersYou get a reserved StarRocks team for the year and an annual pool of engineering hours. Incidents, tuning, upgrades and development all draw from the same pool, so you decide where the time goes.
This model fits two kinds of teams. Small deployments that need expert help now and then. And large fleets run by a strong in-house team that wants senior StarRocks engineers behind it, where per-node pricing would not make sense.
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:
Swipe to see all plans →
Response targets are written into your agreement.
On the 24/7 plans we don't count tickets. Everything needed to keep production running as designed is included:
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 StarRocks specialists who work on complex production problems. We don't run a first-line help desk.
Not ready for an annual plan? Start with a fixed-price block of hours and use it for an assessment of your cluster before you choose a plan.
Swipe to see all columns →
Hours can be used for any StarRocks work, on a best-effort response.
Move to a 24/7 plan within 90 days and we waive the onboarding fee, because the assessment already did that work.
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 StarRocks nodes, how many clusters you run, and which are production and which are dev or test.
The same contract can also cover Apache Druid, Apache Flink and the pipelines around them, with one team across all of them.
