Database hosting

Database hosting services: dedicated, in your cloud or ours

Dedicated clusters for the databases you run in production, hosted in OSStend's cloud, in your own cloud account or in your data center, and run 24/7 by OSStend engineers.

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

Database hosting services run your database on infrastructure you do not manage yourself. OSStend hosts PostgreSQL, MySQL, Redis or Valkey, OpenSearch, Kafka, RabbitMQ and ClickHouse on dedicated clusters designed for the workload, in OSStend's cloud, your cloud account or your data center, with engineers on call 24/7. For who runs the database day to day, see the managed database service page.

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
Compare

What do database hosting services include?

Database hosting services provide the servers or cloud capacity a database runs on, and the amount of operation that comes with it ranges from none to the full job. At the full end, hosting also covers backups, failover, patching, monitoring and 24/7 response, which is what OSStend provides.

AreaWhat OSStend hosting covers
CapacityDedicated, single-tenant clusters sized to the workload, not a shared plan size.
PlacementOSStend's cloud, your cloud account or your data center, set per workload.
AvailabilityReplication and failover designed for your recovery targets, across zones where the platform allows.
Backups and recoveryBackup schedules and recovery points set to your targets, with point-in-time recovery where the engine supports it.
Patching and upgradesVersions and patches planned around your change calendar and never forced.
MonitoringMetrics and alerts forwarded to your Datadog, Dynatrace, Splunk or Prometheus, with engineers acting on them.
On-callNamed engineers 24/7. See service levels.

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.

Shared, dedicated or managed hosting: what is the difference?

The three terms describe who shares the hardware and who runs the database. Shared hosting divides one server between many customers, dedicated hosting gives you the server or cluster, and managed hosting adds an operations team on top of either.

TypeWho shares the hardwareWho runs the databaseFits when
Shared hostingMany customers on one serverYou, within the host's limitsA small site or prototype with light load.
Dedicated server or cluster, self-managedNobody: the capacity is yoursYour teamYou have database engineers on call and want full control.
Dedicated and managedNobody: the capacity is yoursThe host's engineers, to a design you sign offThe database matters to the business and your team should not carry the pager.

How we compared: these are categories, not vendors, so the table carries no vendor prices. OSStend sits in the last row. Dated limits for named services are on the alternatives pages.

When shared or self-managed hosting is the better choice: a small project with light load and an owner who enjoys running servers will usually cost less than a designed cluster. OSStend is built for production databases where an outage has a business cost.

From our on-call engineers: what we check first on a database we inherit

When we inherit a production database we check recoverability and growth before tuning anything, because those two decide how bad the next incident is. A restore that has never been tested and one huge table are the most common findings.

  • We restore the latest backup to a scratch instance and time it, because a backup that has never been restored is an assumption, not a recovery plan.
  • We list the largest tables first. In Kubernetes Postgres estates we have been asked to stabilise, a very large unpartitioned audit table was a recurring factor in slow base backups and slow replica rebuilds.
  • We check replica health and clone time next, since replicas that crash or take hours to rebuild leave a single copy of the data during an incident.
  • Changes go through pre-production first, then production, because fixes that look safe on a small dataset behave differently on a large one.
  • We check disk headroom against the growth of the biggest tables, not against current usage.

Can the database be hosted in my cloud account, OSStend's cloud or my data center?

Yes. Where the cluster runs is a choice made per workload, and the service model follows from it: fully managed in OSStend's cloud or your cloud account, co-managed where you own the infrastructure.

Where it runsWhat it isService model
OSStend's cloudSingle-tenant clusters in the region you choose, on Google Cloud or AWS, multi-zone by default.Fully managed
Your cloud accountOSStend operates inside your account and VPC, so data, billing and the security boundary stay with you. AWS first, then Azure and Google Cloud. See bring your own cloud.Fully managed
Your data centerOn-premises and air-gapped sites, on Kubernetes, OpenShift or Windows hosts, with FIPS where required.Co-managed

Every option is compared on deployment options. Uptime and response figures are set per plan and written into your contract; see service levels.

How do cloud database options compare?

Cloud databases fall into three families: a hyperscaler's own service, a developer platform, and dedicated hosting. The right one depends on how far the workload sits from the defaults of a standard plan.

