Every site gets its own walls.
Most managed hosts run your sites as neighbours — shared database server, shared filesystem, shared fate. WP Cloud OS gives each site its own namespace, its own database with its own credentials, and a default-deny network policy around it. Not a setting. The only way it builds a site.
Three things we do differently
Isolation you can verify
One Kubernetes namespace per environment, one MySQL database and user per site, granted on that database only. A compromised plugin reaches its own site and stops there.
Provisioning that shows its work
Creating a site is eight steps, and you watch each one. If step six fails, steps one to five are undone in reverse — and you see that happen rather than finding half a site later.
You choose where it runs
Placement takes a policy — cheapest, fastest, balanced, or a substrate you name — with jurisdiction filters for data that must not leave a country.
From nothing to a running site
No ticket, no callback, no "your account is being reviewed".
-
Create an account
Name, email, organisation. You are signed in when you finish.
-
Create a site
Give it a name and a plan. Optionally a domain.
-
Watch it build
Capacity reserved, database created, workload started, WordPress installed, hostname attached. Each step with its own outcome and how long it took.
-
Log in to WordPress
The administrator account is yours — the address that created the site.
An API, not an afterthought
The console is one client of the same API you get. Scoped keys, idempotency keys on every write, and errors that are documents rather than HTML.
Every write is idempotent
Send an Idempotency-Key and a retry after a timeout returns the
original operation instead of creating a second site. A network blip should
not cost you money.
Errors say what to do
RFC 9457 problem documents carrying whether the failure is retryable and whether it can be relocated — so a client can decide, rather than guessing from a status code.
Start with one site.
Nothing is charged today — billing is not connected yet, and we would rather say so than surprise you.