Everything a rebuild needs — nothing you have to babysit.

Design directions

Three styles, three approaches, nine designs.

Classic — established, editorial, timeless rather than old: serif headlines, ruled dividers, deep grounded colour. Contemporary — current and friendly: soft shapes, one confident hue, humanist type. Modern — bold and of the moment: bento grids, vivid accents, oversized type.

Refresh keeps your layout exactly and renews the look. Refine restructures where it clearly improves flow. Re-imagine keeps every piece of content and reinvents the rest from first principles. Your logo directs the colour; your content directs the structure.

• Tiles appear progressively, generated by our most capable AI model
• Two more takes of any favourite, up to two per style × approach
• Your own wishes and a choice of text treatment
• A share link where colleagues vote per design — extra takes too, from one fixed budget

The split viewer

Today, next to ReWynded.

The original on the left, the redesign on the right, a divider you drag, scrolling kept in sync, fullscreen per pane. On a phone the panes stack. From the first design to the last page of the build, this is where you look at your site.

Later, in the workbench, the left pane mirrors your old site so a click on an old link opens the matching new page — and a click in the new page selects the component you want to change.

Component library

A living style guide, approved by you.

The moment your package is pinned, ReWynder draws every common component of your new site in the chosen design — navigation, headers, cards, forms, footers — as one page you review, refine and approve. Every page is then built from exactly these components, and a change to the library becomes a rule for the whole site.

It also gates the price: what you sign off is what the rebuild is priced against.

Reading your site

Connect it, upload it, or let a browser read it.

ReWynder recognises WordPress, WordPress.com, Joomla, Drupal, TYPO3, Magento, PrestaShop, OpenCart, Concrete CMS, Wix, Squarespace, Shopify and Blogger from your landing page and offers the most direct path: a one-click connection, a self-removing connector, a backup upload, or your own exports. The crawler is always the last link, so no site can dead-end.

The crawl itself: sitemap first, then every link; one exemplar per page template; images deduplicated by content; a members area behind a login on request. Five situations pause and ask instead of truncating — size, time, sibling subdomains, hard-to-read pages, more pages than included — and every pause resumes from a checkpoint.

The connectors in detail

The build

Page by page, each one checked twice.

A site blueprint — routes, components per page, collections, build order, redirects, accessibility and SEO — leads the build. Pages are generated one at a time from the approved library, reviewed by fixed security rules and by an AI reviewer, stored and committed. A finished page is editable immediately.

Last comes the site’s application: the shell, every approved page ported to its route, the application layer with collections and forms, and the site’s admin panel themed with your tokens. When a real infrastructure cost is at stake, the build pauses to ask first.

Site chat

Say it once; the site changes everywhere.

In Expert mode you describe a change in plain words. A style applied across nine pages becomes one change per page; a new page is assembled from your library into the blueprint and built like any other; on PRO, new functionality — a form that emails you, an integration — regenerates the application layer. Requests outside your package get a kind hint and the exact upgrade amount, never a dead end.

Change ledger

Every change is a commit. Any one can go.

Manual edits, AI reworks, library changes and chat results each become one commit in your site’s repository and one row in the Changes list. Reverting takes out that change and only that change — later work is untouched by construction. If a later change overlaps, ReWynder names it and offers to take those out too, or keep everything as is.

Your site’s own CMS

Two places to edit, clearly divided.

The ReWynder dashboard edits every static text: page texts, site-wide details, interface labels. The site’s /admin — platform-provided, themed with your component library, running on the site’s own database — manages repeatable content (collections), the form inbox and settings such as the password and search-engine indexing.

• Plain forms, no client-side JavaScript required
• One-click signed sign-in from the platform, or your own password
• Admin pages never cached, never indexed, never framed

Hosting

A world map, and a cloud project per site.

Pick the datacenter closest to your visitors. Google Cloud today: Eemshaven, St. Ghislain, London, Frankfurt, Hamina, Iowa, South Carolina, Oregon, Singapore, Tokyo, Sydney and São Paulo. AWS, Azure and Scaleway are on the map, greyed, coming soon.

Each published site runs in a cloud project created for it: its own compute, its own database, a managed certificate on your domain. The platform acts through a single deployer identity it can only impersonate — no keys exist anywhere. Your Google account can look inside from the first day; with PRO you can request the source, and access to or handover of the project.

Maintenance

Monitored, audited, kept current.

Every rebuilt site carries a versioned health checker that reports every 30 minutes. Every build registers its full dependency manifest, audited daily against public vulnerability data. Security updates are meant to reach your dev site first and production only after your approval — the automated approval flow is on the roadmap; the audits run from day one.

Maintenance is a one-year contract per site from go-live, paid monthly or yearly: one fixed, all-inclusive fee per tier, itemised. Any separate cloud services your site needs are added at cost, agreed before anything deploys. It renews for a year unless you cancel a month before the end.