Arxi Enterprise
This document describes the current Arxi Enterprise status for teams evaluating self-hosted or managed-cloud enterprise deployments.
Who Arxi Enterprise Is For
- Self-hosted enterprises that need strict control of identity, policy, evidence boundaries, and operations.
- Platform teams embedding Arxi into a broader governance/compliance runtime.
What Arxi Enterprise Is Not
- Not a fork of Arxi OSS evidence semantics.
- Not a replacement for Arxi OSS canonical encoding/hash/verifier behavior.
- Not a claim that managed-cloud operational signoff is fully complete today.
Current Enterprise Features
Implemented in This Repository (Arxiu)
- Sidecar enterprise modes and fail-closed enterprise config validation.
- Enterprise identity header extraction and policy-gate middleware.
- Control-plane ingress-check bridge (
/v1/enterprise/ingress/check) and sidecar boundary hook emission (/v1/enterprise/sidecar/hooks). - Managed-cloud writer-lease assertion enforcement for mutating paths.
- Enterprise-aware readiness mode (
probes.readiness_mode=storage_and_enterprise) that fail-closes/readywhen enterprise control-plane health dependency is unavailable. - Stable enterprise boundary vocabulary and conformance tests.
- End-to-end tests proving fail-closed deny behavior without evidence-state mutation regressions.
Primary references:
crates/arxi-sidecar-config/src/config.rscrates/arxi-sidecar-config/src/validation/enterprise.rscrates/arxi-sidecar/src/middleware/enterprise.rscrates/arxi-sidecar/src/control_plane_bridge.rscrates/arxi-sidecar/src/contract.rscrates/arxi-sidecar/tests/enterprise_vocabulary_contract.rscrates/arxi-sidecar/tests/enterprise_control_plane_e2e.rssystem-tests/tests/suites/sidecar_enterprise.rs
Implemented in Asset-Core (Enterprise Runtime)
- Enterprise service crate (
arxi-enterprise) with platform-backed: authz, quota, managed fleet, cloud operations/resilience, governance, audit-chain, operations hooks, and usage export. - Enterprise control-plane runtime crate (
arxi-enterprise-control-plane) with active HTTP routes for ingress checks, fleet, recovery drills, replication/SLO assessment, governance, audit export, and sidecar hooks. - Generated/deterministic OpenAPI for control-plane contracts.
- Low-cardinality control-plane telemetry families and metrics endpoint.
Primary references:
Asset-Core/products/arxi/crates/arxi-enterprise/src/lib.rsAsset-Core/products/arxi/crates/arxi-enterprise-control-plane/src/server.rsAsset-Core/products/arxi/crates/arxi-enterprise-control-plane/src/spec.rsAsset-Core/products/arxi/crates/arxi-enterprise-control-plane/src/telemetry.rsAsset-Core/Docs/products/arxi/architecture/arxi_enterprise_architecture.mdAsset-Core/Docs/products/arxi/architecture/arxi_enterprise_control_plane_architecture.md
OSS Boundary
Arxi Enterprise extends Arxi OSS without changing core evidence authority:
- OSS evidence semantics remain deterministic and auditable.
- Enterprise layers may admit/deny operations, but do not rewrite evidence math.
- Enterprise dependencies remain outside core OSS invariant crates.
Planned / Remaining Enterprise Work
The remaining enterprise backlog is operational promotion work rather than core repository feature implementation.
- XR-03 managed-cloud rollout and operations evidence finalization.
- XR-04 final joint security signoff across platform/security/operations.
- Promotion packet consolidation and go/no-go governance signoff.
Primary references:
Asset-Core/Docs/products/arxi/roadmap/arxi_enterprise_remaining_execution_backlog.mdAsset-Core/Docs/products/arxi/operations/arxi_managed_cloud_rollout_hardening_evidence.mdAsset-Core/Docs/products/arxi/security/arxi_enterprise_joint_security_signoff.md