GenWave
genwave.site
Live edge renderer

WordPress keeps the content.
Visitors get a React site.

This domain is the renderer behind GenWave Front Sites. Customer sites are served from here — each on its own hostname, rebuilt as a modern React frontend while their WordPress carries on being the CMS it always was.

See what it doesyou are looking at the platform, not a customer site
0
plugins removed

WordPress keeps running exactly as it is

1
write to publish

no rebuild, no deploy step

sites per Worker

one renderer, isolated per host

How a site gets here

  1. 01

    Read

    The live site is scanned as a visitor sees it — structure, copy, imagery, menus.

  2. 02

    Compose

    Pages are rebuilt as typed React components against a design system, not scraped markup.

  3. 03

    Review

    The result is compared against the original before anyone sees it.

  4. 04

    Serve

    Published to the edge. WordPress stays the CMS; an edit appears in seconds.

Why the address you are on looks like this

Every published Front Site answers on its own hostname under this domain until its owner connects their own. One renderer serves them all, and a site is resolved per request from the hostname it arrived on — so two customers can never see each other's content, and publishing a site is a single write rather than a deployment.