The engine, run as a platform

The open-source repo is the engine, a library you embed. Enterprise is the same engine run as a service, in your cloud account or ours.

diff open-source enterprise

aspect open source enterprise
what it is a library you embed the engine run as a service
search BM25 · vector · SQL, hybrid same engine, same results
data your object store your object store, same files
runs as one process, in your app gateway + a worker per database
availability one node at least two nodes per database
isolation your process one OS process per database
access none, it is a library API keys + console
usage not tracked metered per request
support GitHub issues support + SLAs
license Apache-2.0 commercial

How the platform works →  ·  Pricing →

infino enterprise --list

gateway + api keys

Stateless auth, routing, and per-request metering in front of every database.

high availability

Every active database is served from at least two nodes.

process isolation

One worker process per database. Two databases never share one.

on-demand start

Workers start on the first request. An idle database costs only storage.

console

Accounts, API keys, and usage in one place.

your cloud or ours

Managed, or self-hosted in your account. S3, Azure Blob, GCS.

control plane on your bucket

Platform state is JSON on the bucket. No etcd or Postgres to run.

support + SLAs

Part of every enterprise agreement.

infino deploy --byoc

Runs in your cloud account

One build, managed or self-hosted. Point it at your bucket and everything stays in your account.

YOUR CLOUD ACCOUNT your application HTTPS gateway api keys · route · meter · stateless one process per database worker engine + cache worker engine + cache worker engine + cache reads · appends OBJECT STORAGE your bucket · the source of truth superfiles _platform/ nothing crosses the dashed line data, indexes, and the platform’s own state stay in the account

cat FAQ.md

is the enterprise engine a fork?

No. Workers run the same engine that ships on GitHub. Enterprise adds the layer around it: gateway, workers, keys, metering, console.

what does an install consist of?

Stateless gateway instances, a supervisor and workers per node, and a bucket. No metadata database, no coordination service.

in our own cloud, does anything leave our account?

No. The platform reads and writes your bucket and nothing else, including its own state. Backing up the bucket backs up everything.

how is it licensed?

The engine is Apache-2.0 and stays that way. The platform is commercial; terms depend on how you deploy it.