1. Your files
  2. Load
  3. Ask
Where is your data?
Where should the table live?

SOC 2 Type II. No rows pass through our API servers while loading.

Stored in Infino Cloud on this demo deployment, so treat it as ephemeral. For durable data, open an Infino Cloud account.

Your files go straight from your browser to the storage you chose; they never pass through our servers.

i

    The engine repository: a retrieval engine that stores data on object storage and runs SQL, full-text search and vector search over it. One file (a "superfile") is a valid Parquet file with BM25 and vector indexes spliced in; the supertable layer composes many superfiles into a queryable table with snapshot-isolated reads and an atomic-commit manifest.

    Both arms see the same files and get the same question. File Tools opens them one by one, the way a model typically does today. Infino searches them through a fast retrieval index, with subagents that take a question in plain English. Questions that send an agent across many files are where they come apart; one answered from a single named file usually comes out level.

    The arms answer the same question at once, and each panel settles the moment its own arm finishes.