Alternative

Elastic Cloud pricing and alternatives: managed OpenSearch

OpenSearch under the Apache 2.0 licence, sized to your indices and run 24/7 in our cloud, your cloud account or your data center.

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

  • Operated by AceMQ
  • OpenSearch
Elastic Cloud → OSStend · at a glance

OSStend runs OpenSearch, an Apache 2.0 search and analytics suite derived from Elasticsearch 7.10, for teams that want a fixed design and a place of their choosing instead of Elastic Cloud pricing models. Elastic Cloud remains the better choice if you depend on Elastic's own solutions or newer Elasticsearch features.

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

Elastic Cloud and OSStend at a glance

Elastic Cloud is Elastic's hosted service for Elasticsearch and the Elastic solutions built on it. OSStend runs OpenSearch, a different engine with a different licence, and tailors the cluster to the workload.

OSStend
EngineOpenSearch, with OpenSearch DashboardsElasticsearch, with Kibana and Elastic's Search, Observability and Security solutions
LicenceOpenSearch is released under Apache License 2.0 (OpenSearch FAQ)Elastic announced in August 2024 that AGPL would be added next to ELv2 and SSPL as a licence option (Elastic)
Where it runsOur cloud, your cloud account, your data centerElastic Cloud Serverless, Elastic Cloud Hosted, or self-managed; sold through AWS, Azure and Google marketplaces (Elastic pricing)
PricingPrice drivers on pricing; sized per designHosted is resource-based and Serverless is usage-based, both pay as you go or prepaid (Elastic pricing)

Sources: Elastic pricing, Elastic licence post and OpenSearch FAQ, checked 30 Oct 2026.

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

Why teams look for an alternative to Elastic Cloud

Three reasons come up: the licence history, two pricing models that are hard to forecast against a fixed budget, and where the service can run. Each is stated below with its source.

Illustrative: plan names and shapes stand in for any provider's menu.
Licence.
Elasticsearch has been offered under ELv2 and SSPL, and Elastic said in August 2024 that it would add AGPL as another option (Elastic, checked 30 Oct 2026). OpenSearch is released under Apache 2.0 and is a project of the Linux Foundation (OpenSearch FAQ, checked 30 Oct 2026). Teams with an open source licence policy often start from this difference. The OpenSearch vs Elasticsearch comparison covers it in full.
Pricing model.
Elastic's pricing page describes Hosted as resource-based and Serverless as usage-based, with Platinum and Enterprise subscription tiers on Cloud (Elastic pricing, checked 30 Oct 2026). Comparing either with a fixed cluster design takes some work.
Place.
Elastic Cloud runs as a hosted service. Its self-managed option leaves infrastructure to the customer (Elastic pricing, checked 30 Oct 2026), so a managed service in a data center or an air-gapped site needs another vendor.

A fair snapshot of Elastic Cloud

Elastic is the company behind Elasticsearch, and Elastic Cloud is the most direct way to run it with the vendor's own features. If your teams use Elastic's Observability or Security products, or features newer than the OpenSearch fork point, staying is the lower-risk path.

  • It offers Search, Observability and Security solutions on one platform (Elastic pricing, checked 30 Oct 2026).
  • It lists a 99.95% monthly uptime SLA for the Platinum and Enterprise subscription tiers on Elastic Cloud Hosted and Serverless (Elastic pricing, checked 30 Oct 2026).
  • It is available through the AWS, Azure and Google marketplaces, which helps teams that buy through cloud commitments (Elastic pricing, checked 30 Oct 2026).

Where Elastic Cloud is the better choice: estates built on Elastic's solutions, applications that use Elasticsearch features added after the fork, and teams that want the vendor to run the engine it writes. OpenSearch was derived from Elasticsearch 7.10.2 and is described as keeping backwards-compatible REST APIs with 7.10 (OpenSearch FAQ, checked 30 Oct 2026), so newer workloads need a compatibility test before any move.

Compare

Full comparison: OSStend and Elastic Cloud

OSStend is listed first. The Elastic column states what Elastic publishes, with the date checked.

FactorOSStend
Good fitSearch and log workloads that run on OpenSearch; teams with an Apache 2.0 policy; estates that must run outside a public cloudTeams using Elastic's solutions or newer Elasticsearch features; buyers who want the vendor to run its own engine
Poor fitWorkloads that depend on Elastic-only products or features, free tiers, self-serve sign-upEstates that need a managed service in a data center or an air-gapped site
Engine and licenceOpenSearch, Apache License 2.0 (OpenSearch FAQ)Elasticsearch under ELv2, SSPL and, from the August 2024 announcement, AGPL (Elastic)
Where it runsOur cloud, your cloud account, your data center, Kubernetes or OpenShiftHosted service on the major clouds via marketplaces; self-managed is run by the customer (Elastic pricing)
TailoringNode roles, shard and replica plan, plugins and upgrade timing designed for the workloadWithin the chosen deployment type and subscription tier
MigrationReindex or snapshot with both clusters live; OSStend runs and owns the cutoverYour team plans and runs it
Service levelsWritten SLA per plan (see service levels)Elastic lists 99.95% monthly uptime for Platinum and Enterprise (Elastic pricing)
Pricing modelPrice drivers: node count and size, storage, SLA tier, where it runs. See pricingHosted resource-based, Serverless usage-based (Elastic pricing)

