01
We map what you actually need.
A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.
We build & run this
5eves — Managed WordPress Hosting on Kubernetes
Our sister brand. A managed hosting platform that provisions isolated WordPress sites on a Kubernetes cluster, with an AI-assisted theme builder on top. We designed it, built it and run it.
View it live ↗
Australian-based team
Senior developers only
Fixed quote before we start
Kubernetes
Multi-tenant cluster
API
Automated site provisioning
AES
Encrypted credential storage
5eves is CloudyWP’s sister brand, not a client. It is listed here because running it is the clearest evidence of what we can build — not to imply an external engagement.
Kubernetes
WordPress
Redis
MySQL
Traefik
Australian team
Based here, working your hours — not a timezone away
144+ projects delivered
Over 10+ years building and maintaining sites for Australian businesses
One developer, start to finish
The same person every time — no re-explaining your site
Straight answers, on your terms
We only take work we can finish. Ask us anything first — no obligation
The challenge
- Provisioning a real, isolated WordPress site on demand is a very different problem from deploying one site — it has to happen without a human touching the cluster.
- Multi-tenancy means one customer’s site must not be able to reach another’s, while still sharing infrastructure economically.
- Every provisioned site generates credentials that have to be stored and retrieved without ever sitting in plaintext.
- Selling capacity you do not have is how hosting platforms fail; capacity has to be enforced in code.
- Running WordPress behind a proxy introduces HTTPS detection problems that surface as admin redirect loops rather than as clear errors.
What we did
- Built on Kubernetes, with the whole platform defined as versioned manifests rather than hand-configured servers.
- An API service provisions customer sites programmatically against the cluster, so a new site is an API call rather than a support ticket.
- Studio, the AI-assisted theme builder, runs as its own service with persistent storage, so design work survives restarts.
- Shared Redis and MySQL services back the tenant sites, keeping per-site cost down without giving tenants access to each other.
- Every stored site credential — SSH, SFTP and the rest — is encrypted at rest behind a platform key.
- A capacity gate governs how many sites can be sold against real cluster capacity, enforced in configuration rather than tracked by hand.
- Traefik handles ingress, with HTTPS forced explicitly at the application layer because the proxy resets the header WordPress would otherwise rely on.
The outcome
- A working multi-tenant hosting platform running isolated WordPress sites on Kubernetes.
- Site provisioning is automated end to end through the API.
- AI-assisted theme building available to customers as part of the product.
- Credentials encrypted at rest; capacity enforced rather than estimated.
Got something similar?
Tell us what is happening and we will come back with a fixed quote and a timeline, usually within one business day.
Get a fixed quote
