GitHub, with boundaries
Choose repositories for each sandbox. Access starts read-only; allow changes when you need them.
About GitHub access
Linux development sandboxes, on your computer or another.
Your editor, your terminal. One place to bring it all together.
Available for macOS and Linux
Give your projects their own Linux VM, with the CPU, memory, and storage you choose.
Keep your favorite editor and terminal. Open a project and get straight to work.
Bring local and remote sandboxes together. Work from one place, across your computers.
A WORKFLOW THAT FEELS LIKE YOURS
Create a sandbox, connect your tools,
and pick up where you left off.
Start it here. Run it there. Keep track of both.
The tools you know, with room to work elsewhere.
A server in your sandbox. A preview in your browser.
THE DETAILS, TAKEN CARE OF
Repositories, credentials, and backups.
Managed in the same place.
Choose repositories for each sandbox. Access starts read-only; allow changes when you need them.
About GitHub accessKeep credentials in your computer’s credential store. Choose the sandboxes and HTTPS domains that can use them.
How secrets workSave local sandboxes to an archive. Restore a backup as a new sandbox, ready to pick up again.
About backupsGet Silo. The VM runtime, Linux image, and Git tools come with it.
Release notesNo. Choose your preferred editor and terminal in Silo. Open a project from Files, or use SSH access with a compatible editor or coding agent.
Install Silo on both computers. Enable SSH and Allow remote management on the host, then connect from your computer. Keep Silo running on the host. Manage its GitHub account, secrets, and backups there.
Remote setup guide →Your files survive stops, restarts, and app updates. Quitting Silo stops its local VMs and preserves their files; VMs on other computers keep running.
No. GitHub is optional. You can create a sandbox and work in its terminal without connecting an account.