[bldr]
open core

the engine is open source

the technology at the core of bldr — the distributed, content-addressed build system — is free and open. run the daemon on your own hardware, inspect every line, and never worry about lock-in. bldr cloud is orchestration on top, never a gate in front.

[01·what's open]

the whole build system

object store & dag runner

the content-addressed store, the block/ref layers, garbage collection and the pure dag runner.

cli & daemon

the bldr cli and the daemon that owns the store, schedules pods and exposes the grpc api.

function library

fs, blob, http, oci and pod functions — the deterministic building blocks of every build.

[02·self-host in minutes]

one daemon, one binary

start a node, register a workspace, and run your first cached build. the first run populates the cache; the next resolves entirely from content-addressed objects.

~/ · quickstart
$bldr-daemon serve
[bldr] node up · peer 12D3KooW…
$bldr ws register
registered 4 members ok
$bldr build
✓ build complete cid:fs:…q7f2
a taste of the function library
fs.mergeoverlay-merge filesystem trees
fs.diffdiff two trees → delta
fs.filter_globinclude / exclude by glob
fs.tarpack a tree into a tar blob
blob.untarunpack a tar into a tree
blob.compressgzip / zstd a blob
http.getfetch a url → blob
oci.rootfsassemble image layers → tree
pod.dagrun an isolated pod dag

…and many more. see the full reference.

[ where the line sits ]

everything needed to build is open source and always will be. the proprietary layer is purely orchestration — the automation, collaboration and governance a fleet needs. you can run the core forever without ever paying us a cent.

built in the open

issues, patches and ideas are welcome. bldr is early software — the best time to shape it is now.