Compare / OpenSearch Service

WarpSearch vs Amazon OpenSearch Service (managed OpenSearch)

AWS's managed OpenSearch clusters. You pick instance types and counts and pay for every node-hour, plus storage, whether or not anyone is querying.

Managed OpenSearch still means sizing a cluster. WarpSearch answers the OpenSearch REST API with no nodes to run. Below is what a managed OpenSearch domain costs for four real workloads, next to WarpSearch. For a fixed-plan managed OpenSearch provider, see Aiven; for AWS's serverless option, see OpenSearch Serverless pricing.

The scoreboard

Price

Cheaper on all 4 workloads OpenSearch Service can run

Small RAG13 to 40x cheaper
WarpSearch$10
OpenSearch Service$132 to $397
Catalog2.9 to 11x cheaper
WarpSearch$139
OpenSearch Service$400 to $1,575
Mid-size logs1.4x cheaper
WarpSearch$1,465
OpenSearch ServiceAbout $2,000
Large logs2.6x cheaper
WarpSearch$39,060
OpenSearch ServiceAbout $103,000

Monthly, list prices. Bars are drawn to the middle of a range.

How they bill

WarpSearchOpenSearch Service
Billing unitPer GB stored, per GB written, per requestPer instance-hour for data, master and warm nodes, plus EBS and managed storage
Smallest HA cluster$10 a month minimumAbout $390 a month for 3 x r7g.large data nodes ($0.178/hour each), before storage and dedicated masters
Scale to zeroYes, after 15 minutes idleNo. Nodes run all month
Capacity planningNoneYou size nodes, EBS volumes and shards
Log retentionOne index, storage tiered per GBHot nodes plus UltraWarm (S3-backed, read-only) at $0.024/GB-month plus warm node hours

What OpenSearch Service cannot do, or does only in part: Provisioned clusters billed by the instance-hour whether you query or not. You choose instance types, node counts, EBS volumes and shards. Warm (UltraWarm) storage needs dedicated master nodes and holds read-only indexes.

Price

Monthly cost at list prices in US East.

1M text chunks with 768-dim embeddings, 7 GB of JSON. 1M queries a month spread through the day. 1 GB written a month.

WarpSearchOpenSearch Service
Storage$0.56 (7 GB held x $0.08)$2 to $7 (20 GB gp3 per node at $0.122)
Writes$1.00 (1 GB x $1.00)In instance cost
Search$2.00 (1M requests)$130 to $390 (1 r7g.large with no HA, or 3 across three zones)
Data returned$0 (about 40 GB, inside the free 100 GB)AWS data transfer rates
Minimum$10 minimum applies (usage is $3.56)None. Production adds about $296 for 3 dedicated masters (m7g.large)
Total a month$10$132 to $397

Our sizing. 1M x 768-dim vectors need about 3.5 GB of memory for HNSW, which fits a 16 GB node.

5M products with 384-dim embeddings, 10 GB of JSON. 50M queries a month (about 19 a second on average). 20 GB written a month.

WarpSearchOpenSearch Service
Storage$0.60 (7.5 GB held x $0.08)$11 to $18 (30 to 50 GB gp3 per node)
Writes$20 (20 GB x $1.00)In instance cost
Search$100 (50M requests)$390 to $1,557 (3 x r7g.large to 3 x r7g.2xlarge)
Data returned$18 (250 GB returned, 100 GB free, before compression)AWS data transfer rates
MinimumClearedNone. Production adds about $296 for dedicated masters
Total a month$139$400 to $1,575

Our sizing. 5M x 384-dim vectors need about 8 to 9 GB of memory per copy; the right size depends on your peak query rate, which varies from the 19 a second average.

Performance

TestResult
Keyword search, 2.8M docs (LoTTE)2.1 ms median, 3,700 queries/s
Keyword search, 10M passages (MS MARCO v2)2.4 ms median (5.4 ms with an exact total hit count)
Keyword search, small BEIR sets1 to 6 ms median
Vector search, 10M x 128-dim (BigANN SIFT)0.964 recall@10 at 6.2 ms median, 162 queries/s
Vector search, 1M x 1536-dim (arXiv)0.961 recall@10 at 15.7 ms median
Filtered vector search, 10M (YFCC)0.959 recall@10 at 10.4 ms median
Log filters, 22M events (http_logs)1 to 2 ms median
Log aggregations, 22M events190 to 430 ms median (sort, daily histogram, avg by status)
Ingest, short text63,000 to 97,000 docs/s
Ingest, logs (247M events)76,000 to 81,000 events/s
Ingest, 768 to 1536-dim vectors2,200 to 4,000 vectors/s
Time to searchableSeconds, or immediate with commit=true
Cold startNot measured yet. First query on a 2.3 GB index: 17 to 19 ms vs 2.7 ms warm (page cache only)

Measured October 2026 through our Elasticsearch-compatible API, warm cache, client in the same region, single runs. Every test ran on deliberately minimal hardware, 2 to 4 CPUs (a 4 CPU container or an AWS i8g.large with 2 vCPUs), so these are the least favorable results we can produce. More hardware only improves them. Numbers exclude internet round trips.

Bottom line

Choose WarpSearch for

  • Search apps: $10 vs $132 to $397 for RAG, and $139 vs $400 to $1,575 for the catalog workload.
  • No instance types, EBS volumes, dedicated masters or shards to size, and no paying for idle hours.

WarpSearch costs a fraction of a provisioned cluster for apps and catalogs, with no instances, EBS volumes or shards to size.

Questions

What is managed OpenSearch?

A provider runs OpenSearch clusters for you: Amazon OpenSearch Service domains, Aiven, and others. You still choose instance types, node counts, disks and shards, and you pay for every node-hour whether or not anyone queries.

How much does AWS OpenSearch cost?

A highly available cluster of 3 r7g.large data nodes is about $390 a month in US East before storage. Production setups add about $296 a month for 3 dedicated master nodes, which UltraWarm requires.

Managed OpenSearch or OpenSearch Serverless?

Managed domains bill node-hours around the clock. OpenSearch Serverless removes node sizing but bills OCU-hours, about $350 a month for search alone while awake. WarpSearch bills per request, with a $10 monthly minimum.

Sources

Rates are on-demand, US East (N. Virginia), from the AWS Price List API on October 21, 2026. Node counts and sizes are our estimates, not AWS sizing guidance. Reserved instances and savings plans lower the instance price. Prices checked October 20, 2026. List prices in US dollars, before discounts. Estimates are marked. Tell us if something is out of date: contact us.