Sources: Elastic pricing, Elastic licence post, OpenSearch FAQ, checked 30 Oct 2026.

Enterprise only

How OSStend does it

OSStend designs the OpenSearch cluster for your indices and query load, moves the data with both clusters live and runs it with named engineers. The first step is a 45-minute workload review with an engineer: the current setup is reviewed, the design is sketched, and a price follows for that design.

Managed OpenSearch is sized from measured ingest and query volume, with the node roles, shard plan and plugins written into the design. Dashboards, ingest agents and any feature that relies on an Elastic product are listed in the review, so each has a replacement or a decision before anything moves.

Contact us if

  • Your workload runs on features OpenSearch has, and an Apache 2.0 engine suits your policy.
  • You want a fixed cluster design you can price, in your cloud account or data center.
  • You also run Kafka, PostgreSQL or RabbitMQ and want one vendor.
Talk to an engineer

Not a fit if

  • You depend on Elastic's Observability or Security products, or on Elasticsearch features newer than the fork.
  • You want the vendor that writes the engine to run it.
  • You want a free tier or a card sign-up.
Pricing

Elastic Cloud pricing: list prices and what ours depends on

Elastic prices Hosted by resources and Serverless by usage, and its Hosted page lists a starting price for each subscription tier. OSStend prices the design, and the drivers are the node count and size, storage and retention, the service level tier and where the cluster runs.

Elastic Cloud Hosted tierAs low as, per month
Standard$99
Gold$114
Platinum$131
Enterprise$184

Source: Elastic Cloud Hosted pricing, checked 1 Nov 2026. Elastic's footnote bases these figures on a cloud production configuration with 120 GB of storage across 2 zones, with instance usage-based pricing on top; they are not tied to one cloud or region. Serverless is usage-based and its page lists no single starting price (Elastic pricing).

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 compare, take current node sizes, retention and ingest volume and price the same shape on both sides. Details are on pricing.

Fair notes on other options

Teams leaving Elastic Cloud usually weigh OpenSearch on AWS, staying on Elastic with a different deployment type, or another managed vendor.

Amazon OpenSearch Service.
AWS runs OpenSearch for you on AWS (AWS, checked 30 Oct 2026). It suits OpenSearch workloads that stay on AWS.
Elastic self-managed.
Keeps the Elastic engine and features, with the customer running the infrastructure (Elastic pricing, checked 30 Oct 2026).
Instaclustr.
Lists OpenSearch among its services (Oct 2026; checked 30 Oct 2026, Instaclustr).

How to choose

Choose by which Elastic features you use and where the cluster must run. If you use Elastic-only features, stay; if you use search and logs on core features, OpenSearch is a fair swap.

  1. If you use Elastic's solutions or newer Elasticsearch features, stay on Elastic Cloud.
  2. If you want an Apache 2.0 engine and the workload fits OpenSearch, choose OpenSearch.
  3. If OpenSearch must run in a data center or your own cloud account, choose OSStend.
  4. If it stays on AWS and the AWS service fits, compare Amazon OpenSearch Service, with its price lines and quotas dated 17 Nov 2026.
How it works

Moving off Elastic Cloud

The first step is a compatibility check of mappings, queries and tooling. Data then moves while Elastic Cloud stays live, and clients switch once the new cluster is verified.

Illustrative: each phase is planned and rehearsed with your team before traffic moves.
  1. Review

    Index mappings, queries, ingest pipelines, Kibana objects, plugins and the Elasticsearch version in use.

  2. Design

    Node roles, shard and replica plan, plugins and where the cluster runs. Features with no OpenSearch equivalent are decided here.

  3. Move

    Data moves by snapshot or reindex. OpenSearch documents a Migration Assistant for moving from Elasticsearch (OpenSearch docs, checked 30 Oct 2026); see also the Elasticsearch to OpenSearch guide.

  4. Cut over

    Clients and dashboards switch in stages. Elastic Cloud stays available for rollback.

Talk to an engineer

Price your OpenSearch design with an engineer

45 minutes: your Elastic Cloud deployment is reviewed and the OpenSearch design is sketched.

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