Platform Docs

Governed execution and replay for real-time systems.

ByteOr combines a bounded transport substrate, deterministic pipeline execution, governance-aware runtime controls, and a hosted control plane. Start with the platform shape here, then move into the specific surface that matches how you build, operate, or investigate.

Start With What Is ByteOr Choose Your Path

The docs are organized in layers: understand the stack, learn the shared operator model, then drop into Cloud, Enterprise, OSS, or IndexBus for product-specific work.

The stack at a glance

Four layers, clear boundaries, and one shared execution story.

IndexBus

Apache-2.0 / MIT

Bounded shared-memory transport substrate

ByteOr OSS

Apache-2.0 / MIT

Deterministic spec, validation, lowering, and execution

ByteOr Enterprise

Commercial

Governance, replay, adapters, DataGuard, and operator tooling

ByteOr Cloud

Commercial SaaS

Hosted control plane for versions, bundles, deployments, and agents

Start with the platform

These are the shortest paths into the current docs corpus.

What Is ByteOr

Start with the four-layer stack, the two execution models, and the platform boundaries.

Architecture

See how IndexBus, OSS, Enterprise, and Cloud compose into one operating model.

Choose Your Path

Route evaluators, OSS builders, enterprise operators, and Cloud users to the right surface.

Operator loop

The shared lifecycle that ties authoring, deployment, and investigation together.

Author and validate

Start from one plan contract, choose SingleRing or LaneGraph explicitly, then validate before runtime work begins.

Compile and configure

Promote validated plans into immutable versions and pair them with environment-specific tuning or config bundles.

Deploy with approvals

Use Cloud or Enterprise workflows to target environments where approvals and policy gates apply.

Capture and replay

Investigate incidents from captured evidence, then replay in dry-run or governed execute mode when allowed.

Product Surfaces

Choose the surface that matches the work.

Core Concepts explains the shared model first. Cloud, Enterprise, OSS, and IndexBus then narrow the view to the actual deployment or integration surface.

Core concepts

Shared execution models, spec authoring, validation, governance, and the operator loop.

Cloud control plane

Organizations, agents, bundles, deployments, approvals, and hosted replay workflows.

Enterprise runtime

CLI-driven validation, governed rollout, tuning profiles, incident bundles, and replay.

OSS substrate

Deterministic pipeline specs, lowering, execution primitives, ABI surfaces, and rustdoc.

Transport layer

IndexBus shared-memory lanes, semantics, zero-copy data flow, and SHM layouts.

Steady-state operations

Use these paths once you are past orientation and working on live systems.

Cloud Quick Start

Draft, validate, version, bundle, enroll, and deploy through the hosted control plane.

Enterprise Governance

Understand approval-aware execution, policy gates, and governed enterprise actions.

Incident and Replay

Follow the capture, investigation, and replay path used in steady-state operations.

IndexBus SHM Transport

Review the transport substrate when you need host-level delivery and layout rules.

Canonical detail stays secondary

Reference is still part of the site, just not the front-door story.

Use the editorial docs for platform shape, product routing, and operator workflow. Move into reference only when you need the canonical contract or mirrored repo detail.

Reference Hub

Repo map, source-of-truth guidance, release and authoring policy, and indexes.

Synced Repo Docs

Jump directly into mirrored crate and repository docs when you need source-adjacent context.