Proof, not promises

BuildExponential.Org runs on BuildEx OS.

The fastest way to trust an operating system is to watch its makers run their own company on it. We do. The platform that would run your company already runs ours - and it's open source, so none of this is a claim you have to take on faith.

Company #0

Our company runs on it

Charter, decisions, pipeline, and the content engine all live as markdown in a BuildEx workspace on our own machine - the same product we ship. The guarantees below aren't slogans; they're invariant tests in this repo.

Open

MIT, top to bottom

The kernel, the sync service, the connectors, the toolkit - all readable, forkable, auditable. The invariants are in the tests.

Portfolio

One operator, many ventures

The same operator runs several ventures from the same cockpit. Honest states included - a killed venture stays on the map as killed.

The invariants - enforced, not promised

The safety story is in the code.

Five things about BuildEx aren't marketing lines - they're release-gate test suites that must stay green for the build to ship.

We never touch your model keys

Credentials stay in the keychain seam

Your agent authenticates with your own subscription - BuildEx never sets a provider key or reads your credentials to run it. No secret reaches a repo, a log, a synced file, or a config artifact.

secrets suite ↗
The gate holds

Nothing outward without a human

Connectors are read-only by construction; every outward or irreversible action waits in Pending until you tap. Both are enforced by the gates suite.

gates suite ↗
Never lose work

A conflict is always recoverable

The sync engine backs up conflicting work byte-for-byte before it does anything else. Losing an operator's edit is a test failure.

sync-safety suite ↗
Companies stay isolated

One company can never read another

Every company is its own repo behind a server-side permission matrix and per-machine tokens. No cross-company read is possible - the suite asserts it.

permission-matrix suite ↗
Trust surfaces don't guess

The map is rendered, not hallucinated

The org map, history, and admin views are derived from repo state with zero LLM in the path - same repo, same bytes, every render. What you're trusting is deterministic, not a model's summary.

determinism suite ↗

The map is the pitch.

Every completed transformation slots into the same public shape - problem, the loops we installed, the artifacts, and the numbers. Watch us build in the open, then decide.

charter - the thesis decisions/log.md - every call, superseding pipeline - the funnel as files sources/ - the senses

Download BuildEx