Record to website
Published, verified, and never staleOne mapping, then it runs itself
You expose the fields you already have behind a scoped API key and tell us what each one means. That work happens once and then covers every business on your platform, including the ones you sign years from now.
One integration for all tenants
You map your schema once. Every business on your platform is then addressable, whether you have fifty of them or fifty thousand, with no per-tenant setup work.
Scoped, revocable access
Reads happen through API keys you issue and can revoke. We take the fields you expose and nothing else, and the key is what defines that boundary.
Your field names, kept
The mapping layer adapts to your data model instead of asking you to reshape it. Custom fields, optional sections, and partial records are all first-class.
Push or poll
Send us a webhook when a record changes and the site follows within minutes, or let us poll on a schedule if emitting events is more change than you want to make.
Every site is a repository
Generated code lives in a real Git repository per tenant. You can read it, audit it, diff two publishes, and take it with you.
Sandbox before production
Point the mapping at test records and inspect the generated sites before a single customer-facing domain is involved.
Generate, verify, and publish a site
for every business you hold.
A green production build is the definition of done. A site that does not build is never published.
What happens between a record and a live site
Read the record
We call your platform with a scoped API key and read the fields you mapped — hours, services, service areas, staff, licences, availability, and whatever custom fields your vertical needs. Nothing is duplicated into a second database for someone to keep in sync.
Generate the site
An agent turns that record into a real codebase: routes, components, copy, and structured data appropriate to the business type. Each tenant gets its own Git repository, so every site has a full, inspectable history.
Build and verify
The site is installed and compiled like any other application. A green production build is the definition of done — a site that does not build is never published, so a bad generation can not reach a customer.
Publish to the edge
The build is deployed to Cloudflare's network as an isolated worker and served from its own subdomain or the business's own domain, server-rendered so the first response is complete HTML.
Republish on change
When the underlying record moves, the affected site is regenerated and redeployed. The business owner is never asked to confirm, edit, or approve anything — the site simply keeps agreeing with the system they already run on.
Roll back on demand
Because every publish is a commit and a versioned deployment, any site can be pointed back at an earlier build immediately, without reconstructing the record that produced it.
Sites that search engines and assistants can actually read
Server-rendered at the edge, with structured data emitted from the same record that renders the page
Subdomains out of the box
Every tenant is live immediately on its own subdomain, so a business is reachable before anyone thinks about DNS.
Custom domains
Businesses that already own a domain can point it at their site, with certificates handled for them.
Server-rendered HTML
The first response carries the complete page. Crawlers and language models do not have to execute JavaScript to read a customer's hours.
Structured data included
LocalBusiness, opening hours, and service markup are emitted from the same record that renders the page, so they can never disagree with it.
Fast from anywhere
Sites run at the edge rather than from one origin, which is what local search traffic on phones actually needs.
Isolated per tenant
One worker per site. A heavy hour on one business's site is invisible to every other business you publish.
Why platforms hand this to us instead of building it.
Websites are the feature customers ask for constantly and the one platforms most regret shipping themselves.
Stop shipping a website product you did not want to build
Websites are the feature vertical SaaS platforms get asked for constantly and regret building. A page editor becomes a support surface, a template library becomes a design backlog, and stale content becomes a churn reason. This removes the whole category of work.
Turn data you already hold into a line item
The record your customers maintain to operate is already complete enough to be their web presence. Publishing it is additional revenue per tenant that costs you no additional content operations.
Make correctness the default state
The common failure of small-business websites is not ugliness, it is being wrong — old hours, a disconnected number, a service no longer offered. When the site reads from the operational record, being current is the resting state rather than a task.
Get found by search engines and language models
Every site is server-rendered with structured data, so the facts about a business are legible to crawlers and to the assistants people increasingly ask before they call anyone.
Keep your customers inside your platform
There is no second tool, no separate login, and no other vendor in the relationship. The website becomes another thing your platform does, under your brand.