Service levels

Service levels: two tiers, a written SLA for each

Hand OSStend the whole service, or keep your infrastructure and let it run the engines. Either way, the same named engineers are on call 24/7.

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

  • Operated by AceMQ
  • 24/7 on call
  • Two tiers
  • Enterprise only

OSStend offers two service tiers. Fully managed means OSStend runs everything, in its cloud or inside your cloud account. Co-managed means you keep the infrastructure and the network in your data center, private cloud, Kubernetes or OpenShift, and OSStend operates the engines 24/7. Each tier has its own SLA, written into the contract.

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

The two tiers

Fully managed hands OSStend the whole service. Co-managed leaves the infrastructure with you and hands OSStend the operation of the engines. The engineers, the engines and the process are the same in both.

Fully managed

OSStend runs everything

Provisioning, upgrades, scaling, backups and 24/7 on-call. Dedicated in OSStend's cloud on Google Cloud or AWS, or inside your own cloud account.

Uptime SLA
Co-managed

You keep the infrastructure

OSStend operates it 24/7. You keep the network and access controls, in your data center, private cloud, Kubernetes or OpenShift, including air-gapped, FIPS and Windows hosts.

Response-time SLA

What each tier covers

The tiers differ in who owns the infrastructure and the network, and in the kind of SLA that follows from that. When OSStend owns the infrastructure it can commit to uptime. When you own it, the commitment is how fast engineers respond.

Fully managedCo-managed
Where it runsDedicated in OSStend's cloud, or inside your AWS, Azure or Google Cloud accountYour data center, private cloud, Kubernetes or OpenShift, including air-gapped, FIPS and Windows hosts
Who keeps the infrastructureOSStend in its cloud, or your account where OSStend operates inside itYou
Network and access controlsYours when it runs in your accountYours
On call 24/7 by named engineersYesYes
Upgrades, patching and scaling planned around your change windowsYesYes
Kind of SLAUptime SLAResponse-time SLA

Within co-managed, the detailed split, such as who provisions servers, who runs backups and who patches the operating system and hardware, is written into the contract for each engagement.

On call and incident handling

Named engineers across the Americas, EMEA and APAC are on call around the clock under both tiers. Incidents are ranked by severity, and Severity 1 is answered 24/7.

The engineers on call are the ones who designed and run your cluster, backed by AceMQ's 10+ years of operating these systems. Security controls that apply to both tiers are on security, and where each tier can run is on deployment options.

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. At AceMQ every ticket has a named owning engineer, and senior architects lead every engagement and every escalation.

Choosing a tier

Choose fully managed when you want no infrastructure to own. Choose co-managed when the workload has to stay on infrastructure you control.

  • Fully managed fits teams that want the whole service run for them, in OSStend's cloud or in their own cloud account.
  • Co-managed fits regulated, on-prem and air-gapped estates, cloud repatriation, and any site where the network and access controls stay with you.
  • Price follows the tier, the engine, the cluster size and the location. See pricing.
Talk to an engineer

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
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.