{
    "product": "Cenvero Stratum",
    "generated_at": "2026-08-03T07:17:50+00:00",
    "format": "cenvero-docs-v1",
    "document_count": 1,
    "documents": [
        {
            "slug": "introduction",
            "title": "Introduction",
            "category": null,
            "url": "https://www.stratum.cenvero.com/docs/introduction",
            "headings": [
                {
                    "level": 1,
                    "text": "Introduction"
                },
                {
                    "level": 2,
                    "text": "What you get"
                },
                {
                    "level": 2,
                    "text": "Every node is the same node"
                },
                {
                    "level": 2,
                    "text": "The two bridges"
                },
                {
                    "level": 2,
                    "text": "How a node is managed"
                },
                {
                    "level": 2,
                    "text": "Where to go next"
                }
            ],
            "word_count": 581,
            "markdown": "# Introduction\n\nCenvero Stratum is a software-defined networking platform for bare-metal\ninfrastructure. It runs your entire network stack — switching and routing,\nDHCP and DNS, load balancing, firewalling, and multi-host clustering — as a\nsingle agent on the servers you already own. There is no external controller to\noperate, no hardware appliance to buy, and no per-port licensing.\n\nA node runs a single agent. It handles packet processing in the kernel, manages\nthe host's network interfaces — putting them back if something changes them\noutside Stratum — and coordinates with its peers in a high-availability cluster.\nThe result is a complete, self-contained fabric that behaves the same on one\nserver or a thousand.\n\n## What you get\n\n- **In-kernel data plane.** Packet processing happens in the kernel on a fast\n  path for line-rate forwarding, with an optional kernel module that detects\n  out-of-band changes to managed interfaces so the agent reconciles them back to\n  their intended configuration.\n- **Batteries included.** DHCP, authoritative DNS, an L4 load balancer, a\n  zero-trust firewall, BGP edge routing, and per-tenant bandwidth control ship in\n  the box — no add-ons.\n- **Multi-host by default.** Nodes form a high-availability cluster and stretch a\n  VXLAN overlay across hosts, racks, and data centers. A workload's endpoint\n  keeps its addressing as it moves between hosts.\n- **Operable.** A single configuration file per node, one CLI\n  (`cenvero-str-ctl`), and a management panel for fleet-wide releases, updates,\n  and licensing.\n\n## Every node is the same node\n\nThere is one kind of node. It hosts workloads and attaches their endpoints to\nthe fabric, *and* it routes traffic between the fabric and the outside world —\nNAT, upstream route exchange, north-south load balancing. You do not pick a node\ntype at install, and any node can take on any of that later.\n\nWhat limits a node is how many interfaces it has free, not what it was\ninstalled as. See [Nodes and Interfaces](/docs/nodes).\n\n> Earlier versions split nodes into Compute and Gateway. That split has been\n> removed, and a node updating from an older version is migrated automatically.\n\n## The two bridges\n\nStratum separates management traffic from workload traffic on every node:\n\n- A **management bridge** — agent control, clustering, and HA signalling.\n- A **workload bridge** — carries workload traffic.\n\nThis keeps the control plane reachable even when workload networks are\nsaturated or misconfigured.\n\n## How a node is managed\n\nThe agent reads a single configuration file per node, keeps its local\nstate on disk, and writes its own logs. You drive it locally with\n`cenvero-str-ctl` and centrally from the management panel.\n\n## Where to go next\n\nIf you are evaluating or learning:\n\n- **[Concepts](/docs/concepts)** — the vocabulary used throughout these docs.\n- **[How Stratum Works](/docs/architecture)** — the components, the packet path, and what survives what.\n\nIf you are deploying:\n\n- **[Installation](/docs/installation)** — get the agent onto a node and activated.\n- **[Quick Start](/docs/quickstart)** — define a network and attach your first endpoint.\n- **[Configuration](/docs/configuration)** — the node configuration model in depth.\n\nIf you are running it:\n\n- **[Operations](/docs/operations)** — logs, updates, health checks, troubleshooting.\n- **[Monitoring](/docs/monitoring)** — which source answers which question.\n- **[Security Model](/docs/security)** — what is enforced, and your hardening checklist.\n- **[Licensing](/docs/licensing)** — plans, activation, and enforcement.\n- **[API Reference](/docs/api)** — the agent's local REST/operator API.\n\nThe whole documentation set is also downloadable as JSON from the\n[documentation index](/docs), for offline reading or indexing.\n\n> Stratum is licensed software. Installation and binary downloads require a\n> valid license — see [Licensing](/docs/licensing) to get one.\n"
        }
    ]
}