Skip to content
InSearch
How it works
Enterprise search software ChatGPT Enterprise pricing Coveo vs Lucidworks Dust vs GoSearch Dashworks alternatives Glean pricing Glean alternatives Microsoft Copilot alternatives Dropbox Dash pricing Dropbox Dash vs Glean Dust vs Gemini Enterprise Guru pricing Coveo pricing Coveo alternatives Bloomfire alternatives Guru alternatives Moveworks alternatives Claude Ask Your Org Claude Enterprise pricing Notion AI pricing Elastic Enterprise Search pricing Perplexity Enterprise pricing Copilot Studio pricing Amazon Kendra pricing Unleash pricing ChatGPT Business pricing Copilot Business pricing Kore.ai pricing Claude Team pricing Dust pricing Grok Business pricing Hebbia pricing Hebbia alternatives Slack AI pricing Algolia pricing Pinecone pricing Azure AI Search pricing Search management software Law firm knowledge management software Internal knowledge base software Amazon OpenSearch Service pricing Gemini Enterprise vs ChatGPT Enterprise ChatGPT Enterprise vs Copilot Amazon Quick Suite pricing Amazon Q pricing Gemini Enterprise pricing Copilot pricing Slack enterprise search Enterprise search use cases Enterprise search tools AI work assistant Knowledge base search AI enterprise search Internal company search engine Internal knowledge search Workplace search Search all company apps AI knowledge assistant Unified search Search Slack & Drive AI assistant for work Knowledge management RAG for enterprise Cited AI answers Confluence search Notion search AI for support agents Sales enablement search Engineering search Enterprise search for remote teams HR knowledge assistant Permission-aware search Secure AI search Onboarding knowledge SharePoint search Intranet search See all →
Security Pricing Blog Contact Sign in
Procurement manager comparing two printed vendor proposals at a desk

Compare · Amazon OpenSearch Service pricing

Amazon OpenSearch Service pricing per instance and OCU, with AWS OpenSearch Serverless cost for company search

Most OpenSearch cost guides are written for log analytics, where a cluster swallows terabytes a day and the hard question is retention. This page is for a different reader: the person asked what OpenSearch would cost behind employee search, so people can type one question and find the answer across Drive, Slack, Confluence and Jira.

One search · cited answers · permission-aware

Answer Console
Your files only
Reading your filesโ€ฆ

That request did not get through. Tap Ask InSearch again.

No account needed. Your files are read once to answer, then deleted from our servers, and never used to train any model.

Short answer

Amazon OpenSearch Service bills provisioned domains per instance hour plus storage, and OpenSearch Serverless per OCU hour plus storage. In the AWS price list for US East (N. Virginia) a t3.small.search node is $0.036 an hour (about $26 a month), m7g.large.search is $0.135 (about $99), r7g.large.search is $0.178 (about $130), gp3 storage is $0.122 per GB a month, and every Serverless indexing or search OCU is $0.24 an hour (about $175 a month). A 200 person company on two m7g.large data nodes pays about $202 a month before anyone builds the connectors.

That workload is small. A few hundred employees produce an index of a few gigabytes, and the AWS line item is modest. We work the bill through with the rates AWS publishes in its own price list and say plainly what the invoice leaves out. We sell InSearch, a finished product that competes with building on OpenSearch, so where OpenSearch is the cheaper and better choice we say that too.

Drive Slack Notion Confluence Jira Salesforce

Cited to source docs

Permission-aware · never trains on your data

Why it works

What your team gets with Amazon OpenSearch Service pricing

Provisioned domains bill per node hour

Every data node and dedicated cluster manager node has an hourly rate whether it serves one query or a million. Partial hours bill as full hours, and storage is billed on what you provision, not what you fill.

Serverless bills per OCU hour

Indexing and search compute are metered separately in OpenSearch Compute Units at $0.24 an hour each in US East. One indexing plus one search OCU running all month is about $350 before storage.

The AWS bill is the engine only

OpenSearch indexes what you send it. Someone still builds the Slack, Drive and Jira connectors, keeps document permissions in sync and writes the step that turns results into an answer.

What it handles

One search, a cited answer, scoped to you

InSearch searches across every connected app, checks your permissions, and writes one clear answer with citations back to the exact source documents.

  • Lists on-demand hourly rates for the instance types a small search domain uses, read from the AWS price list
  • Converts them into monthly figures and prices storage on gp3, OR1 managed storage and Serverless
  • Explains OCU billing for OpenSearch Serverless, including the new option to scale a collection group to zero
  • Works out a monthly bill for 200 employees of internal search on three different setups
  • Names the build work the AWS invoice does not include, so the total cost is honest
