Managed Elasticsearch Hosting — production-ready from $15 a month
Distributed search and analytics engine. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Elasticsearch, no lock-in.
Elasticsearch on ManageStacks is production-grade Elasticsearch (or OpenSearch, the AWS-forked Apache-2.0 fork) deployed to your own AWS, Azure, or GCP region — priced flat at $29 per cluster per month regardless of index size, with automatic sharding, replication, snapshot-to-S3 backups, and Kibana included. Materially cheaper than Elastic Cloud or AWS OpenSearch Service for typical workloads. Also fully licence-safe against the Elastic v7.11+ SSPL/ELv2 change (we support OpenSearch as a drop-in).
What does Elasticsearch do, and why do teams deploy it?
Elasticsearch is the world's most widely deployed search and analytics engine. Built on Apache Lucene, it provides near-real-time full-text search, structured queries, aggregations, and geospatial features. It's the search engine behind e-commerce sites, log platforms, and thousands of application-specific search implementations.
Since Elastic switched to SSPL/Elastic License 2.0 in 2021, AWS forked the last Apache-2.0 version and continued it as OpenSearch. Both engines share the same core (Lucene) and largely the same API. ManageStacks offers both — pick based on your licence posture and vendor preference.
Running production Elasticsearch/OpenSearch means running a 3-node cluster minimum, sizing JVM heap and off-heap page cache correctly (50/50 rule), configuring shard counts per index carefully (getting this wrong is the #1 cause of performance problems), setting up snapshot-to-S3 for backups, and testing major-version upgrades (each version has schema and behaviour changes). ManageStacks handles it.
- Full-text search with relevance scoring, analyzers, and multi-language support
- Near-real-time indexing (sub-second) and sub-second query response
- 3-node cluster minimum with automatic sharding and replication
- Rich aggregations for real-time analytics
- Kibana included for exploration, dashboards, and index management
- Snapshot-to-S3 backups with configurable retention
Distributed search and analytics engine
What does managed Elasticsearch hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
Self-hosting Elasticsearch vs managed — what does it really cost?
The software is free. The engineer-hours are not.
Running it yourself
- Stand up 3+ nodes on VMs; tune JVM heap and off-heap page cache
- Design shard topology per index; get replica counts right for HA
- Configure snapshot-to-S3 backups; verify restores work
- Test major-version upgrades in staging; validate query compatibility
- Decide Elasticsearch (SSPL/ELv2) vs OpenSearch (Apache-2.0); package either
On ManageStacks
- Subscribe through your AWS, Azure, or GCP marketplace
- Cluster comes up as 3 nodes with TLS, JVM tuning, S3 snapshots, Kibana/Dashboards
- Grafana dashboards ship for cluster health, JVM heap, indexing rate, query latency
- Rolling upgrades handled by us with zero-downtime cluster availability
- Pick Elasticsearch or OpenSearch — same operational shell for both
Elasticsearch on ManageStacks vs the alternatives
How Elasticsearch/OpenSearch on ManageStacks compares to the two dominant managed search offerings and running the cluster yourself.
| Elasticsearch/OpenSearch on ManageStacksUs | Elastic Cloud | AWS OpenSearch Service | Self-hosted on your VM | |
|---|---|---|---|---|
| Deployment | Managed on your AWS, Azure, or GCP | Vendor-hosted (multi-cloud) | AWS-managed | You provision + operate |
| Data residency | Your cloud region | Vendor region choice | AWS region | Your cloud region |
| Pricing basis | Flat per cluster | Per node-hour + storage | Per instance-hour + storage | Your compute cost |
| Engine choice | Elastic or OpenSearch | Elasticsearch only | OpenSearch only | You choose |
| Open source | SSPL/ELv2 or Apache-2.0 | SSPL/ELv2 (hosted) | Apache-2.0 (hosted) | SSPL/ELv2 or Apache-2.0 |
| Kibana / Dashboards | Included | Included | OpenSearch Dashboards included | You install |
Provisioning, upgrades, backups and monitoring on your team’s plate.
What does running Elasticsearch yourself involve?
ManageStacks deploys Elasticsearch (or OpenSearch, your pick) as a 3-node cluster with JVM heap tuned, TLS between nodes and clients, snapshot-to-S3 backups, and Kibana or OpenSearch Dashboards. We handle rolling upgrades, shard rebalancing, and the operational polish that keeps Lucene-based clusters performant under load.
Elasticsearch key numbers
How long from subscribing to a live instance?
Subscribe
Subscribe to ManageStacks through your AWS, Azure, or GCP marketplace.
Choose engine
Pick Elasticsearch (Elastic-vendor SSPL/ELv2) or OpenSearch (Apache-2.0).
Provision
3-node cluster spins up with TLS, JVM tuning, S3 snapshots, Kibana/OpenSearch Dashboards, and Grafana monitoring — typically 3-5 minutes.
Index + search
POST documents to your index. Standard REST API and client libraries all work. Set up ILM policies for lifecycle management.
When is self-hosting Elasticsearch the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Elasticsearch at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Elasticsearch run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Elasticsearch in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Elasticsearch on ManageStacks
Elasticsearch or OpenSearch — which should I pick?
For net-new deployments where licence purity matters (regulated industries, distros with strict OSI-only policies, or cloud-reselling concerns), pick OpenSearch — fully Apache-2.0 licensed. For existing Elasticsearch deployments, or if you need specific Elastic-vendor features (Elastic APM, ML anomaly detection), pick Elasticsearch. Wire-protocol and query DSL are largely compatible for standard search and analytics workloads.
How does this compare to Elastic Cloud or AWS OpenSearch Service?
Elastic Cloud is priced per node-hour + storage + I/O; AWS OpenSearch is similar. Both grow expensive as your cluster scales. ManageStacks is flat $29 per cluster at standard tier. For small-to-medium clusters (< 500 GB data, < 3 nodes), self-hosted on ManageStacks is materially cheaper. Elastic Cloud is worth it if you specifically need Elastic-vendor features (Search UI, Enterprise Search connectors, App Search); AWS OpenSearch for VPC-tight integrations.
How is cluster health and shard management handled?
3-node cluster minimum with 1 replica per primary shard. Cluster health, shard allocation, and index-level relocation are monitored continuously. Grafana dashboards show cluster status, JVM heap, indexing rate, query latency, and shard balance. Automatic shard rebalancing keeps the cluster even.
Can I use Kibana / OpenSearch Dashboards?
Yes. Kibana (for Elasticsearch) or OpenSearch Dashboards (for OpenSearch) install alongside the cluster and mount at a subdomain of your deployment. Pre-built dashboards for common exporters (Filebeat, Metricbeat) are included.
Does ManageStacks handle Elasticsearch/OpenSearch version upgrades?
Yes. Major upgrades (7 → 8 → 9 for Elasticsearch; 1 → 2 → 3 for OpenSearch) involve schema and behaviour changes tested on a clone of your indexes first. Rolling restarts across cluster nodes keep the cluster available during the upgrade.
How is snapshot-to-S3 backup configured?
S3-backed snapshot repository is configured by default. Daily incremental snapshots + weekly full snapshots. Retention is configurable (default 30 days). Restore any snapshot to any cluster through the ManageStacks dashboard or the native REST API.
What about vector search for AI/embedding workloads?
Both engines support kNN vector search via the built-in kNN plugin. HNSW indexes are the default. For very-large vector workloads (100M+ vectors, high-QPS), Qdrant or a purpose-built vector DB might be a better fit — but for tens of millions of vectors alongside a text-search workload, Elasticsearch/OpenSearch is efficient.
What if I want to migrate off?
Snapshot to S3 → restore into another cluster. Both engines support cross-cluster search + replication for zero-downtime migration. Elasticsearch/OpenSearch are portable by design. Migration off ManageStacks is a supported operation.
Run Elasticsearch without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $15/mo.