TLDRocket
Sign in

OpenSearch veterans launch Infino. Here’s why it matters for agent builders.

The New Stack Adrian Bridgwater

OpenSearch veterans launched Infino, a retrieval layer for AI agents. It aims to replace a messy stack of search, vector, warehouse, and ETL tools with one copy of the data.

Based on reporting by The New Stack, Adrian Bridgwater — read the original for the full story.

Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error

Infino has formally launched an agent retrieval platform built around a simple bet: AI agents don’t query data like humans do, so the data stack should stop pretending they do.

CEO Ekechi Nwokah says agents are now the “largest new consumer of data since the web browser,” but they’re still being fed through systems built for older patterns: SQL warehouses, keyword search, vector search, and ETL pipelines that keep everything in sync. Infino’s pitch is to collapse that mess into one layer over object storage, with one copy of the data and one interface for ranked search, exact counts, joins, filters, aggregation, and reasoning.

That matters because agents are noisy readers. They ask lots of small questions, often in parallel, then stitch the answers together themselves. Each round trip eats context, time, and money. Infino argues that a warehouse here, a search engine there, and a vector database somewhere else just forces the agent to do extra work, and then do more work to verify the first round of work.

The company’s answer is to store data as Apache Parquet on object storage and put search indexes beside the Parquet footer. That lets other Parquet tools keep reading the same files, while Infino’s engine handles retrieval. The company says its open source core is Apache-2.0 on GitHub, and its hosted Infino Cloud can point at existing Parquet data without teams having to build infrastructure first.

Infino also says it has built targeted inference models into the retrieval loop, because agents spend a lot of time bouncing between query formulation, search, validation, and retries. On the business side, Nwokah claims the platform is about 10x cheaper than traditional search or analytics infrastructures for its intended workload, and its own published comparison pegs it at about 10.5x cheaper than Elasticsearch and 23x cheaper than OpenSearch.

The startup says it is already handling multi-billion-document use cases in people search, document processing, product analytics, and security, with one unnamed customer putting petabytes of company data on the system. Nwokah and his co-founders, who include veterans of Amazon, Google, LinkedIn, and AWS OpenSearch, are betting that the next big retrieval problem is not better search in isolation. It’s making agents stop juggling five tools just to answer one question.

My take — AI-written commentary, not fact-checked reporting

This is the right complaint at the right time: agent stacks are already turning into a small museum of duplicated tooling. One copy of the data, one policy layer, fewer bits of ceremonial glue code — that’s not sexy, but it’s how systems stop becoming a support ticket. The industry keeps calling that “simplification” while adding another gateway, which is a pretty advanced joke.

Read more about this at: The New Stack

Related stories

The daily briefing

Every AI story that matters, in your inbox by 8am.

TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the day in two minutes. Follow companies and topics for alerts, or get the briefing in Slack. Free, no spam, unsubscribe anytime.