OptionExamplesGood fitPoor fit
Hyperscaler database serviceAmazon RDS, Google Cloud SQL, Azure Database for PostgreSQLA standard plan holds the workload and you stay in one cloud.You need settings or extensions the plan does not expose, or the database must run in more than one cloud or on-prem.
Developer platformNeon, Supabase, Railway and RenderPrototypes and apps that want a database bundled with the platform.Steady production load that needs a dedicated cluster in your own account.
Dedicated, managed hostingOSStendProduction databases that outgrow a plan, or must run in your account, several clouds or your data center.Free tiers, self-serve sign-up with a card, or a database that fits a standard plan.

How we compared: each named service has its own page with dated limits and list prices read from the vendor's page. See managed PostgreSQL pricing compared for seven services side by side, or the best managed open-source database providers.

What does database hosting cost?

Hosting cost follows four things: the engine, the size and replica count, the service level, and where the database runs. OSStend prices the design, not a plan size, and there is no free tier or card sign-up.

Engine
each engine has its own operating profile, and several can share one contract and one on-call team.
Size and replicas
data size, request rate and the replica layout the recovery targets need.
Service level
fully managed or co-managed, and the uptime or response 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.

To estimate a hyperscaler bill for comparison, use the cost calculator. The model that applies across every engine is on pricing.

How it works

How do I choose a database host?

Choose by what the database must do, not by the plan menu. Start with the recovery targets and the place it must run, then check who is on call.

  1. Write down the recovery point and recovery time the business can accept, and the region or site the data must stay in.
  2. Check whether a standard plan from a hyperscaler or platform meets them. If it does, it is usually the cheaper route.
  3. If the plan does not expose the settings, versions or place you need, look at dedicated hosting.
  4. Ask who is on call at 3 a.m. and whether that person knows your design.
  5. Ask how the move happens and whether both sides stay live until you switch.
  1. Review

    An engineer reviews the current setup: sizes, settings, modules or plugins, versions, traffic and where it must run.

  2. Design

    The cluster design is written and signed off before anything is built: size, topology, configs, versions and upgrade calendar.

  3. Move

    The new cluster runs beside the old one and stays current while the old service stays live. Traffic switches only when the new side is verified.

  4. Run

    Named engineers operate it 24/7: backups, patching, scaling and incident response, with upgrades on the customer's change calendar.

Enterprise only

When should I contact OSStend, and when not?

Contact OSStend when a production database has outgrown a standard plan or has to run somewhere a plan cannot. If a standard plan fits, or you want a free tier, a turnkey service is the better choice.

Operated by AceMQCompany figures, as published on acemq.com
160+customers served by AceMQ, which operates OSStend
10+years running open source data and messaging
24/7on-call engineers, not a ticket queue

Contact us if

  • You need custom configuration, versions or extensions, or your own upgrade calendar.
  • The database must run in your cloud account, in more than one cloud or in your data center.
  • You want one team accountable for several engines.
Talk to an engineer

Not a fit if

  • Your workload fits a standard plan in a single cloud.
  • You want a free tier or to sign up with a card.
FAQ

Questions about database hosting

These are the questions buyers ask before choosing a database host.

Talk to an engineer →

What are database hosting services?

Database hosting services run your database on servers or cloud capacity you do not operate yourself. They range from renting a server to a full managed service. OSStend's hosting is the managed end: dedicated clusters with backups, failover, patching and 24/7 on-call engineers.

What is the difference between a cloud database and database hosting?

A cloud database is a database delivered from a cloud provider's platform, usually on a plan menu. Database hosting is the wider term for any arrangement where someone else provides the place it runs. OSStend hosts dedicated clusters in its cloud, in your cloud account or in your data center, so the cloud and the operator can differ.

Does OSStend offer MySQL database hosting?

Yes. OSStend hosts MySQL and MariaDB on dedicated clusters, with a primary plus replicas, failover and point-in-time recovery. See managed MySQL.

Can OSStend host a database in my own cloud account?

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

How is database hosting priced?

The price follows the engine, the size and replica count, the service level and where it runs, and an engineer prices the specific design after a workload review. There is no free tier. See pricing.

Talk to an engineer

Talk to an engineer about hosting your database

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.