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.
Strategy, decisions, clients and the content we publish all live as markdown in a BuildEx brain on our own machine - the same product we ship. The guarantees below aren't slogans; they're tests in this repo.
A desktop app you run yourself, forked from Orca and MIT-licensed like it. No server of ours sits between you and your company - there is nothing to trust us with.
Every repo you have given a brain shows up on one read-only screen. Honest states included - a business BuildEx cannot read says so, rather than quietly dropping off the list.
Five things about BuildEx aren't marketing lines - they're tests that run on every pull request, and the file is linked under each one.
The sharp edges - moving money, messaging real people, publishing - wait for you. BuildEx writes those rules into your agent's own .claude/settings.json and the agent runtime enforces them. It deliberately has no gate of its own, because a second decision path is a second thing that can disagree.
What your agent wakes up knowing is a plain scan of your files - no embedding step, no vector database, no model in the path. An unchanged brain renders byte-identical every time, which is the test.
company-context tests ↗Connect Stripe for two businesses and you get two keys, filed under two companies. A name that isn't a real company, or one that could walk out of its own folder, is refused rather than written to a shared slot.
plugin-credentials tests ↗.buildex/Saving is an ordinary git commit, restricted by pathspec to the brain. Whatever else is in your working tree - half-finished code, a branch mid-rebase - is not swept into it.
brain-git-paths tests ↗When a scheduled job opens a fresh workspace, the company's context and its gate rules are in place before the agent says anything - on every dispatch path, not just the one that was easy to test. An unprepared agent working on your company is the failure this one exists to prevent.
worktree-init tests ↗Our own company is the same ten folders of markdown you get on first run - the same files, in a repo we own. Watch us build in the open, then decide.