Myrax docs

Where your code runs

The split between your machine and this server decides every other answer in these docs. The work happens where your files are; the server keeps the room.

The split between your machine and this server is the whole architecture, and it decides every other answer in these docs. Short version: the work happens where your files are, and the server keeps the room.

On your computer

  • The files. Source, assets, and the git history of the workspace. They are written by the agent into a folder you chose.
  • The agents. Claude Code, Codex, OpenCode and Ollama run as processes on that machine, under your user account.
  • The model traffic. Requests go from your machine to your provider, with your key or your existing sign-in.
  • The browser test. A local Chromium opens the built page and measures it. No page ever leaves the machine to be tested.
  • The device token. What pairing gives you, stored locally, used to poll the queue and post results back.

On the Myrax server

  • Your account and sessions. Email, a password hash if you set one, and session records.
  • The room. Projects, plans, approvals, seat logs, member roles, and the queue the daemon polls.
  • The build record. The measured values behind each browser check, the diff summary, model usage per seat, and the checkpoint reference.
  • The artifact. Once a build passes, the zip is uploaded so you can download or publish it later without the original machine present.
  • Published sites. If you publish, the files are served from here on your address or your own domain.

What never reaches the server

ThingWhy it stays local
Your provider passwordsThe agent signs in on your machine. Myrax asks it to work; it does not authenticate on your behalf.
Keys saved in ProvidersStored on that computer and passed to the agent as an environment variable for that run only. See Providers and keys.
The full file contents before a buildThe agent reads the workspace locally. What comes back is a diff summary, not your source tree.
Excluded secrets in an export.env, *.pem, *.key, node_modules and .git are filtered out of every zip.

Why the split is worth the friction

A hosted builder has to hold your keys or bill you for tokens. Both are avoidable if the model runs on your machine, and avoiding them changes the economics: a build costs whatever your provider charges you, which after a subscription is often nothing per request, and Myrax has nothing to mark up.

The friction is real and worth naming. You have to install something, keep a daemon running, and your computer has to be awake when you build. A browser tab is easier. The trade is that your code and keys never sit on someone else's disk, and the folder is yours when you leave.

An honest limit

The server does see what it needs to coordinate: project names, briefs, plans, check logs, and the artifact once you build successfully. If you would not put a sentence in a brief, do not put it there. For the full list of what is stored, see the privacy page.