Every rule, every second
Every rule against every instrument or every device, on a one‑minute window — not the dozen someone had time to wire up.
OliverDB is a fast columnar analytics database that ships as one small binary. Embed it in your application or run it as a service — same engine either way. Its cellular design scales from a tiny in-process instance to a coordinated cluster, and every query is scoped by the key that carries it, so it’s safe to hand to an untrusted agent.
Every query arrives as a program rather than a string, so the engine can fuse five hundred of them into a single pass over the data instead of five hundred scans of it.
Every rule against every instrument or every device, on a one‑minute window — not the dozen someone had time to wire up.
Rank, score and cut inside the engine, so what comes back is the decision and the reason for it, already sorted.
Agents stop exploring one hop at a time. The swarm poses every question together and every answer lands in the same pass.
See the SwarmOne request grounds an agent completely: its exact scope, the live schema, and runnable examples drawn from real data. Productive in a single round-trip.
Every key carries a policy. Before a query runs, it is rewritten to fit that scope — narrowed, not just rejected — so a least-privilege key is safe to hand to an untrusted agent.
The engine ships as one small process. Run it in‑process or as a service while durable data remains in shared object storage — no heavyweight runtime to operate.
The unit of scale is a stateless cell over shared storage. Add or replace cells without moving durable data — no sharding project, no rebalancing, and no data loss when a cell disappears.
Vectorized, multi-threaded scans and pre-aggregated rollups return grouped answers in milliseconds — with standout single-core efficiency.
Query in standard SQL or a compact JSON DSL — same execution, same security path. Text search (terms, phrases, fuzzy, regex) is built in, right next to your aggregates.
A conductor poses a task; a swarm of small models queries the Engine directly and returns grounded, cited findings.
The same policy discipline — rewrite, don’t validate — in front of Postgres, Snowflake, and ClickHouse.