Live demonstrations  ·  Operations

Order a server, cut it up, put something on it, move it.

A hosting control plane rather than a status page. Order capacity from a provider, divide it into isolated slices, deploy a stack into one, and move a running site to another machine without taking it down.

ColoCommerce/Web Services A drawing of the real screen
Hosting
FleetSitesDomainsEmail
Operations
Backups okMigrationsFirewall
3
Nodes
27
Slices
1.4 TB
Backed up
6 days
Since last restore test

Fleet

Live capacity, and what is packed onto it.
node-den-1
Denver · OVH · 8 vCPU · 32GB
62%
71%
44%
6 slices
node-fra-2
Frankfurt · Hetzner · 16 vCPU · 64GB
38%
51%
29%
9 slices
node-ash-1
Ashburn · Proxmox · 24 vCPU · 96GB
81%
66%
73%
12 slices

On node-den-1

One site is being moved to another machine without going offline.
ashcroft-dental.com
WordPress
running
warehouse7.co
LAMP
running
mail.northgate.io
Mail server
running
staging.paloma.dev
WordPress
moving to node-fra-2
Drawn, not run: the real screen needs your data and a login. The shape, the styling and the figures are all the real thing's.

Slices, not shared hosting

Each site gets its own container with its own CPU, memory and disk limits. A neighbour having a bad day is a neighbour having a bad day.

One-click stacks

WordPress, LAMP, mail, a game panel, a wiki — deployed and running, with the database and credentials already made.

Backups that are restored

Backed up to object storage and test-restored on a schedule, because a backup nobody has restored is a hope.

Next: Marketing

See what a send costs before you send it.

Show me All of them