What Webplo is, and how it works

Webplo is the operating business of Krodox Holdings. It builds, hosts and maintains websites for local businesses — the restaurant, the clinic, the studio, the trades company. This is what it does and, more usefully, how it actually works underneath.

The problem it addresses

A small business owner who needs a website has three options, and all of them are bad.

They can hire an agency, which is expensive, slow, and leaves them dependent on that agency for every future change — including access to their own domain. They can use a site builder, which means becoming an amateur designer on evenings and weekends. Or they can do nothing, which is what most of them do.

The premise of Webplo is that in 2026 a sole proprietor should be able to get a real website, on their own domain, without a technical middleman taking a cut of the budget and holding the keys.

What the owner experiences

They answer questions about their business. A site appears, on real infrastructure, with their content in it. They can edit any of it themselves afterwards, and the domain is theirs.

The part that usually surprises people is the timing: launching a live site takes roughly 60 seconds. Not a preview or a staging URL — a provisioned server, a deployed site, a certificate, a working address.

What the AI does, and what it does not

This distinction matters more than any other, and most of the market blurs it.

The AI writes content. Given a business, its category, its location and what it offers, it produces the copy — headings, service descriptions, the about section, the things a business owner finds hardest and most tedious to write about themselves.

The AI does not build the site. It does not generate templates, write code, or provision infrastructure. Those are deterministic systems doing deterministic work: servers created through a provisioning API, sites deployed from version-controlled template packages, DNS and CDN configured by services whose only job is that.

The reason for the split is reliability. Content generation can be imperfect and still useful — an owner reads it, edits it, and moves on. Infrastructure cannot. A server that is "mostly" provisioned is an outage. So the generative part is confined to the layer where variation is acceptable, and everything load-bearing is ordinary, testable software.

The architecture

Underneath, Webplo is roughly a dozen services built in-house, each responsible for one concern: domains, security, licensing, analytics, CDN configuration, repositories, servers and VPS management.

They are separated because their failure modes are different. A registrar being slow should not delay analytics. A CDN configuration error should not stop a site being created. Splitting them means a problem in one area degrades that area instead of the platform.

That structure carries a real cost in coordination, which we would not recommend to a project that does not need it. It earns its keep here because the work is genuinely asynchronous and bursty: the platform processes around 5,000 jobs a day at approximately 0% job error rate, and scales to about 300 sites being created at once.

Why it is built this way

The people building Webplo spent years building complex, scalable systems for large American enterprises. The engineering discipline is the same one those systems required — queues, idempotency, retries, circuit breakers, deployments you can roll back.

The difference is who it is pointed at. That discipline is usually reserved for companies who can afford a platform team. Here it is aimed at a business with one location and no technical staff, who mostly needs their opening hours to be correct on Google and a phone number people can find.

That is the whole thesis: enterprise-grade infrastructure, in service of a business that would never have been able to buy it.

It applies outside the customer list too. Since October 2025 we have sponsored a youth football academy in Miami through Webplo, and built their website the same way we build everyone else's.