Catalyst Data to decision at the speed of the mission. Sovereign. Peer-to-peer. Source-available.
Catalyst is the Common Operational Data Layer (CODL): a sovereign, governed data fabric that connects every sensor, every data repository, and every decision system to a peer-to-peer mesh. Without relocating data, without rip-and-replace, without vendor lock.
Decision speed is a data problem.
Sensors don't talk to each other. C2 systems can't ingest data they don't natively interpret. The kill chain stretches across architectures that were never designed to talk. Coalition sharing is buried in caveats. The constraint isn't collection or analytics. It's the data layer between them.
A peer-to-peer governed data fabric.
Catalyst is the CODL: a self-organizing mesh that connects every node to a common contract. Data moves up to analytics, down to operators, sideways to peers, and back. No central hub. No transitive trust. Sovereignty preserved at every node.
How Catalyst Works
Each workspace manages its own data. Catalyst routes it through the Common Operational Data Layer, protected in transit, and delivers it to the operators who need it. Click any workspace to connect or disconnect.
Workspace Alpha Workspace Bravo Workspace Charlie Five properties that define Catalyst
The CODL is a self-organizing mesh that distributes compute, inference, and storage across every node. Five architectural properties make it work at mission tempo.
Peer-to-peer, not a hub
Every Catalyst node is an equal participant in a self-organizing mesh. Adding a node adds capacity, not load on a center. No chokepoint to jam, lose, or defend. The mesh is greater than any single node and grows stronger with every node added.
Sovereign by default
Commercially developed by Orbis, operated by the government on government infrastructure, source-available to authorized customers. No SaaS dependency. No vendor-in-the-loop for operational decisions. Identity bound at every node against each participant's own authority.
Adapter-based integration, not rebuilds
New sources are added by writing adapters that translate vendor formats into Catalyst's common contract. Adapter source is open wherever licensing and security allow. No single vendor (Orbis included) owns any integration.
Bidirectional fabric, not a pipeline
Data moves up to analytics, down to operators, sideways to peers, and back. Sensor returns flow to fire control. Enriched tracks flow back to the sensor's owning C2. Operators receive enrichment inside the tools they already use.
The edge is the same as the center
Catalyst runs as a physical or virtual appliance, or as a tenant in a customer's Kubernetes cluster. The same fabric and tooling from a forward-deployed node in a conflict zone to a rack in the enterprise data center. Each node operates autonomously under degraded comms.
Mission scenarios
Two exemplars that show what the CODL delivers in operational context: a coalition air defense, and a Stryker company at the contested edge.
Coalition Integrated Air Defense
A multinational IADS protecting against a layered threat. National radars, allied sensors, Patriot, NASAMS, civil air-traffic feeds, overhead cueing. Catalyst presents one unified track picture to every authorized C2 without any participant surrendering custody of underlying data. Each nation's data carries its own Cedar policy, evaluated locally at the consuming node. Inter-enclave traffic is post-quantum secure today. No transitive trust. No central authorization service to compromise.
Stryker company at the edge
A Stryker company conducting distributed operations beyond reliable enterprise connectivity. Every vehicle is a Catalyst node. Imagery classification, RF geolocation, change detection, and threat-warning models run where data is captured. The fabric carries enriched outputs, not raw feeds. When reach-back drops, the company keeps fighting under its own Cedar policy. When comms return, accumulated enrichment syncs to theater and back down to the edge.
Technical foundations
Open, standards-based, sovereign-friendly components. Inspect every line of the stack. Replace any layer on your own terms.
Transport
Pub/sub-query peer-to-peer mesh with key-expression routing, embedded query and storage, and store-and-forward under disconnect. No broker. No central message bus.
Cryptography
TLS 1.3 and QUIC with hybrid post-quantum key exchange combining classical X25519 with ML-KEM-768 (NIST FIPS 203). Protects against classical, quantum, and harvest-now-decrypt-later attacks.
Authorization
Cedar policy language, evaluated locally at every node on every request. Deterministic, schema-validated, formally analyzable. Policies are signed data; updates propagate without redeploying code.
Identity
Mutual TLS with federated identity authorities. Each participant brings its own. Every node authenticates every peer on every request. No transitive trust.
C2 integration
Adapter framework for native sensor and effector protocols. Cursor-on-Target (CoT) and Variable Message Format (VMF) bridge to ATAK/WinTAK, FAAD C2, Anduril Lattice, and allied tactical systems.
Runtime
Single Kubernetes appliance, ARM or x86, ~512MB RAM and one CPU core minimum. Air-gap capable. Reconverges automatically when comms return.
Deployment Model
Catalyst's default deployment runs on Orbis-managed commercial cloud infrastructure - but its decentralized architecture means it can run on any infrastructure your mission requires.
Default: Managed Commercial Cloud
Out-of-the-box, Catalyst runs on Orbis-managed commercial cloud infrastructure - providing global reach, DDoS resilience, and zero-trust network controls with no client infrastructure required to get started.
On-Premises Deployment
Catalyst nodes can be deployed on client-managed hardware - bare metal, VM, or container - in any facility. No dependency on external services once deployed. Fully air-gappable for classified and sensitive compartmented environments.
Sovereign & Private Cloud
Deploy on AWS GovCloud, Azure Government, C2S, or any sovereign cloud of choice. Catalyst has no hard dependency on a specific cloud provider - it runs wherever Envoy and Linux run.
Tactical Edge & DDIL
Catalyst nodes operate autonomously without persistent connectivity - designed for denied, disrupted, intermittent, and limited (DDIL) environments at the tactical edge where centralized architectures fail.
Services That Deliver Catalyst
Products don't deliver outcomes. People do. Orbis engineers build the adapters, deploy the nodes, and design the architecture that makes Catalyst operational for your mission, not just installed.
Producer Adapter Development
Custom adapters that connect your existing sensors, systems, and data sources into Catalyst nodes, translating protocols and normalizing data so it flows into the CODL automatically.
Consumer Adapter Development
Purpose-built adapters that deliver CODL data to your mission applications, dashboards, and C2 systems, in the format and cadence your operators need.
Node Integration & Deployment
End-to-end deployment of Catalyst nodes into your environment, from architecture design through operational handoff, including cross-domain and coalition configurations.
Architecture & ICD Design
C2 architecture, CODL design, data strategies, and interface control documents. We design the environment your Catalyst deployment thrives in.
The organization that governs how its data moves, governs how fast it can act.
Catalyst is the CODL. Sovereign. Peer-to-peer. Source-available. Deployed today, wherever the mission is fought.