Sovereign agent infrastructure for regulated work.
IOBOXX nodes run air-gapped or inside your VPC, with deterministic audit trails baked into the substrate. Bring your own models, your own keys, your own grants — and keep a hash-chained commitlog under every reducer call your agents make on your data.
Stories
Sovereign brain per twin
Each enterprise customer runs its own IOBOXX node with explicit, directional grants — never a shared mutable plane. Cross-twin memory walks always traverse an auditable boundary, and the per-twin commitlog is the regulator-grade record of every state change.
- Tenancy model
- one node per twin
- Audit primitive
- hash-chained commitlog
Cross-LLM resilience
Swap the SOTA model without touching the agent code or the memory layer. Because IOBOXX speaks open MCP, the runtime that calls the tools is interchangeable — Claude, GPT, Gemini, Llama, Mistral — and the typed objects, embeddings, and grants underneath stay exactly the same.
Read the story →BPMN-driven processes
Standard BPMN 2.0 process definitions, executable by agents and humans alike. Versionable, auditable, agentic where it makes sense and form-bound where regulators require it — all backed by the same deterministic commitlog the rest of the platform runs on.
Read the story →
What you can do next
Architecture review
A guided walk through the substrate, memory, agent, and grant layers with the IOBOXX team — tailored to your compliance posture, hosting model, and integration surface.
Book a review →Self-host playbook
Step-by-step from `spacetime publish` to first agent call, including air-gapped deployments, JWT/keychain configuration, and the production hygiene rules baked into the platform.
Read the playbook →Strategic brief
Why sovereignty matters in agent infrastructure and how the IOBOXX positioning differs from incumbent memory tools — written for procurement, security, and architecture reviewers.
Open the brief →