microsrv:~$
RUEN
Console

microsrv

use case · modern VPS

A VPS with essential services included.

A microsrv VM is a Linux server you access through the SSH gateway. It includes a hostname, a valid TLS certificate, an HTTPS gateway, and live migration when the underlying host is reclaimed, eliminating repeated nginx and certbot setup.

Open consoleSee pricing
ssh · publish app
$ ssh -A blog@msrv.spacemicrosrv: connection to blog establishedubuntu@blog:~$ cd /srv && python3 -m http.server 8080Serving HTTP on 0.0.0.0 port 8080 … # available at https://blog.msrv.space — TLS is enabledubuntu@blog:~$

Managed HTTPS

Each VM receives a <vmId>.msrv.space hostname with a valid certificate. The HTTPS gateway accepts requests and forwards them to your application, with no certbot setup or certificate-renewal cron job required.

  • Per-VM hostname

    Use a stable <vmId>.msrv.space hostname with automated TLS, or add your own domain later.

  • HTTP and TCP

    Expose HTTPS apps and TLS/SNI-capable TCP services such as PostgreSQL through the HTTPS gateway.

  • Follows the workload

    When a host is reclaimed, live migration keeps the hostname and open connections intact.

SSH without a public IP

Connect with ssh -A <vmId>@msrv.space. Port 22 is never exposed on the VM, and you do not need a public IP for day-to-day access.

  • Through the SSH gateway

    The only public entry points are the microsrv SSH gateway and HTTPS gateway.

  • Stable address

    The same SSH identity works after live migration, even when the physical host changes.

  • Private by default

    Keep staging dashboards and debug endpoints off the public internet until you publish through the HTTPS gateway.

Stable VMs on interruptible capacity

VMs run on interruptible capacity from major cloud providers and cost about 25% less than the same resources at list price. Before the provider shuts down a host, the orchestrator live-migrates memory so applications keep running.

  • Dedicated vCPUs

    Paid vCPUs belong exclusively to your VM and are not shared with other customers.

  • Live migration

    Running processes continue on a new host without restarting; volumes and network identity remain unchanged.

  • Automatic recovery

    When there is not enough time to migrate, the VM relaunches from a replicated copy.

> capabilities

Included capabilities

The standard new-VM setup is already complete.

  • Key-based SSH

    Access through the SSH gateway with agent forwarding. No public port 22 on the guest.

  • HTTPS gateway

    HTTPS and TLS/SNI TCP at <vmId>.msrv.space without a public IP on the VM.

  • Private network

    eBPF-isolated networks with stable internal IPs and spoofing protection. You can reach the network through the WireGuard gateway from your work laptop.

  • Outbound NAT

    Reach registries, Git, and APIs while keeping the VM off public ingress.

  • cloud-init

    Inject SSH keys and first-boot scripts when the VM is created.

  • Replicated volumes

    Storage remains available when a host is reclaimed and follows the workload across migrations.

Deploy your VPS and continue building.

Create a VM, connect over SSH, publish it at <vmId>.msrv.space, and let microsrv handle host changes in the background.

Open consoleAsk a question