// For DBA Teams
Open source database support for DBA teams.
Your DBAs keep the decisions. We take the patch toil.
OSSeva works with your DBA team rather than replacing it. We ship patched, signed builds for the PostgreSQL, MySQL and MariaDB lines you still run, help plan the major upgrades, and give your team one escalation path across databases, caches and brokers. Priced per cluster.
What changes for the DBA lead
Less patch toil
Someone on your team tracks CVEs for every line you run, rebuilds packages for versions upstream has dropped and explains the scanner results to security. OSSeva ships signed builds for those lines instead. Your DBAs test them and roll them out the way they roll out any minor release.
Version sprawl you can live with
Applications move at different speeds, so most estates run several major versions at once. Patched builds for PostgreSQL 11 to 14, MySQL 5.7 and 8.0 and MariaDB 10.4 to 10.6 keep the older clusters covered while the newer ones carry on with community releases.
Upgrades on your calendar
End of life stops being the deadline. OSSeva Assure adds a written upgrade plan per engine: PostgreSQL to 17 or 18, MySQL 8.0 to 8.4 and then 9.7 using MySQL Shell's upgrade checker, with authentication and replication topology reviewed before the change window.
One escalation path
When an incident spans the database, the cache and the broker, your on-call DBA calls one vendor. OSSeva Operate adds 24/7 monitoring and a 15-minute P1 response, and patches Critical CVEs (CVSS ≥ 9.0) within 48 hours and High within 7 days.
How OSSeva works with an in-house DBA team
Your team keeps the work that needs knowledge of your applications. OSSeva takes the work that is the same in every estate.
Your DBA team
Decides when a build goes to production and runs the change window.
OSSeva
Builds, signs and tests patched releases, and sends CVE notifications with the fix status for your lines.
Your DBA team
Owns the go or no-go, the application testing and the cutover.
OSSeva
Writes the upgrade plan, runs the pre-upgrade checks and reviews configuration and topology (Assure).
Your DBA team
Stays the first responder, because it knows the applications and the data.
OSSeva
Takes engine-level escalations. With Operate, also watches replication, failover and backups around the clock.
Your DBA team
Answers the auditor's questions about the estate.
OSSeva
Supplies SBOMs and CVE remediation records for each build (Assure).
Your DBA team
Can hand it off, or keep it.
OSSeva
Operate covers rolling upgrades replica by replica, point-in-time recovery testing and quarterly capacity reviews.
When another vendor is the better fit
You depend on a vendor's own distribution
Oracle-compatible PostgreSQL, MySQL Enterprise components such as the Enterprise Firewall, or Redis Software's Active-Active replication are best supported by the vendor that builds them.
You want the database hosted for you
OSSeva supports databases you run on your own infrastructure. If you want a vendor to host and run them, a managed service from your cloud provider or a managed database platform fits better.
Frequently asked questions
Does OSSeva replace our DBAs?
No. OSSeva works alongside an in-house DBA team. Your DBAs keep schema design, query work, change approval and the knowledge of your applications. OSSeva takes on the work that does not need that context: building and signing patched releases, upgrade planning, and engine-level escalation.
Can we keep the binaries and data we run today?
Yes. OSSeva takes over support for the community binaries you already run. Patched builds stay on the same major version, so moving to one is the same as a minor update: replace the packages and restart on the same data directory and configuration, replicas first in a replicated topology.
Which database versions are covered?
Patched builds for PostgreSQL 11, 12 and 13, and 14 from its community end-of-life date of 12 November 2026; PostgreSQL 15 is covered on Assure and Operate now. MySQL 5.7 and 8.0, and MariaDB 10.4, 10.5 and 10.6. Current versions of each engine are supported too, and the same contract can cover Redis, Valkey, RabbitMQ, Kafka and MongoDB.
How do patched builds reach our servers?
As signed DEB and RPM packages, tarballs and container images, delivered through your own repository manager or registry. Your existing deployment tooling installs them.
Which tier fits a team that has its own DBAs?
OSSeva Patch if you need fixes for end-of-life lines and nothing else. OSSeva Assure adds upgrade planning, configuration and topology review, and audit evidence. OSSeva Operate adds 24/7 operations if you want cover outside your team's working hours.
How is it priced?
Per cluster, not per core, per GB or per node, so adding replicas or capacity does not change the support bill. Book a discovery call for a quote.
Keep your DBAs. Hand us the patch toil.
Bring your version inventory to a discovery call. A senior engineer will mark which clusters need patched builds and which upgrades to plan first, and we will send a quote.