Answer Cited

Written answer

Full-time employees get 20 days of PTO per year plus 10 company holidays1, requested in Workday with manager approval2.

Only sources you can access

CF People Handbook ยท Time Off [1]
DR PTO-request-process.pdf [2]
Drive · Slack · Confluence Never trains on your data

Why InSearch

One search across every app, with a cited answer

Not eight separate search boxes, not a wall of blue links. InSearch unifies your apps and returns one written answer with citations, scoped to exactly what you can see.

One search, every app

Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce searched in a single query, so you stop opening a different search box for each tool.

A cited answer

A written answer in plain language with inline citations back to the exact source docs, so you can trust it and verify it instead of reading a page of links.

Permission-aware

Google Drive, Slack and Gmail access carries over item by item and is enforced at query time. For Notion, Confluence, Jira, Salesforce and SharePoint the admin chooses at connection whether everyone or only the admin sees their content. It never trains on your data.

Compared

Amazon OpenSearch Service rates side by side

Read from the AWS Price List API for Amazon OpenSearch Service, US East (N. Virginia), on-demand, on November 17, 2026. US dollars. Monthly figures multiply the hourly rate by 730 hours.

Item Published rate About per month What it buys Fits
t3.small.search $0.036 per hour $26 2 vCPU burstable, 2 GiB memory A test domain. Burstable nodes are not meant for steady production load
m7g.large.search $0.135 per hour $99 2 vCPU, 8 GiB memory, Graviton Data or cluster manager nodes for a small production index
r7g.large.search $0.178 per hour $130 2 vCPU, 16 GiB memory More memory per node for vector fields and heavier queries
or1.large.search $0.209 per hour $153 OpenSearch Optimized node backed by managed storage Indexing heavy domains, with storage at $0.024 per GB a month
gp3 EBS storage $0.122 per GB a month $2.44 for 20 GB Provisioned disk per node Most provisioned domains
Serverless OCU $0.24 per OCU hour $175 per OCU Indexing and search compute, metered separately Teams that do not want to size or patch nodes
Serverless storage $0.024 per GB a month $0.24 for 10 GB Managed storage behind a collection Any Serverless collection
InSearch Team / Business / Scale Per user $20 / $32 / $49 per user billed annually Connectors, permission-aware search and cited answers Teams that want employee search without a build

Instance memory figures are from AWS instance type documentation. Reserved Instances for one or three years lower the hourly rate. Semantic enrichment OCUs are also $0.24 an hour and process about 45 MB of English text each. Engine versions on extended support add $0.0065 per normalized instance hour. Data transfer is billed at standard AWS rates, and traffic between nodes inside a domain is not charged.

How much does Amazon OpenSearch Service cost per month?

A one node test domain on t3.small.search costs about $26 a month plus storage. A small production domain on two m7g.large.search data nodes costs about $197 a month plus about $5 of gp3 storage. OpenSearch Serverless with one indexing and one search OCU always on costs about $350 a month. Every figure is the hourly rate from the AWS price list times 730 hours.

AWS says on its OpenSearch Service pricing page that you pay only for what you use with no minimum fee. That is true per hour, and it also means a node bills around the clock until you delete the domain. A search index for employees is rarely idle long enough for that to matter, so treat the hourly rate as a fixed monthly cost.

Three line items make up almost every small bill: instance hours, provisioned storage, and data transfer out of AWS. Dedicated cluster manager nodes, UltraWarm, cold storage and Reserved Instances only become relevant once the index grows into hundreds of gigabytes, which internal search for a few hundred people does not reach.

How is OpenSearch Serverless priced?

OpenSearch Serverless meters compute in OpenSearch Compute Units, separately for indexing and for search, at $0.24 per OCU hour in US East. Storage is $0.024 per GB a month. AWS bills OCUs by the hour with per-minute granularity, and its own worked example on the pricing page puts one indexing OCU and one search OCU at about $176 a month each.

The newer part is collection groups. The Serverless scaling documentation now lets you set the minimum OCU for indexing and search to zero, so an idle collection pays only for storage. The trade is a cold start on the first request after idle time. For employee search, where the first query of the morning should come back in under a second, most teams will keep a minimum above zero, which brings the bill back near $350 a month.

Serverless removes node sizing, patching and version upgrades. It does not remove the connectors, the permission model or the answer layer.

