burstdevelopers

The building starts here.

LESS IMPLICIT.
MORE POSSIBLE.

The guides, tools and primitives to build a private network with explicit trust. From your first identity to your first encrypted object.

Start the quickstart Explore architecture ↗

GoOIDCgRPC / TLSStarlark

YOUR FIRST BUILD↗

# From the Burst Kit workspace
$ sh scripts/check.sh
$ sh scripts/build.sh dev

# Six purpose-built commands
burst            # control + console
burstnode        # storage peer
burstpolicy      # local signing
burst-policy-worker
starburst        # explain + simulate
burstworker      # offline runsc jobs

Next: configure a real OIDC provider and TLS identities.

Choose your starting pointDevelopment ecosystem

01 / GET STARTED

Your first
Burst network.

Build the toolkit, configure identity and walk the encrypted-object lifecycle.

02 / WRITE POLICY

Make your
rules executable.

Signed Starlark policies, trusted context, modules and bounded simulation.

Talk to the
control plane.

Routes, scoped authorization, CSRF protection and mutation idempotency.

[ THE TOOLKIT ]

Small boundaries.
Big possibilities.

Understand what each component owns, what it implements and where the next integration begins.

burstThe workspace

burstauthIdentity & access

burstsecurityTrust at the boundary

burstnetThe encrypted data plane

burstrpcA shared vocabulary

burstcontractsRules that hold

starburstPolicy, made expressive

burstdecentraappThe execution layer

burstlibCommon ground

Understand the boundaries.

GOOD DOCS
INCLUDE THE LIMITS.

Read what’s implemented, what’s bounded and which acceptance checks remain. Development capabilities are documented as development capabilities.

Implementation status ↗Troubleshooting ↗