Early access · v0.x
lbr CLI
Drive every product from your terminal — create clusters, networks and registries, add monitors, send mail. One binary, one login.
CLI docsThe toolchain
Four ways in. One platform behind them.
Early access · v0.x
longbridge-go SDK
A typed Go client for the whole Public API — the same client the CLI and the Terraform provider are built on.
SDK docs Beta
Terraform provider
Declare your platform as code — clusters, networks, registries, email domains — then plan and apply like any other resource.
Provider docs OpenAPI
Public API
One documented OpenAPI surface at /api/v1 with one API-key model, across every product. Everything the Console does, you can too.
API referenceTry it
The same grammar, every product.
Provision a control plane, a mesh, a registry, a monitor, or a sending domain — with one command each, one login, and one place to look when it breaks.
lbr cp create prod --tier large # a Kubernetes control plane
lbr mesh create staging # a WireGuard network
lbr registry create acme # a private registry
lbr uptime monitors create --url ... # an uptime monitor
lbr email domains add acme.com # a sending domainOne auth model
One key. Every product. Scoped by grants.
A lngbr_ API key — or your CI's OIDC identity — authenticates
every product on one wire. Personal keys act as you; machine-user keys carry exactly
their grants. Narrow a key at mint; it never exceeds its owner's access.
- Personal keys for you, machine-user keys for automation.
- OIDC exchange for CI — nothing long-lived to leak.
- Fine-grained grants and custom roles, enforced everywhere.
- Narrow at mint — a key never exceeds its owner's access.
Read the docs, grab a key, ship.
The CLI, SDK, and provider are documented with worked examples. The API is one OpenAPI surface.