Architecture Overview

    ByteOr Cloud is a hosted control plane for pipeline drafts, immutable versions, config bundles, deployments, enrolled agents, artifacts, and replay workflows.

    Core model

    The control plane keeps authoring, versioning, and runtime operations separate.

    • Drafts are mutable authoring records.
    • Versions are immutable compiled records.
    • Config bundles attach environment-specific runtime posture to a version.
    • Deployments bind a version plus bundle to an environment and target enrolled agents.
    • Artifacts and replay preserve the incident and audit trail after runtime activity.

    Control-plane layers

    The product is organized around a small set of cooperating layers.

    • API service: authentication, RBAC, tenancy scoping, request validation, and write-path orchestration.
    • Worker service: asynchronous jobs such as spec ingest, deploy-bundle build, artifact ingest, replay, retention, and metering aggregation.
    • Shared domain crates: tenancy, approvals, deployments, artifacts, config bundles, and audit rules used across the backend.
    • Object storage and database persistence: durable records for versions, bundles, deployments, artifacts, and generated deploy-bundle blobs.
    • UI application: operator-facing flows for workspace setup, authoring, version creation, config bundles, deployments, incidents, and settings.

    Ownership tree

    Every runtime and governance object resolves through the same tenancy tree.

    Organization
└── Project
    └── Environment
        ├── Agent
        ├── Pipeline Draft
        ├── Pipeline Version
        ├── Config Bundle
        ├── Deployment
        ├── Approval
        └── Artifact

    That ownership tree drives API paths, RBAC checks, approval posture, and retention boundaries.

    Hosted surfaces

    The intended hosted surfaces are:

    • https://cloud.byteor.com for the production UI
    • https://api.byteor.com/v1 for the production API
    • https://cloud.staging.byteor.com and https://api.staging.byteor.com/v1 for staging
    • https://cloud.dev.byteor.com and https://api.dev.byteor.com/v1 for development

    OIDC callbacks should stay on the cloud.* origin rather than the API origin.

    Provenance
    Need the canonical source?
    Use the public hub to orient yourself, then jump to repo-owned docs or rustdoc when you need contract-level detail.
    Source-of-truth modelRepo docs index