DBA services

Database administration services, fully run by senior engineers

Senior OSStend engineers take over the DBA function for the databases you already run: co-managed on your infrastructure, in your cloud account or your data center, or fully managed in OSStend's cloud.

45 minutes with an engineer: we review your workload and sketch the design.

  • Operated by AceMQ: 160+ customers, 10+ years
  • 24/7 on-call engineers
console.osstend.com / acme-corp / dba-run

An example scope file for a co-managed engagement, with illustrative values:

# DBA services
service: dba-run
engines: [postgresql, mysql]
tier:    co-managed
target:  customer-aws-account
scope:   [monitoring, tuning, backups, upgrades, on_call]
upgrade_window: "Sun 02:00-04:00 CET, after change freeze"
on_call: 24/7
osstend.yaml (example)Design signed off

Database administration services from OSStend put senior engineers in charge of the DBA function for your databases: monitoring, tuning, upgrades, backups and 24/7 on-call. They suit teams that keep their databases but need the work run for them, co-managed on your infrastructure or fully managed.

160+AceMQ customers
10+Years running these systems
24/7Engineers on call
3Places it runs: our cloud, yours, your data center
Engines we run, on the platforms you already use
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Valkey
  • OpenSearch
  • Kafka
  • RabbitMQ
  • AWS
  • Google Cloud
  • Azure
  • Kubernetes
  • OpenShift
  • Prometheus
  • Grafana
  • Datadog
  • Dynatrace
  • Splunk
Built for your workload

What database administration services cover

Database administration services from OSStend cover monitoring, tuning, backups and recovery, upgrades, capacity and 24/7 incident response for PostgreSQL, MySQL, Redis or Valkey and OpenSearch, on the databases you already run. OSStend engineers also take MongoDB co-managed, and agree the scope with you first.

AreaWhat OSStend engineers do
Monitoring and alertingMetrics and alerts forwarded to your Datadog, Dynatrace, Splunk or Prometheus, with thresholds set per workload and engineers acting on them.
Performance tuningQuery, index and configuration review against the real workload, including slow-query analysis.
Backups and recoveryBackup schedules and recovery points set to your recovery targets, with point-in-time recovery where the engine supports it.
Upgrades and patchingVersions and patches planned around your change calendar and never forced.
Capacity and sizingSizing reviews as data and traffic grow, so storage and compute follow measured load.
Incidents and on-call24/7 response from named engineers who know your design, with an SLA written into your contract.
EnginesPostgreSQL, MySQL, MongoDB, Redis or Valkey, and OpenSearch.

There is no fixed menu here: the engines, versions and configurations your workload needs are written into the design you sign off before anything is built, and that design is what OSStend runs.

Database support services: what is included and what is not

OSStend's database support services cover the daily operation, the changes, the incidents and the performance review of the databases you already run. Application code, and any infrastructure you own, stay with your team unless the scope says otherwise.

AreaIncludedNot included unless agreed
Daily operationsHealth checks, alerts and verified backups.Work on systems outside the agreed scope.
ChangesVersion upgrades on your calendar and configuration changes.Changes outside your change calendar.
Incidents24/7 on-call response and a root-cause write-up.Faults in your application or network.
PerformanceSlow-query review and index advice.Rewriting application queries.
Application codeOSStend reviews queries and tells you what it finds.Your team owns and changes the code.
Infrastructure you ownOn co-managed setups OSStend operates the database on your hosts.Hosts, storage and network stay yours.

Database administration services or hiring a DBA

Hire a DBA when the database is your product's core and you need someone in every design meeting. Use a database administration service when you want 24/7 cover across several engines without a single person's hours and skills setting the limit.

FactorHire a DBADatabase administration service
Coverage hoursOne person's working hours.24/7 on-call engineers.
Engines coveredOne person's skills.PostgreSQL, MySQL, Redis or Valkey and OpenSearch.
Holidays and turnoverA gap when the person is away or leaves.A named team that knows your design.
Cost modelSalary and benefits. The US Bureau of Labor Statistics lists a median of $126,760 a year for database administrators and architects in May 2025 (BLS Occupational Outlook Handbook, checked 15 Nov 2026).Quoted per scope.

Hire in-house when the database is your product's core and you need someone in every design meeting.

How database administration services are priced

Database administration services are quoted per scope: the number and size of databases, the engines, the hours of cover and whether OSStend also runs the infrastructure.

Engines and number of databases
each engine and cluster under management.
Data size and change rate
how much data there is and how fast it changes.
Cover and response terms
written into the contract.
Co-managed or fully managed
whether OSStend also runs the infrastructure.

See pricing for how the model applies across every engine.

Compare

Where turnkey database services stop

Turnkey database services automate the platform. The DBA function around it, such as tuning for your queries, planning upgrades and owning incidents, still needs people, and a team without a DBA carries that work alone or lets it slip.

Illustrative: plan names and shapes stand in for any provider's menu.
AreaWhat a plan fixesWhat OSStend does instead
PlatformThe infrastructure and a set list of settings.Runs the database you already have, wherever it is, or runs it in OSStend's cloud.
TuningLeft with your team.Engineers tune queries, indexes and configuration against the workload.
Upgrade timingThe provider's schedule.Your change calendar.
IncidentsLeft with your team, or a ticket queue.Named engineers on call 24/7.

Plan scope differs by provider and change over time. Treat each provider's current documentation as the source for what it covers.

How it works

Design. Move. Run. for database administration

