Self-host developer tools
Developer tools are happiest on a machine that keeps its disk, its caches, and its running processes. These recipes put them on an exe.dev VM behind exe.dev's HTTPS proxy, so only people you share with can reach them, with no passwords to manage.
Results
All results →No recipe matches yet. Ask Shelley to set it up →
All 12 Developer tools recipes
code-server
Developer tools
Your editor in a tab. Your projects right where you left them.
VS Code in your browser, with code-server
Linux desktop
Developer tools
Xfce, Chrome, and coding agents on a VM you open in a browser tab.
A Linux desktop in your browser
Docker Engine
Developer tools
Keep the docker CLI. Send the builds, the containers, and the fan noise to a VM.
Use exe.dev as a remote Docker host
BuildKit
Developer tools
One big VM with a warm build cache that every laptop and CI job builds on.
Run a remote Docker builder with a warm BuildKit cache
Crabbox
Developer tools
Remote test boxes for you and your coding agents, on your exe.dev account.
Use exe.dev VMs as Crabbox boxes
Dev, Test, Prod
Developer tools
You can build, test, and deploy on exe.dev.
Dev, Test, Prod: Choose One, Two, or Three
Forgejo
Developer tools
Self-hosted Git forge with exe.dev SSO
Forgejo
Gitea
Developer tools
Self-hosted Git forge with exe.dev SSO
Gitea
GitHub Actions
Developer tools
Every job on a fresh copy of a warm VM, billed by the second.
Run GitHub Actions jobs on exe.dev, a fresh VM per job
marimo
Developer tools
An open source reactive notebook
Spinning up a Marimo Notebook
Nix remote builder
Developer tools
One big VM that builds for every machine and caches what it built.
Run a Nix remote builder and binary cache on exe.dev
Tangled knot
Developer tools
Your git repos on your own VM, with tangled.org on top.
Host your Tangled repos on your own knot
Frequently asked questions
Who can reach a tool I deploy?
Only you, until you share the VM. exe.dev's proxy asks visitors to log in before any request reaches your VM.
Can I open the same VM in my desktop editor?
Yes. Every VM is reachable over SSH, so VS Code Remote-SSH, Cursor, Zed, and JetBrains Gateway all work. See VS Code.
Don't see what you need?
Anything that runs on Linux runs on exe.dev. Describe it, and Shelley sets it up on a new VM.