Deterministic governance
for agentic AI systems.
InvarOS is not a monitor. It is not a probabilistic filter or post-hoc log aggregator. It is a governance substrate — mathematical, auditable, and deployable on real hardware from Kubernetes clusters to constrained edge routers.
[2026-07-10T13:30:17Z] INFO loading plugin: topology.so ... ok
[2026-07-10T13:30:17Z] INFO loading plugin: receipts.so ... ok
[2026-07-10T13:30:18Z] INFO topology scan complete
"tbom_version": "3.0.0",
"host_fingerprint": "ca1d805c0ee07910...",
"topology_fingerprint": "a92137f8a9d4161c...",
"nodes_discovered": 14,
"edges_discovered": 3
[2026-07-10T13:30:18Z] INFO receipt generated — tbom_v3.0.0
[2026-07-10T13:30:18Z] INFO host: GL-MT3000 / OpenWrt (mips_24kc)
Authentic output from invarosd running on a GL-MT3000 OpenWrt edge router. TBoM 3.0.0 artifact emitted. No cloud connection required.
Not a monitor. Not a guardrail. Infrastructure.
The enterprise AI security market is saturated with API proxies, prompt filters, and post-hoc observability dashboards. These tools are easily bypassed by direct connections, custom sockets, or secondary agent channels. InvarOS takes a different position.
- API proxy — bypass with direct TCP socket
- Probabilistic prompt filter — bypass with rephrasing
- Post-hoc log aggregator — governance after the fact
- Cloud-dependent — offline environments unsupported
- Application tier — sits above the execution layer
- Deterministic — mathematical verification, not heuristics
- Infrastructure layer — beneath applications and agents
- Air-gap capable — operates autonomously, no cloud required
- Evidence-generating — cryptographic receipts at every step
- Deployable today across enterprise, server, edge, and micro-edge environments
One platform. Two implementation layers.
InvarOS is a single, coherent platform built in two complementary layers. Neither replaces the other — the native runtime grounds the enterprise platform in physical reality.
InvarOS Enterprise
The mature governance platform. Includes the proprietary mathematical verification core, policy compilation to zero-knowledge schemas, Topology Bill of Materials (TBoM) generation, commitment arcs, evidence pipelines, Kubernetes ValidatingAdmissionWebhook enforcement, and asynchronous air-gapped federation.
invarosd
The portable native daemon and plugin runtime. Designed to deploy across enterprise, server, edge, and micro-edge environments without architectural modification. Loads capabilities dynamically via a C ABI plugin boundary. Produces TBoM artifacts and cryptographic receipts without a cloud connection.
What InvarOS does today.
The following capabilities are implemented, tested, and operational.
Topology Bill of Materials (TBoM)
A formal representation of the operational topology of an AI system — infrastructure, execution topology, agents, tools, capabilities, trust relationships, evidence, and governance boundaries. TBoM 3.0.0 artifacts emitted by invarosd per observation epoch, with topology and host fingerprints.
Cryptographic Receipts
HMAC-SHA256 receipts generated per execution event. CycloneDX 1.6 CBOM, in-toto statement envelopes, and ZK compliance claim wrappers produced continuously.
Mathematical Verification
C++20 Eigen-based proprietary mathematical solver. Structural analysis, cycle verification, transient distribution computation, and entropy constraint enforcement. Implementation is confidential.
Native Plugin Architecture
invarosd loads capabilities dynamically at runtime via a strict C ABI isolation boundary. Shared objects (.so files) attach to the daemon without recompilation or service restart. The topology discovery plugin and receipts plugin are operational. This boundary enables proprietary mathematical solvers to be distributed as protected compiled plugins while the host daemon remains separately deployable.
Kubernetes Admission
ValidatingAdmissionWebhook handler with SLSA annotation validation, hardware attestation checks, and cross-tenant namespace trust contract enforcement. Fail-closed posture.
Air-Gapped Federation
Asynchronous recognition model. Governance (Rule), Commitment (Proof), Federation (Recognition). No consensus protocol. No WAN broadcast. Cross-tenant trust via cryptographic fingerprints only.
Policy-to-ZK Compiler
Canonical policy set dynamically compiled to ZK compliance JSON schemas. Policy fingerprints generated deterministically. 95 compiler tests pass. Schema correctness verified.
Integrations
OpenTelemetry exporter, Kubernetes admission controller, LangChain adapter, MCP stdio server, FastMCP HTTP server. Helm chart with rootless security posture.
Real artifacts from real hardware.
The following topology evidence was produced by invarosd during live deployment. These are not mock data or synthetic fixtures.
Dell x86_64 Linux Server
GL-MT3000 OpenWrt Edge Router
MAC addresses and final IP octets have been masked for publication. Node IDs and fingerprints are truncated. Structural composition and interface types are authentic.
What you can engage with today.
Available now
- Pilot design and scoping conversations
- Architecture assessments and topology extraction engagements
- Consulting on AI governance infrastructure requirements
- Research and academic collaboration
- Integration design for MCP, LangChain, and Kubernetes environments
- Regulated and disconnected deployment planning
- Strategic partnership discussions
Coming shortly
- Public software packaging and distribution
- Self-service download portal
- Community edition release
- Documentation site and developer portal
The platform exists and substantial engineering has been completed. Public packaging is in progress. Contact us to discuss early access.