Unisrv logoUnisrv.io
Home

Philosophy

Why Unisrv exists and is built the way it is.

Infrastructure should be simple to use without requiring someone else to own all of it.

A cheap VPS, a server in your closet, a rack in a datacenter and a VM in AWS are all perfectly good computers. Yet how you deploy, connect and operate workloads usually depends on where that machine happens to live.

We don't think it should.

Unisrv gives all those machines the same runtime, network and control plane. You describe what should run and Unisrv handles placement, rollouts, TLS, routing and recovery.

Unisrv is not a wrapper around other providers. They can supply the compute, but Unisrv provides the platform running across it.

You can start with one small server, add another provider later, bring in specialized hardware, or use Unisrv capacity when you need to burst.

On the left, your machines: a Raspberry Pi, a VPS, a rack or a cloud VM, each running the open source node agent. You own them. On the right, Unisrv runs the control plane, the edge that handles TLS and routing, and optional managed capacity. The two sides connect over QUIC with a hybrid X25519 and ML-KEM key exchange.

Three parts

Node agent

Runs on each of your machines and starts the instances. It uses the strongest isolation the hardware allows: a Firecracker microVM on bare metal with KVM, and a regular container in an already virtualized environment. It's open source, so the part that touches your hardware is code you can read.

Control plane

Turns the individual machines into one unified platform. You declare the desired state and the control plane keeps reality matching it: where instances run, how deployments roll out, what happens when one fails. It's global and reachable from anywhere: open the dashboard or the CLI and you control every machine, with no VPN to set up.

Network

Connects everything into one private network. Nodes talk over an encrypted QUIC connection that they open themselves. They need no open inbound ports, so they work behind NAT and most firewalls. The edge terminates TLS and routes HTTP from the internet to your services.

On this page