Four ways out
| What you want | How |
|---|---|
| A finished build as a zip | Download the artifact from the build. Secrets and dependencies are already excluded. |
| The working files | They are in ~/.myrax/workspaces/<project-id> on the paired computer, as a normal git repository. |
| Everything at once | myrax-connector export <dir> <name> packs a workspace from the command line. |
| Moving to another Myrax account | Transfer export and import move a workspace between accounts, including its history. |
The workspace is just a folder
This is the part worth internalising: a build is not stored in a format only Myrax understands. It is files on your disk, in a git repository, with the history of every checkpoint. You can open it in an editor, push it to a remote, or delete the Connector and keep working.
What stops working when you stop
- Published sites stay published. What you shipped is not taken down because a subscription lapsed.
- Snapshots stay with the build. A frozen build that passed remains restorable.
- New builds stop. The room, the queue and the gate need the server.
What to do before you go
- Download the artifact of anything you might want to redeploy.
- Copy the workspace folder somewhere that is not the Connector's home directory.
- Note any custom domain pointed at a build, so you can repoint it at whatever you move to.
Publishing and addresses: Publishing. The reasons a domain can keep working: Custom domains.