OSStend works in three steps. An engineer designs the cluster and you sign it off, OSStend runs the migration and owns the cutover, and named engineers then run it 24/7.

  1. Design

    An engineer reviews your database estate: engines and versions, sizes, backup and recovery set-up, monitoring, runbooks and where each database runs. The review produces the scope of work, and you sign it off before OSStend changes anything.

  2. Move

    OSStend takes over operations in place, with monitoring, access and runbooks connected first, or moves a database to a new cluster with zero downtime as the plan. Both sides stay live until you switch.

  3. Run

    Named engineers run the DBA function 24/7: monitoring, tuning, backups, upgrades on your calendar, capacity reviews and incident response, with an SLA written into your contract.

Deployment

Deployment and service levels

DBA services run co-managed on infrastructure you own, in your cloud account or your data center, or fully managed on dedicated clusters in OSStend's cloud. The first keeps the databases where they are; the second moves them.

AceMQ engineersOne on-call team, one contract, wherever it runs
  • Dedicated in OSStend's cloud

    Single-tenant clusters in the region you choose, on Google Cloud or AWS. Multi-zone by default, with cross-zone traffic planned up front.

    Fully managed
  • In your cloud account

    OSStend operates inside your account and VPC, so the data, the billing and the security boundary stay with you. AWS first, then Azure and Google Cloud.

    Fully managed
  • In your data center

    Cloud repatriation, on-premises and air-gapped sites, on Kubernetes, OpenShift or Windows hosts, with FIPS where required. Delivered through an operator on your cluster, with supported charts and images.

    Co-managed

Fully managed deployments carry an uptime commitment. Co-managed deployments carry a 24/7 response-time commitment, because you own the infrastructure. The service levels page sets out the tiers, and deployment shows each option in detail.

Uptime and response figures are set per plan and written into your contract. AceMQ, which operates OSStend, sets its support response targets from 15 minutes, by plan.

Operated by AceMQ

Proof from AceMQ's operating record

OSStend is operated by AceMQ, a company with 160+ customers, 10+ years of running open-source infrastructure and engineers on call 24/7. Those company facts match acemq.com.

Operated by AceMQCompany figures, as published on acemq.com
160+AceMQ customers
10+years operating
24/7on-call engineers

AceMQ names a customer only with that customer's written permission, so most of this record stays anonymous. Ask for a similar workload in the 45-minute review.

Pricing

Pricing for database administrator services

Pricing for database administrator services follows four drivers: the engine, the cluster size, the SLA tier and where it runs. An engineer prices the specific design after a workload review. There is no free tier and no card sign-up.

Engine
each engine has its own operating profile, and several engines share one contract and one on-call team.
Cluster size
the number of databases and clusters under management and their size.
SLA tier
fully managed or co-managed, and the uptime or response-time commitment attached.
Where it runs
OSStend's cloud, your cloud account or your data center.

Prices are quoted per design, after the workload review, so the figure is for the cluster you need rather than a plan size. Send the engine, rough size and where it must run, and the engineer prices that design.

The pricing page shows the model that applies across every engine.

Enterprise only

When to contact OSStend, and when not to

Contact OSStend when your DBA work has outgrown a standard plan or has to run somewhere a plan cannot. If the workload fits a standard plan, or you want a free tier or card sign-up, a turnkey service is the better choice.

Contact us if

  • You keep your databases but have no DBA, or one person on call alone.
  • Upgrades, tuning and backup checks keep slipping behind feature work.
  • You run several engines and want one team and one contract across them.
  • You want the DBA function run for databases in your cloud account or your data center.
Talk to an engineer

Not a fit if

  • Your databases fit a standard managed plan and you have the people to run them.
  • You want a free tier, or to sign up with a card. OSStend starts with a conversation with an engineer.
  • You want to hire a permanent in-house DBA and keep the work internal.
FAQ

Questions about DBA as a service and database management services

These are the questions IT and engineering leaders ask most before handing the DBA function to a service.

Talk to an engineer →

What is DBA as a service?

DBA as a service means a provider's engineers carry the DBA function for databases you run, instead of you hiring and covering it. OSStend's database management services take over monitoring, tuning, backups, upgrades and 24/7 on-call for PostgreSQL, MySQL, MongoDB, Redis or Valkey and OpenSearch.

What do database administrator services include?

Database administrator services cover the work that keeps a database healthy: monitoring, performance tuning, backups and recovery, upgrades and patching, capacity reviews and incident response. The scope is agreed in a review of your estate before any change is made.

How is a DBA service different from a managed database service?

A managed database service runs the platform from a fixed menu. A DBA service runs the administration of the databases you already have, wherever they run, and can also move them into an OSStend-run cluster. The two can be combined across engines on one contract.

Can OSStend take over a database that is already in production?

Yes. The engineers start with a review of the current set-up, connect monitoring, access and runbooks, and then take over operations in place. A move to a new cluster is optional and uses replication to avoid downtime.

Which databases are covered?

PostgreSQL, MySQL, MongoDB, Redis or Valkey and OpenSearch. The covered engines and versions are listed in the scope that you sign off.

What is the difference between database administration services and database support services?

Administration is the planned, ongoing DBA work: monitoring, tuning, backups and upgrades. Support is the response when something breaks. OSStend's service covers both, with the scope agreed first.

Can you work with the monitoring we already have?

Yes. Metrics and alerts are forwarded to your Datadog, Dynatrace, Splunk or Prometheus, with thresholds set per workload and engineers acting on them.

How are database administrator services priced?

The price depends on the engines, the number and size of the clusters, the SLA tier and where they run. The pricing page sets out the model, and an engineer prices the specific scope after a review.

Talk to an engineer

Talk to an engineer about your DBA workload

45 minutes with an engineer: bring your current setup, and the engineer reviews the workload and sketches the design.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.