Security
Your code stays on your machines.
The By Dawn daemon on your machine connects out to By Dawn and claims the work you send it. Nothing on our side opens a connection into your machine.
The boundary
What runs where.
The agents work on your machines. The board runs on ours.
- It connects outThe daemon keeps an outbound connection to By Dawn and claims jobs itself. It only listens on localhost.
- Sign-ins and keysClaude Code and Codex sign-ins stay on your machine and By Dawn never collects them. An API key, such as Grok’s, can live in your org’s encrypted secret store.
What By Dawn holds
The plan and the proof.
The board, the docs and what each mission did.
- What we keepThe board, docs, memory, test library, and each mission’s log and proofs.
- Private spacesA docs space can be private to named members, teams or projects, with viewer, editor and admin roles. Private spaces are filtered out of search inside the search itself.
How it works
The trust boundary
- Your machineThe agent, your repo, your sign-ins.
- OutboundThe daemon connects out and claims work.
- By DawnThe board, docs, memory and proofs.
Questions
Asked about security.
Can we self-host By Dawn?
Not today. The agents run on your machines; the board runs on ours.
Does By Dawn see our code?
Your repo is checked out on your machine. By Dawn holds the mission’s log and proofs, and the pull request lives in your own GitHub or Azure DevOps.
The waitlist