Platforms
Four engines. Every system we ship runs on one of them.
A product list grows without limit. A platform list does not. Naming the engines is what keeps fifteen systems from reading as fifteen unrelated bets — and it is how you tell which capability you are actually buying.
§ 01
Manifold
State reconciliation and digital twins for physical systems.
Sense, model, simulate, actuate, reconcile — with explicit state authority between sensor, simulation, and operator, and drift detection when predicted and observed state diverge. Knowing which source is authoritative, and flagging it when they disagree, is the hard part.
Runs on Manifold
PRODIGY (all three configurations) · SerpenOps & SerpenSky · Box Truck Sprinter · City Manifold
§ 02
Cortex
Document, signal, and knowledge intelligence.
Ingest, classify, verify, synthesize — with source tiering and provenance retained end to end. The tiered model built for Global Health IQ separates official agency, local health department, academic, news, and AI-generated material, and holds a hard firewall between verified and inferred. That is the platform standard.
Runs on Cortex
Global Health IQ · Intelligence Hub · FokusRead · Member Berries
§ 03
Aya
The agentic and cognitive layer.
Routed strategies — planner, executor, memory retriever, verifier, router, self-critic — with persistent project memory and a public evidence harness that writes reasoning traces you can inspect. Models recommend; the operator decides. Every discarded alternative keeps its rationale.
Runs on Aya
Work OS · OpenAya · the assistant surface inside every other system
§ 04
Vault
Sovereign storage and identity.
Bring your own storage — Drive, Dropbox, Box, OneDrive, or a local filesystem — connected through an OAuth 2.0 PKCE bridge so client applications never touch raw provider tokens. The institution's data stays where the institution already keeps it.
Runs on Vault
Data Vault · MyDigital · the persistence layer beneath the other three engines
Explore Data Vault →Next step