Koddrio Cloud — a K2 Studio case study

Client: Koddrio Ltd, United Kingdom
Years: 2026 — ongoing
Scope: Product management, development (backend), architecture, infrastructure, operations
Stack: WordPress and PHP, containers, AMD EPYC and NVMe, Google Cloud network and CDN, Redis and MySQL

The problem

An agency runs dozens of client sites, and ordinary managed hosting sells it a plan: so many WordPress installs, so many gigabytes. A large WooCommerce store and a brochure site get the same ration — so one is starved and the other is paid for in vain.

The second problem is money. One invoice arrives for the whole agency, and working out what an individual client costs can only be done by hand. Yet hosting has to be re-billed to clients every month.

What we did

A container per site: PHP workers, memory, database, cache and disk are allocated to the site, not to a plan.
An agency dashboard: search by client, tag and domain, bulk operations, a full activity log, roles for the team and access for clients.
Developer tooling: Git deployments, SSH and WP-CLI, and commands run across the whole fleet at once via the REST API and the Kodo utility.
Blueprints and images: a new site from your own template, cloning, syncing, and promoting staging to production.
Cost attribution by client, site and resource, right-sizing recommendations, forecast-based billing alerts and per-client quotas.
White-label: the dashboard on your own domain, with the agency’s logo and colours.
Operations: core and plugin updates, uptime monitoring, malware scanning, daily backups.

Result

Up to 9x the throughput Compared with cloud VMs at a similar price. Our own AMD EPYC servers with redundant NVMe storage — in Washington D.C. for the US and Frankfurt for Europe; networking, load balancing and CDN on Google Cloud’s premium network with more than two hundred edge locations. The availability target is at least 99.995% a month.

Why a container per site

Managed hosting usually sells a plan, and the resources underneath it are shared: the neighbour on your server is somebody else’s problem right up until it becomes yours.

Here the resources belong to the site. The minimum is two PHP workers of 128 MB each and 5 GB of redundant NVMe; beyond that the agency decides who gets what. A store can be given three times what a brochure site gets, without overpaying for the second. A site on SQLite runs without a database server at all — and is not charged for one.

The isolation is not only about performance. Every site lives in its own container: even under a full compromise, neighbouring sites and their services are invisible from inside that environment.

A bill that breaks down by client

The platform costs everything out by client, site and resource, shows unused capacity and suggests what to trim. Alerts arrive on the forecast rather than on the invoice, and a quota can be set per client.

One agency used it to strip eighteen PHP workers and over three hundred gigabytes of unused storage from a dozen client sites — and still had headroom to spare.

The agency bills its own clients: Koddrio never charges an agency’s clients directly, and never contacts them without permission.