Skip to main content
Let’s get Infino running in a few minutes. We’ll build a small knowledge base (a handful of help-center notes) and search it four ways: by keyword, by meaning, by both at once (hybrid), and with SQL. Pick your language; each step builds on the one before it.
Prefer the terminal, or driving Infino from a coding agent? The CLI does all of this — create, ingest, search, and query — without writing code.
1

Install

The Rust examples build Arrow data, and update / delete take DataFusion predicates (col, lit), so add these alongside infino, matching the Arrow and DataFusion versions Infino uses (Arrow 53 and DataFusion 53 for infino 0.1.x):
Run cargo tree -p infino to check the versions if you are on a newer Infino.Infino also installs the mimalloc global allocator by default. If you embed it in a process that already sets a global allocator, turn it off: infino = { version = "0.1", default-features = false }.
2

Connect

First, open a connection. "memory://" keeps everything in memory for this walkthrough; point it at "./data" or an "s3://bucket/prefix" URI when you want your data to stick around.
3

Create a table

Now create a table. You give it a schema and say which columns to index: a full-text index on the text, and a vector index on the embedding.
4

Add data

Let’s add a few notes. The embed helper stands in for a real embedding model so the example runs on its own. It’s a 16-dim one-hot by topic (0 = billing, 1 = appearance). Your own embeddings will be dense and higher-dimensional; see Embeddings.
5

Search it

Now the part you came for. The same table answers every kind of query: keyword, meaning, hybrid, and SQL.
Each search returns Arrow rows. With this tiny corpus, the body of the rows you get back looks like this:
Expected output
keyword matched the BM25 terms; semantic ranks the billing notes first; hybrid fuses the two rankings, so the exact keyword match leads while the semantically close note follows; sql returns the two help-center rows. From here, feed the retrieved passages to your model as grounding context.

Next steps

Core concepts

The mental model: one Parquet copy, indexed and queried four ways.

Guides

Tables, embeddings, indexing, search, and storage.

Integrations

LangChain, Vercel AI SDK, CrewAI, and MCP.

SQL Reference

Query and compose search with SQL.
Last modified on July 6, 2026