Myrax docs

Security model

What the architecture protects, and more usefully, what it does not. The gaps are what let you decide whether to trust a build of yours to this.

This page says what is protected and, more usefully, what is not. A security page that only lists strengths is marketing; the gaps are what let you decide whether to trust a build of yours to this.

What is protected

  • Provider credentials stay on the paired machine, or are supplied per run and never written to the server database.
  • Sessions are server-side records with a 30-day expiry, and the cookie is HttpOnly, SameSite=Lax, and Secure in production.
  • Device tokens are stored hashed. The Connector only ever sends the token, never the hash.
  • Ownership checks run on the server for every project, artifact and member action, so a modified client cannot read another account's build.
  • Rate limiting applies to sign-in and code requests, keyed by request and by email, so a guessed code or a mail flood is bounded.
  • Export filtering removes .env, keys, dependencies and git history from every zip.
  • On-demand TLS only issues a certificate for a hostname the application has already approved, which is what stops a stranger pointing a random domain at the server and getting a certificate.

What is not protected

GapWhat it means for you
The agent runs with your user accountInside the workspace it follows the brief, but it has the file permissions you gave it. Run it under an account that only has what it needs.
Published pages are publicNo password, no access list. Never publish a page containing data you would not post publicly.
Briefs and plans are stored on the serverThey are part of the build record. Do not paste credentials into a brief.
The gate checks structure, not safetyA page can pass all eight checks and still have a broken link or a form that emails the wrong inbox.

Reporting a vulnerability

Write to the security address on the contact page, with what you found and how to reproduce it. Do not test against someone else's build; there is no permission for that and it turns a report into an incident.

What a session is, and is not

A signed-in session is a cookie plus a server record. Deleting the record ends access immediately; that is what logging out does. If someone else has your live cookie, they are you until it expires or is revoked, so sign out on a machine you no longer control.

The permissions an agent runs with are laid out in Permissions. Where data actually sits is in Where your code runs.