microsrv:~$
RUEN
Console

microsrv

use case · devbox

Develop in a Linux VM without configuring your laptop.

Build your tools into a base environment once, then create ready-to-code VMs for every branch, task, and CI job. Connect with SSH from VS Code, Cursor, or a terminal; preview over HTTPS at <vmId>.msrv.space.

Open consoleSee pricing
ssh · remote IDE
$ ssh -A feature-42@msrv.spacemicrosrv: connection to feature-42 establishedubuntu@feature-42:~$ mise use -g node@22 && npm test # open the same VM from your editor# cursor --remote ssh-remote+feature-42@msrv.space ubuntu@feature-42:~$ curl -I https://feature-42.msrv.spaceHTTP/2 200ubuntu@feature-42:~$

Use your preferred editor

Connect over SSH from VS Code, Cursor, JetBrains, Zed, or a standard terminal. The address remains stable across live migration.

  • Remote SSH

    Use ssh -A <vmId>@msrv.space without assigning a public IP to the VM.

  • cloud-init configuration

    Add runtimes, dotfiles, and SSH keys during the first boot so every VM is ready to use.

  • Live preview

    Serve the application at https://<vmId>.msrv.space with TLS termination already configured.

One VM per branch or job

Keep a long-lived development VM, then create additional VMs for features, reviews, and CI workers without adding configuration to your laptop.

  • Isolated workspaces

    Parallel development VMs can share a private network when needed or remain fully isolated.

  • CI workers

    Build servers and test runners get dedicated vCPUs and outbound access to registries.

  • Disposable environments

    Delete a development VM after merging its branch; your base environment remains unchanged.

Cost-effective for continuous use

Run VMs for about 25% less than major clouds charge. Live migration preserves in-memory caches when a host is reclaimed, including during long builds.

  • Dedicated cores

    Builds and language servers get exclusive vCPUs, not noisy neighbors.

  • Persistent volume

    Dependencies and worktrees remain available when a host is reclaimed and the VM is recovered.

  • Consistent operations

    The same VPC, HTTPS gateway, and SSH gateway as your production VMs.

> capabilities

A complete development environment

Develop, preview, and automate with the same VM configuration you deploy.

  • Configure once

    Define tools in cloud-init or a golden image, then create additional VMs as needed.

  • Editor compatibility

    Any SSH-capable IDE works without proprietary remote protocols.

  • HTTPS preview

    Share a staging URL at <vmId>.msrv.space without configuring nginx yourself.

  • Outbound Git and registries

    Clone repositories and download packages over NAT without exposing the VM to public ingress.

  • Private network and WireGuard gateway

    Dev VMs live in an isolated VPC that you can join from your own machine through the WireGuard gateway.

  • Live migration

    Long compiles and language servers keep running when capacity moves.

  • Agent-ready

    Hand an autonomous coding agent its own VM — see AI sandboxes for fleet patterns.

    AI sandboxes →

Connect over SSH and start coding.

Remote Linux VMs with your tooling, HTTPS previews, and pricing designed for continuous development.

Open consoleAsk a question