Drop-in replacement for Elasticsearch or OpenSearch,
simpler and more scalable.

Hydrate from your snapshots

Point Infino at an Elasticsearch or OpenSearch snapshot repository. Infino reads the snapshot, not the live cluster, and writes each live document into an Infino table as open Parquet.

• The snapshot repository you already keep is the source. Name the index. Infino loads the snapshot you name, or the newest successful one that holds it.
• Each live document becomes a row. Source fields become columns. The id the index knew the document by is kept.
• Only the documents the snapshot still holds are loaded. Nested documents stay inside their parent.
• Vector fields can come along as columns. Infino can also embed the text on the way in.

Keep OpenSearch. Replace Lucene.

An OpenSearch plugin puts Infino under the APIs you already run. The cluster, the REST surface, and OpenSearch Dashboards stay. Nothing is written to Lucene.

• Index names, mappings, and settings stay in cluster state.
• Every document lives in an Infino table, on Infino Cloud or in your own bucket.
• Bulk, search, and get keep the OpenSearch actions you already call.
• Nodes no longer hold the durable copy. Dashboards aggregations keep working on this path.

talk to an engineer →

Your queries keep working

Point existing clients at Infino, or keep them on OpenSearch with the plugin. Compatible Query DSL requests keep the same shape. Unsupported Lucene features are listed below.

// POST /tickets/_search · compatible request
{
  "query": {
    "bool": {
      "must":   { "match": { "body": "disk full" } },
      "filter": { "term":  { "level": "error" } }
    }
  },
  "size": 10
}

// → same request shape and client · answered from Parquet in your bucket

vs elasticsearch / opensearch →

SQL joins on search results

In Infino a ranked search is a relation, so it joins against the rest of your data in the same statement.

SELECT   p.name AS plan, count(*) AS tickets
FROM     hybrid_search('tickets', 'body', 'disk full',
                       'embedding', :q, 5000) h    -- keyword + vector, fused
JOIN     accounts a ON a.id = h.account_id          -- a plain table
JOIN     plans    p ON p.id = a.plan_id
GROUP BY p.name
ORDER BY tickets DESC;

-- → search joined to your business tables

hybrid search →

A file-and-compute operating model

Elasticsearch and OpenSearch organize data as shards on cluster nodes. Infino separates durable Parquet in object storage from the compute that reads it.

• Table schemas replace index mappings. A new field becomes a column.
• Object storage provides durability, while local RAM and NVMe hold disposable cached data.
• Retained data grows in the bucket and query compute scales independently.

Compatibility and tradeoffs

• Compatible Query DSL requests, bulk and index clients, BM25, vector, and hybrid search retain familiar interfaces.
• Data lands as open Parquet and gains DataFusion SQL over the same rows, with object-storage retention and independently scaled compute.
• Infino dashboards can be built through the MCP server. infino-analytics is a reference implementation. OpenSearch Dashboards stays on the plugin path.

vs elasticsearch / opensearch →

Migration questions