01
Deployment
Cloud, self-hosted, or hybrid — including on-prem and air-gapped.
NXLABS platform · Apostle
Computational-defined infrastructure
Apostle.
The platform that powers our computational-defined infrastructure — for the digital fabrication and deployment of cyber-physical systems. Economic modeling, live observability, and security-first orchestration, unified in one operational layer.
Runtime
ApostleOS v2.4 · Apr 2026
Deployment
Cloud · Self-hosted · Hybrid
Access
By demo · Professional / Enterprise
Built by
NXLABS — Nexus Laboratory, Arkadia's research arm
One operational layer
The layer above your stack.
Apostle doesn't replace your existing infrastructure, data, or security tooling. It sits above them — reading, modeling, and orchestrating — so cost, continuity, and security decisions are reconciled where they actually happen.
Pillar 01
Economic Modeling
Cost-to-risk accounting across every workload, surfaced at decision time — not in a quarterly review. Each service, deployment, and dependency is priced continuously against operational and breach-probability risk.
- ·Per-workload cost accounting
- ·Risk-weighted forecasting
- ·Budget vs. actual with drift alerts
- ·Scenario modeling
APOSTLEOS · COST MODEL
still
▨ preview
Pillar 02
Live Observability
Unified telemetry across infrastructure, data, and security layers. Anomaly detection calibrated per-tenant over a baseline window. Works as an aggregator over Datadog, Splunk, Grafana, or direct-from-source collectors.
- ·Cross-layer correlation
- ·Per-tenant baseline tuning
- ·Runtime anomaly detection
- ·Provenance tracking
APOSTLEOS · LIVE TELEMETRY
still
▨ preview
Pillar 03
Security-First Orchestration
Every orchestration decision routes through the security posture model. No deployment, scaling action, or data movement executes without posture reconciliation. Integrates with existing CI/CD and runtime controllers.
- ·Policy-aware scheduling
- ·Posture reconciliation
- ·Deployment gating
- ·Runtime quarantine
APOSTLEOS · POLICY GRAPH
still
▨ preview
How it works
Four phases. Roughly six weeks to live.
Typical integration: 2–4 weeks of baseline calibration, live orchestration in the following 2–4 weeks. Longer in regulated environments.
01 · Instrument
Connect your telemetry
ApostleOS reads from your existing observability, cost, and security sources. No agents unless you want them.
02 · Model
Calibrate the baseline
Economic and risk models tune to your workloads over a 2–4 week baseline window. Human-in-the-loop review.
03 · Orchestrate
Enable runtime gating
Orchestration decisions start routing through the posture model. Begin in observe-only, move to enforce.
04 · Observe
Operate continuously
Unified cross-layer telemetry, drift alerts, and quarterly review cadence with Arkadia engineers.
Fabrication to deployment
From model to machine, one runtime.
APOSTLE · DIGITAL FABRICATION
loop
Integrations
Sits on top of what you already have.
First-class support across major cloud, observability, security, and data platforms. Custom source adapters available for regulated or air-gapped environments.
CloudAWS · Azure · GCP · DigitalOcean · On-prem supported
ObservabilityDatadog · Splunk · Grafana · New Relic · Direct-source
SecurityCrowdStrike · Palo Alto · Microsoft Sentinel · SentinelOne · Custom
DataSnowflake · Databricks · BigQuery · Postgres · Any JDBC
OrchestrationKubernetes · Nomad · systemd · Bare-metal
CI / CDGitHub Actions · GitLab · Jenkins · ArgoCD · Custom hooks
Security & posture
Built for regulated, air-gapped environments.
Security-first orchestration is a pillar, not a bolt-on. Apostle runs where your workloads run and reconciles policy where decisions happen.
Posture · hardened by design
02
Policy
Security decisions modeled and enforced in the same runtime as cost and continuity.
03
Isolation
Runs above your stack without exfiltrating it — adapters, not data lifts.
04
Review
Quarterly engineering review; federal / regulated-sector variants on request.