---
title: "Self-host developer tools"
description: "Run browser IDEs, Git servers, notebooks, and CI runners on a persistent exe.dev VM with HTTPS and exe.dev login in front."
url: https://exe.dev/deploy/category/dev-tools
---

# 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](/docs/proxy), so only people you
[share](/docs/sharing) with can reach them, with no passwords to manage.

## All 6 developer tools recipes

- [VS Code in your browser, with code-server](https://exe.dev/deploy/code-server.md): Your editor in a tab. Your projects right where you left them.
- [Dev, Test, Prod: Choose One, Two, or Three](https://exe.dev/deploy/dev-test-prod.md): You can build, test, and deploy on exe.dev.
- [Forgejo](https://exe.dev/deploy/forgejo.md): Self-hosted Git forge with exe.dev SSO
- [Gitea](https://exe.dev/deploy/gitea.md): Self-hosted Git forge with exe.dev SSO
- [Running a self-hosted GitHub Actions Runner](https://exe.dev/deploy/github-actions-runner.md): Log in easily into your CI environment
- [Spinning up a Marimo Notebook](https://exe.dev/deploy/marimo.md): An open source reactive notebook

## Frequently asked questions

### Who can reach a tool I deploy?

Only you, until you [share](/docs/sharing) 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](/docs/faq/vscode).

[All recipes](https://exe.dev/deploy.md)