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, and an HTTPS gateway — no repeated proxy and certbot setup.

Open console
ssh · publish app
$ ssh 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.

  • Stable address

    Your <vmId>.msrv.space hostname and TLS certificate last as long as the VM does.

SSH without a public IP

Connect with ssh <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

    One SSH identity for the VM's lifetime — it survives reboots, updates, and recovery.

  • Private by default

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

A reliable VM foundation

Dedicated vCPUs, NVMe storage, and replicated volumes give you a VM that behaves the same every day.

  • Dedicated vCPUs

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

  • Replicated storage

    Data is mirrored across storage nodes and survives hardware failures and node maintenance.

  • Automatic recovery

    If a VM stops, the platform recreates it from its volume with the same addresses and data.

> capabilities

Included capabilities

The standard new-VM setup is already complete.

  • Key-based SSH

    Access through the SSH gateway with key auth. 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

    Your data survives node maintenance and hardware failures and stays with the VM.

Deploy your VPS and continue building.

Create a VM, connect over SSH, and publish your service at <vmId>.msrv.space.

Open consoleAsk a question