// Open source database support consolidation
One contract for your open-source data stack.
One renewal date, one escalation path, including the versions upstream has dropped.
Most estates collect a support contract per technology: one for PostgreSQL, one for the cache, one for the message broker, and self-support for the rest. OSSeva replaces that contract sprawl with a single agreement across databases, caches, brokers, streaming and the runtime layer underneath. We also cover end-of-life versions with patched, signed builds, so consolidating does not force an upgrade first. Pricing is per cluster, not per core, per GB or per node.
Trusted globally by enterprises
What contract sprawl costs you
Each contract made sense when it was signed. Together they make every incident and every renewal harder.
Incidents cross vendor lines
A slow checkout can involve the database, the cache and the broker at once. With three vendors, each one checks its own piece, and your team ends up running the investigation.
Renewals never stop
Separate contracts mean separate renewal dates, price models and procurement cycles through the year. Some bill per core, some per node, some per GB, so growth in one place changes several bills.
Old versions fall outside every contract
Many vendors support only versions that upstream still maintains. The clusters you have not upgraded yet, often the most important ones, end up on self-support with nobody shipping fixes.
What OSSeva delivers
Inventory and version map
Every cluster, its version, where it runs and which contract covers it today, with the end-of-life date for each version on one page.
Transition contract by contract
OSSeva picks up each technology as its current contract ends, so you never pay twice for long and never have a gap.
Patched builds, including EOL lines
Signed builds for the versions you run, including lines upstream no longer patches, such as PostgreSQL 11 to 14, Redis 6.2 and 7.0, RabbitMQ 3.x, MongoDB 4.2 to 6.0, Elasticsearch 7.10.2 and 7.17, and ZooKeeper 3.4 to 3.7.
Migration planning and audit evidence
Upgrade and migration planning per technology, plus SBOMs and CVE remediation records your auditors can check.
One escalation path
24/7 operations across the whole stack, a 15-minute P1 response and a named engineer, with Critical CVEs (CVSS ≥ 9.0) patched within 48 hours and High within 7 days.
Runs where you run
Bare metal, VMs, any Kubernetes distribution and any cloud account. There is no platform to adopt first.
Your options, compared
| Option | What you get | Trade-off |
|---|---|---|
| Keep a contract per technology | Deep specialists for each product | Several renewals, several price models, and incidents that cross vendor lines. |
| A single-database vendor | Strong depth on one engine, often with its own enhanced distribution | Caches, brokers and streaming still need other contracts, and coverage usually tracks upstream support dates. |
| Your cloud provider's managed services | Hosted engines and support in the same bill | Only for workloads on that provider's services, on its version calendar. |
| OSSeva | One contract across the stack, including end-of-life versions, on your infrastructure | You run the infrastructure, or add OSSeva Operate for 24/7 operations. |
Coverage from the OSSeva technology pages for PostgreSQL, Redis, RabbitMQ, Kafka, MongoDB, Elasticsearch, ZooKeeper and Erlang/OTP, checked on 7 October 2026, and from the MySQL and MariaDB technology pages.
Frequently asked questions
What is open source database support?
A commercial agreement that gives you fixes, security patches and expert help for open-source databases you run yourself, so you are not relying on community forums and upstream release dates alone. OSSeva covers the databases and the caches, brokers and streaming platforms around them under one contract.
Which technologies does one OSSeva contract cover?
PostgreSQL, MySQL, MariaDB, Redis, Valkey, RabbitMQ, Apache Kafka, MongoDB, Elasticsearch with OpenSearch as a migration target, ZooKeeper, etcd, ClickHouse, Apache Pulsar, ActiveMQ and the runtime layer underneath, such as Erlang/OTP. The technologies page lists every version.
Do we have to upgrade before we consolidate?
No. OSSeva ships patched, signed builds for end-of-life versions, so you can move support first and upgrade on your own schedule.
Who supports PostgreSQL?
The PostgreSQL Global Development Group maintains it and fixes each major version for five years. Commercial support comes from cloud providers for their managed services and from support companies, OSSeva among them, for PostgreSQL you run yourself.
How is it priced?
Per cluster, not per core, per GB or per node, so adding capacity does not change the support bill. Book a discovery call for a quote.
What is third-party database support?
Support from a company other than the one that sells or maintains the database. For open-source software that is normal: the code is public, and OSSeva builds, patches and supports it for you.
Who is this for?
Teams running three or more open-source data or messaging technologies on their own infrastructure who want fewer contracts, one renewal date and one place to call when something breaks.
One contract, one renewal date, one escalation path.
Book a discovery call with your inventory and renewal dates, and we will map a transition and a quote.