Your own machine

Every Lathe instance is a dedicated virtual machine for one customer. It is not dedicated hardware, and it is not a namespace or a slice of a shared cluster.

What "machine" means

Your instance has its own virtual machine boundary: its own guest kernel, root filesystem and local disk. Lathe manages the operating system and root access for you. No other Lathe customer runs inside that VM.

A virtual machine is still a machine. "Your own machine" describes the isolation boundary and who uses it. We never call it dedicated hardware because the physical host is not yours.

What the boundary buys you

Your plan's resources: The RAM and local NVMe assigned to the VM are for your instance. Another Lathe customer's database, app or queue cannot consume them from inside your machine.
No shared-cluster neighbor: Your workload does not share a Kubernetes namespace, process tree or guest operating system with another Lathe customer. There is no cross-customer noisy neighbor inside the VM.
A smaller blast radius: Your apps, databases and sign-in share one machine with each other, but not with another customer. A workload that exhausts resources can affect the services on your box; it does not run inside theirs.

What it does not mean

The physical server underneath the VM can be shared by the infrastructure provider. Lathe does not sell dedicated hardware. It sells one managed virtual machine per customer, with backups, TLS, monitoring, updates, the portal, REST API and MCP included.

For available sizes and what each plan includes, see pricing. For backup, resizing and account rules, see limits and policies.