Your work. In its own space.

Linux development sandboxes, on your computer or another.
Your editor, your terminal. One place to bring it all together.

Available for macOS and Linux

Isolated

Give your projects their own Linux VM, with the CPU, memory, and storage you choose.

Familiar

Keep your favorite editor and terminal. Open a project and get straight to work.

Connected

Bring local and remote sandboxes together. Work from one place, across your computers.

Explore the app
Try the sidebar to explore Silo.Read-only · Sample data

A WORKFLOW THAT FEELS LIKE YOURS

Less setup. More building.

Create a sandbox, connect your tools,
and pick up where you left off.

Start it here. Run it there. Keep track of both.

THE DETAILS, TAKEN CARE OF

Give each sandbox what it needs.

Repositories, credentials, and backups.
Managed in the same place.

GitHub, with boundaries

Choose repositories for each sandbox. Access starts read-only; allow changes when you need them.

About GitHub access

Secrets, scoped to the job

Keep credentials in your computer’s credential store. Choose the sandboxes and HTTPS domains that can use them.

How secrets work

A way back

Save local sandboxes to an archive. Restore a backup as a new sandbox, ready to pick up again.

About backups

Make room for your next idea.

Get Silo. The VM runtime, Linux image, and Git tools come with it.

Release notes

macOS

Apple Silicon

macOS 14 or later · M-series Macs

Download for macOS.dmg

Open the disk image and drag Silo to Applications.

First launch on macOS

Silo is not notarized. If macOS blocks the first launch, open System Settings → Privacy & Security and choose Open Anyway.

A few things to know.

Do I need to change my editor?

No. Choose your preferred editor and terminal in Silo. Open a project from Files, or use SSH access with a compatible editor or coding agent.

How do remote computers work?

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 →
What happens when I stop a sandbox?

Your files survive stops, restarts, and app updates. Quitting Silo stops its local VMs and preserves their files; VMs on other computers keep running.

Do I need to connect GitHub?

No. GitHub is optional. You can create a sandbox and work in its terminal without connecting an account.

Silo, in action

Product demonstration with sample data. Editor and computer views are illustrations. Read the transcript