These are our estimates, not AWS quotes. Assume 200 employees and a 10 GB index of documents, messages and tickets, about 20 searches per person per working day and 22 working days, so 88,000 queries a month. Query volume barely moves an OpenSearch bill because you pay for capacity, not per search.

  • Minimum test domain. One t3.small.search node and 10 GB of gp3. $26.28 plus $1.22, about $28 a month. No replica, so one node failure takes search down.
  • Small production domain. Two m7g.large.search data nodes with 20 GB of gp3 each. $197.10 plus $4.88, about $202 a month. One replica of every shard survives a node loss.
  • Multi-AZ with Standby. Three r7g.large.search data nodes, three m7g.large.search cluster manager nodes and 20 GB of gp3 per data node. $389.82 plus $295.65 plus $7.32, about $693 a month. AWS does not charge extra for the Standby feature itself.
  • Serverless. One indexing and one search OCU always on plus 10 GB of storage. $350.40 plus $0.24, about $351 a month.

If you add semantic search through automatic semantic enrichment, encoding a 10 GB corpus once is roughly 228 OCU hours at 45 MB each, about $55, then a little more as documents change. InSearch on the Team plan is $20 per user billed annually, $4,000 a month for the same 200 people. On the invoice OpenSearch is far cheaper. The next section is why the invoice is not the whole cost.

What is not in the OpenSearch bill?

OpenSearch indexes JSON documents you send it and answers queries. For employee search that leaves a list of work on your side:

  • A connector and sync job for every source, Slack, Google Drive, Confluence, Gmail, Jira, Salesforce, with OAuth, pagination, rate limits and deletes handled.
  • Document level permissions copied from every source and enforced on every query, so nobody sees a file they cannot open in the original app. OpenSearch has fine grained access control for its own users, not a mirror of Google Drive sharing.
  • Chunking, embeddings and an answer step with citations if people expect answers rather than ten blue links.
  • Monitoring, version upgrades, index mappings and on-call for when a connector breaks.

Suppose a competent engineer takes three months to ship this for five sources, then spends one day a week keeping it alive as APIs change. At a US engineering salary that is far more than the AWS line. The build vs buy internal search engine breakdown walks through the full arithmetic.

It is the right choice when search is a feature of a product you ship, when your data already flows through AWS, or when a platform team wants control over ranking, mappings and the hourly bill. It is also the natural landing place for teams leaving Amazon Kendra who want to stay inside AWS.

It is the wrong choice when the goal is to let employees find answers across the SaaS tools they already use and nobody owns a search platform. Then the cost that matters is the engineering time, not the $202 a month. Permission-aware AI search is the part that takes longest to build right, and it is what InSearch ships on day one with connectors for Drive, Slack, Notion, Confluence, Gmail, Jira and more. Start a trial and point it at two sources to compare against a prototype on OpenSearch.

Good questions

Questions about Amazon OpenSearch Service pricing

No. Amazon OpenSearch Service is pay as you go with no minimum fee, so you pay for every node hour and every GB of storage you provision. The smallest t3.small.search node is $0.036 an hour in US East, about $26 a month. Free tier eligibility depends on your AWS account terms, so check the billing console.
OpenSearch Serverless costs $0.24 per OCU hour in US East, billed separately for indexing and search, plus $0.024 per GB a month of storage. One indexing and one search OCU running all month is about $350. Collection groups can now scale to zero OCUs when idle, at the cost of a cold start.
For a small index the managed bills land in the same range, a few hundred dollars a month. Amazon OpenSearch Service bills per node hour inside your AWS account, while Elastic Cloud bills by deployment size or serverless compute units. The bigger cost for either is building connectors, permissions and the answer layer.
An OCU, OpenSearch Compute Unit, is the billing unit for OpenSearch Serverless and for features such as direct query and semantic enrichment. AWS prices it at $0.24 an hour in US East. Serverless meters indexing OCUs and search OCUs separately, so a collection always on uses at least one of each.
It depends on whether you want a component or a product. OpenSearch, Azure AI Search, Algolia and Pinecone are parts you build on. InSearch is a finished product that searches Drive, Slack, Notion, Confluence, Gmail, Jira and more with permissions enforced and cited answers, priced per user with no build.

Explore more

More ways teams find answers with InSearch

Give your team one place to find every answer.

One search across all your company apps, a clear cited answer, scoped to exactly what each person can see, and never trained on your data.

See pricing

One search across every app · cited answers · permission-aware · never trains on your data