Who builds Befall
One person, one Wyoming LLC, and a set of claims that are only worth the name attached to them.
Updated 2026-09-01
Short answer
Befall is built by Bora Esen and operated by Stimilon LLC (Wyoming, USA). The comparison pages on this site are written by the same person who writes the code, each naming the date its sources were read, including the places where a competitor does something Befall does not.
Who builds Befall?
Befall is built by Bora Esen, and operated by Stimilon LLC, a Wyoming limited liability company registered at 30 N Gould St, Ste R, Sheridan, WY 82801. It is one person’s project rather than a team’s, which is worth knowing before you depend on it: it means replies come from the person who wrote the code, and it means the bus factor is one. The source for the hosted service is closed; the MCP server package is published on npm as befall and its repository is public under MIT.
Who writes the comparison pages, and how are they checked?
The same person who writes the code. Each comparison page names the date its sources were read and links them, because a claim about a competitor is only worth the person standing behind it. MCP Agent Mail’s page says outright that it has a pre-commit guard Befall does not, and that its glob-aware TTL path reservations do the same job ours do. The Claude Code agent teams page exists because two rounds of research told us agent teams locks source files, and reading Anthropic’s own documentation on 2026-08-14 showed the locking it describes is over the shared task list — the correction is on the page rather than quietly fixed.
The category table was built by querying the GitHub API for each project rather than copying a directory listing, after the first attempt produced repositories that turned out to be dormant, renamed, or nonexistent. Stars, licence, and the last commit on the default branch are read per repository, because a project’s pushed_at moves on any branch push and makes dead work look current.
Why was Befall built?
Because three coding agents were run against this repository on day one and they collided immediately. The first refusal in Befall’s own room was real, not a demo: one agent held apps/web/app/api/**, a second asked for a file inside it, and the claim came back refused with the file both claims covered named. Whether the second agent then edited anyway is something Befall cannot see, and never claims to. Everything on this site follows from that being a coordination problem rather than a merge problem — isolation defers the collision to merge time; a refusal moves it to before the edit, for the agents that ask.
What does the privacy claim actually commit to?
Source code and diffs never leave your machine. What does: repo-relative paths, branch names, commit SHAs, the list of dirty paths, claims, task titles and free-text descriptions, and the messages you explicitly send. Those last two are text you author, they are stored, and source pasted into one is uploaded with it — “metadata only” is a claim about your source, not about everything you type. Realtime broadcasts carry an empty payload inside an envelope that still routes room, topic, event kind, actor and timestamp; subscribers re-fetch the change through the authenticated API. That is a design constraint, not a policy promise, which is why it is stated the same way on the security page and in the code.
How do I reach a human?
Open an issue on the befall-mcp repository — it reaches the same person, in public, where the answer is useful to whoever hits the problem next.