OSStend pricing: dedicated, tailored, quoted per design
Dedicated clusters in our cloud, your cloud account or your data center, on one contract. The price follows four drivers: engine, cluster size, SLA tier and where it runs.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Dedicated clusters
- ✓One contract
- ✓Enterprise only
Database as a service pricing at OSStend is built from four drivers: the engine, the size of the cluster, the SLA tier and where it runs. Every price is for a dedicated cluster tailored to the workload, on one enterprise contract. There is no free, developer or card sign-up plan.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What sets the price
Four drivers move the price of a cluster. Your engineer sets each one in the design step and prices the result after the workload review.
| Driver | What moves the price |
|---|---|
| Engine | PostgreSQL, MySQL, MongoDB, Redis or Valkey, OpenSearch, Kafka or RabbitMQ. Each has its own topology, tooling and tuning. See managed database services. |
| Cluster size | Node count, instance size, storage and partition plan, sized to measured load rather than picked from a plan menu. |
| SLA tier | Fully managed or co-managed, and the SLA that goes with each. See service levels. |
| Where it runs | Our cloud, your AWS, Azure or Google Cloud account, or your data center, Kubernetes, OpenShift or an air-gapped site. In your own cloud account the infrastructure stays in your billing. |
How a price is set
Each price is for a dedicated cluster sized to the workload, not a shared plan. Your engineer prices the design after the review, so the figure is for the cluster you need.
Prices are quoted per design rather than read from a list. Send the engine, the rough size and where it must run, and the engineer prices that design from the four drivers above. If you keep your own databases and want the DBA work run for you, see database administration services.
Larger engagements can be phased: a proof of concept on one workload, then production, then the wider platform. Customer outcomes describes the workloads OSStend suits, and the documented limits of turnkey services show where a plan menu stops.
What is included
The price covers the service around the engine, not only the servers. The same named engineers, the SLA, monitoring and the migration are part of the engagement.
| Included | What it covers |
|---|---|
| An SLA | One for each tier, written into the contract. How the tiers differ is on service levels. |
| Named engineers, 24/7 | On call across the Americas, EMEA and APAC: upgrades, patching, scaling, backups and incident response, planned around your change windows. |
| Monitoring | Metrics and alerts forwarded to your Datadog, Dynatrace, Splunk or Prometheus, not a separate console. |
| Migration | OSStend runs the migration and owns the cutover, with both sides live until you switch. |
| One contract | One contract and one on-call team across every engine. |
How the migration is charged, the contract term and invoicing are set out in the written quote, before anything is signed.
Who this pricing is for
OSStend sells dedicated, tailored clusters to enterprises. There is no free, developer or hobby plan, no card sign-up and no self-serve console. Every engagement starts with a conversation with an engineer.
Contact us if
- ✓You need a cluster sized, configured and run around your workload.
- ✓You want one contract and one on-call team across several engines.
- ✓You are comparing the list price of a cloud provider's database with a dedicated service. See Amazon RDS alternative and managed PostgreSQL pricing compared.
Not a fit if
- ✕Your workload fits a standard plan. A turnkey service will cost you less.
- ✕You want a free tier or a developer plan.
- ✕You want to sign up with a card and start today.
Billing questions
Short answers to the billing questions buyers ask before a first call.
Is there a free tier or a developer plan?
No. OSStend is enterprise only, with no free tier, no hobby plan and no card sign-up. Engagements start with a conversation with an engineer.
What decides the price of a cluster?
Four drivers: the engine, the cluster size, the SLA tier and where the cluster runs. The engineer prices the design for the workload after the review.
Who pays for the cloud infrastructure when it runs in my own account?
In a customer's own cloud account the data, the billing and the security boundary stay with the customer. How infrastructure and service charges are itemised is confirmed in the estimate.
Is there one contract for several engines?
Yes. One contract and one on-call team cover every engine, so PostgreSQL, Kafka, RabbitMQ and the rest do not need separate vendors.
To price a specific design, talk to an engineer or read how it works first.
Related pages
- EnginesManaged database service for enterprise workloadsA managed database service for enterprise workloads: PostgreSQL, MySQL, Redis or Valkey, OpenSearch and Kafka, designed, run and tuned by engineers.
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- DBA servicesDatabase administration services, run 24/7Database administration services for PostgreSQL, MySQL, Redis or Valkey and OpenSearch: monitoring, tuning, backups, upgrades and 24/7 on-call engineers.
- CustomersCustomer outcomes for enterprise data workloadsOSStend customers are enterprises whose workloads outgrow a turnkey plan. Operated by AceMQ: 160+ customers, 10+ years, 24/7. Outcome cards to follow.
- Research · Original dataManaged service limits index, checked 9 Nov 2026A managed service limits index: 13 documented limits of Amazon MQ, MSK, ElastiCache, Neon, Supabase and Instaclustr, each with its source link and date.
- AlternativeAmazon RDS alternatives in 2026Amazon RDS alternatives for PostgreSQL and MySQL: where RDS is the better choice, what the alternatives cost, and running dedicated clusters in any cloud.
Talk to an engineer, not a ticket queue
45 minutes with someone who runs these systems. We map your databases and brokers, the zero-downtime cutover path and which tier fits.
- ✓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