Pricing
Open source support pricing.
Priced per cluster, not by the size of the machines.
OSSeva prices open source support per cluster for most technologies, across one contract for current and end-of-life versions. This page explains how a quote is built: the unit we count for each technology, what moves the number, and what each tier includes. We do not publish prices. Book a discovery call for a quote.
Trusted globally by enterprises
What OSSeva counts for each technology
Most technologies are priced per cluster. A few use the unit that matches how they run: per application server for Apache Tomcat, per application for Spring Boot, and per application runtime environment for .NET. Each technology page has the versions and tier scope behind its unit.
What moves the quote
How many units are in scope
The number of clusters, ensembles, application servers, applications or runtime environments you want covered, counted in each technology's unit from the table above. Adding capacity to a cluster does not change the count.
Which versions you run
Current versions and end-of-life lines are both covered. Lines the upstream project no longer fixes need OSSeva's patched builds, so the version mix shapes the backporting work in the quote.
Which tier you choose
Patch, Assure or Operate. The tier sets how much of the work OSSeva takes on, from signed patched builds up to running the system with you.
Whether you need 24/7 cover
Assure includes 24/7 reactive support when you raise an issue. Proactive 24/7 monitoring, the 15-minute P1 incident response SLA and engineers who run the system end to end come with OSSeva Operate. For a RabbitMQ estate, see managed RabbitMQ.
What your auditors ask for
SOC 2, HIPAA, PCI DSS and ISO 27001 evidence packages and a pen-test validation summary are part of Assure and Operate. The rules they answer are set out in audit evidence for end-of-life open source.
What each tier includes
The tiers are the same for every technology. The full scope for each project is on its technology page, and the tier comparison sets them side by side. Work that sits outside a tier is scoped separately: database consulting and a Dedicated Partner engineer, database migration and a fixed-scope database health check.
OSSeva Patch
Quarterly CVE patches for every covered version, out-of-cycle releases for CVSS 9.0+ issues, signed artifacts (GPG and Sigstore) through Helm, Maven or OCI registries, vulnerability disclosure notifications and a version compatibility matrix. No architecture review, compliance attestations or 24/7 operations.
OSSeva Assure
Everything in Patch, plus an annual configuration and architecture audit, version upgrade planning, a reference architecture, a named architecture consultant, a pen-test validation summary and compliance evidence for SOC 2, HIPAA, PCI DSS and ISO 27001, and 24/7 reactive support. Proactive 24/7 operations and the incident response SLA are part of Operate.
OSSeva Operate
Everything in Assure, plus 24/7 monitoring and alerting, a 15-minute P1 incident response SLA, a named senior engineer, runbooks, quarterly business reviews, capacity planning and rolling upgrades executed node by node. OSSeva Operate patches Critical CVEs (CVSS ≥ 9.0) within 48 hours and High within 7 days.
Response and patch targets
The same for every covered technology.
| Target | Commitment | Tier |
|---|---|---|
| Critical CVE patched (CVSS 9.0 or higher) | Within 48 hours | Patch and above |
| High CVE patched | Within 7 days | Patch and above |
| Reactive support | 24/7 when you raise an issue | Assure and above |
| P1 incident response | 15 minutes, 24/7 | Operate |
Buying through procurement
- One contract for software, services and operations: one supplier review, one security questionnaire and one escalation path.
- One pricing unit: per cluster for most technologies, so adding cores, memory or replicas does not change the support bill.
- Signed builds, an SBOM per build and CVE remediation records come with OSSeva Assure for your audit and vendor risk teams.
The procurement guide lists what to require from any open source support vendor.
How other support is usually priced
Support vendors and cloud services count different things. The unit decides how the bill grows, often more than the first-year price does.
By CPU core count
Common for commercial database and middleware subscriptions. The bill follows the hardware, so more replicas or bigger machines raise it even when the support work stays the same.
By node or server
Each broker, replica or server is a line item. High availability and scale-out add cost with every node.
By data volume or throughput
Some subscriptions count gigabytes stored, memory held, messages or throughput. The cost moves with traffic and retention, which makes it hard to forecast.
Usage-based cloud services
Managed database services bill for instance hours, vCPUs, storage and I/O, with the provider's support attached. That support covers only instances on that service, on its version calendar.
Per cluster (OSSeva)
One unit for each system that has to stay patched and running, whatever its size. Any of these models can come out cheaper for a particular estate, which is why the calculator below works from your own figures.
Compare with your own figures
The database support cost calculator adds up what your support contracts, commercial licences, team time on patches and upgrades, and renewal cycles cost each year, using only the numbers you enter. It holds no vendor prices, ours included, and the arithmetic runs in your browser. Enter an OSSeva quote to see the net difference over one year and three.
How much does RabbitMQ support cost?
It depends on how many clusters you run and the tier you choose. OSSeva prices RabbitMQ support per application cluster, not by CPU core count, and Erlang/OTP support comes with it at no additional cost. Book a discovery call for a quote.
How much does PostgreSQL extended support cost?
OSSeva prices PostgreSQL support per cluster. The same contract covers patched builds for 11, 12 and 13, and for 14 after its community end of life on 12 November 2026, and the tier sets how much of the work OSSeva takes on. The database support cost calculator compares it with what you pay today, from your own figures. Book a discovery call for a quote.
Is OSSeva priced by CPU core count?
No. Most technologies are priced per cluster, so adding cores, memory or replicas to a cluster does not change the support bill. Tomcat is priced per application server, Spring Boot per application, .NET per application runtime environment and Node.js per application runtime.
How much does MongoDB support cost?
OSSeva prices MongoDB support per replica set or cluster, and the tier you choose, Patch, Assure or Operate, sets what is included. Book a discovery call for a quote.
How much does Redis support cost?
OSSeva prices Redis support per instance cluster, not per GB of memory or per operation. The quote depends on how many instance clusters you run, their versions and the tier. Book a discovery call for a quote.
How much does Kafka support cost?
OSSeva prices Kafka support per cluster, not per broker, partition or throughput tier. Adding brokers to a cluster does not change the count. Book a discovery call for a quote.
Does OSSeva publish a price list?
No. A quote depends on the units in scope, the versions, the tier and the hours of cover, and a list price would not describe your estate. Book a discovery call for a quote, then put it in the database support cost calculator next to what you pay today.
What do we need for a quote?
A list of the technologies, versions and clusters or other units you want covered, the tier you are considering, and whether you need 24/7 cover or compliance evidence. Bring your current contracts and renewal dates too, and we will price the same coverage line by line.
Get a quote
Get a quote priced per cluster.
Book a discovery call with your technologies, versions and clusters, and we will price the coverage line by line.
Prefer to talk or read more first?