Elasticvue Alternative for Amazon OpenSearch
Elasticvue is a free, open-source GUI for Elasticsearch that also works with OpenSearch: cluster and shard overviews, index and alias management, snapshots, a REST tab, and document search and editing. It is maintained, with release 1.17.0 on 28 October 2026 and an Elasticvue 2 beta announced.
The alternative matters when your clusters are Amazon OpenSearch Service domains or Serverless collections. DynoTable signs every request with your AWS profile, SSO included, stages document edits as a diff you review, and runs SQL that joins an index to a DynamoDB table. For a cluster you run yourself with a password, Elasticvue is the better fit, and this page says where.
When to use Elasticvue and when to use DynoTable
| Your workflow | Choose |
|---|---|
| Elasticsearch, or a self-hosted OpenSearch cluster with a password | Elasticvue |
| Nodes, shards, snapshots, repositories and index templates | Elasticvue |
| A free, open-source client you can also run in a browser or Docker | Elasticvue |
| An Amazon OpenSearch domain, signed with your AWS profile or SSO | DynoTable |
| An OpenSearch Serverless collection | DynoTable |
| Review an edit as a diff, catch a conflicting write, revert later | DynoTable |
JOIN an index to a DynamoDB table, or GROUP BY the joined rows | DynoTable |
Signing in to Amazon OpenSearch
Elasticvue added AWS IAM support in version 1.8. A cluster connection takes an
access key ID, secret access key, optional session token and region, and its
source signs each request for the es service, which is what a managed domain
expects. Credentials are typed into the connection, so an SSO user copies
fresh temporary keys in whenever they expire.
A Serverless collection signs as a different service. AWS's client examples
for collections all use aoss
(AWS docs),
and Elasticvue's source fixes the service to es.
DynoTable reads your profiles from ~/.aws, SSO and aws login sessions
included, finds your domains and collections with them, and signs each request
for the right service. Nothing to paste, and temporary credentials refresh the
way the AWS CLI's do. The identity still needs data access on the domain or in
the collection's data access policy.
The other direction is DynoTable's gap. Its self-hosted endpoint is a URL with no username, password or API key, so a self-hosted cluster that requires one connects in Elasticvue and not in DynoTable.
Searching an index
Elasticvue's search page takes a query string, which it sends as a
query_string query, and lets you open and edit the full JSON body behind it.
Results show in a table you can download as JSON, and there are examples for
the query syntax.
DynoTable's index tab is closer to a table view. The Lucene box completes field names from the mapping and values from the index as you type, filter pills compile to query DSL, and a time range appears when the index has a date field. Raw mode takes a JSON query DSL body or a Lucene line, linted against the mapping, with saved queries and per-index history. Column sorts run on the server, a free-text search highlights the matching words, and Quick View shows a document without leaving the grid.
Editing documents
Elasticvue edits a document in place and saves it with
PUT <index>/<type>/<id>?refresh=true. The request carries no if_seq_no, so
a write someone made after you opened the document is overwritten. Bulk delete
goes out as one _bulk request.
DynoTable stages the edit: Pending changes shows a per-field diff, and you commit all of it or part of it. On a domain, the commit carries the version you read and stops on a concurrent change, which you can rebase. A Serverless collection has no version check, and the tab shows a Last-write-wins badge so you know. Every commit can be reverted from History. Bulk edit and bulk delete run over a selection or every document a query matches, staged the same way.
Joining OpenSearch and DynamoDB
Elasticvue has no SQL surface beyond its REST tab, where you can post to the
SQL plugin yourself. The plugin's joins are best-effort and do not aggregate
the joined result; on OpenSearch 2.19 a JOIN … GROUP BY we ran came back with
null counts and no error (the
Dashboards comparison has the
request and response).
DynoTable's SQL Workbench runs the join in the app, across engines:
SELECT c.country, COUNT(*) AS orders, SUM(o.amount) AS revenue
FROM dynamodb.orders o
JOIN opensearch.customers c ON o.customerId = c.customerId
GROUP BY c.countryAn index joins on a keyword, number or date field, and the other side can be a DynamoDB table or an index on another domain. The join runs on your machine, which bounds how many rows it can combine. OpenSearch SQL has the rules.
Cluster administration
This is Elasticvue's strongest ground and DynoTable's thinnest. Elasticvue shows nodes and shards, manages snapshots, repositories and index templates, and, on Elasticsearch only, users and roles.
DynoTable manages the index itself: create an index from ⌘K, change replicas and the refresh interval on a domain, delete an index behind a typed confirmation, and export its definition as a REST request or Terraform. It has no node, shard or snapshot views and no generic REST console.
Price and licence
Elasticvue is free under MIT, as a desktop app for Windows, macOS (Intel and Apple Silicon) and Linux, a browser extension for Chrome, Firefox and Edge, a hosted web version, or a Docker image. The web and Docker versions need CORS enabled on the cluster.
DynoTable is closed source. Its Free plan has no time limit and needs a free account; it includes browsing, OpenSearch index search, exports and MCP reads. A paid seat adds editing, the SQL Workbench, Smart Tables and the AI agent, from $9/mo billed annually ($108/yr), with a 30-day trial and no credit card. See pricing.
Try DynoTable on the same domain
Download DynoTable for macOS (Apple Silicon or Intel), Windows or Linux, turn on OpenSearch for your profile, and open an index from ⌘K. Connecting OpenSearch covers domains, Serverless collections and self-hosted clusters.
FAQ
Is DynoTable an Elasticvue alternative?
For Amazon OpenSearch, yes. DynoTable signs requests to domains and Serverless collections with your AWS profile, including SSO, stages document edits as a reviewable diff, and runs SQL that joins an index to a DynamoDB table. Elasticvue is free and open source, also covers Elasticsearch, and has more cluster administration: nodes, shards, snapshots and index templates.
Does Elasticvue work with Amazon OpenSearch Service?
Yes, for domains. Since version 1.8 Elasticvue can sign requests with an AWS access key, secret key, optional session token and region, and its source signs for the es service that managed domains use. Serverless collections expect the aoss service, and Elasticvue does not read AWS profiles or SSO.
Does Elasticvue check for conflicting edits?
No. Elasticvue saves a document with a PUT request that carries no if_seq_no, so a change someone made after you loaded the document is overwritten. DynoTable stages the edit and, on a managed domain, commits it with the version you read, so a concurrent change becomes a conflict you can rebase.
Is Elasticvue free?
Yes. Elasticvue is free and open source under the MIT licence, as a desktop app, a browser extension, a web version or a Docker image. DynoTable's Free plan is also free with no time limit and includes OpenSearch index search; paid seats start at $9 a month billed annually.
Related
- The best OpenSearch GUI clients roundup puts Elasticvue next to the rest of the field.
- The OpenSearch Dashboards comparison and the DocKit comparison.
Last verified 2026-10-29 against Elasticvue 1.17.0. OpenSearch is a trademark of LF Projects, LLC. Elasticsearch is a trademark of Elasticsearch B.V. AWS, Amazon OpenSearch Service and DynamoDB are trademarks of Amazon Web Services; referenced here for identification only.