Backplane

Backplane connects independently developed services into an operable installation. Services describe what they expose; operators connect hooks to activities, react to events, change live configuration and inspect the resulting runs. The console combines platform administration with pages supplied by those services.

Choose a starting point

Your goal	Start here
See a working installation	Run hello and formatter
Build a Go service	Service SDK, then components
Build a module's console pages	Frontend packages and standalone module development
Connect existing capabilities	Bindings and rules
Deploy only the infrastructure you need	Deployment modes
Call the platform programmatically	Generated clients and RPC reference
Investigate an incident	Telemetry, audit, errors

What the platform provides

• A Go lifecycle and dependency tree, typed configuration, optional infrastructure drivers, public route declarations and an internal service API.
• Catalog and instance status, revisioned configuration, hook bindings, event rules, workflow runs and administrative schedules.
• A React component system, schema forms, editors, charts, observability views and a module contract with standalone development.
• Durable PostgreSQL audit, bounded OTLP forwarding and read access to independently operated telemetry stores.
• A cookie-authenticated console and generated TypeScript clients for every backplane.console.v1 service.

Backplane does not deploy services or replace a scheduler such as Kubernetes. It does not own the OpenTelemetry Collector or telemetry storage. Application-specific products can use its APIs and UI packages without moving their domain model into the platform.

Documentation contract

Guides describe the current implementation. The reference section is synchronized from the repository's authoritative API and package documentation on every site build. The site is published from a release tag; its version appears in the header. Release archives include the same static site for independent hosting.