Wire your schema, generate sites against test records, and read the code we produce without paying anything. You start paying when a site is live and serving a real customer.
Map your schema, generate sites against test records, and read the code before a single customer is involved.
No card required.
For vertical SaaS platforms publishing a site for every business on the book.
Billed monthly on the number of live sites. Sandbox sites are not counted.
For platforms with large tenant counts, procurement requirements, or their own infrastructure constraints.
Volume pricing, contractual uptime, and a named engineer for the integration.
All prices in USD. A site counts from the day it goes live and stops counting the period after you unpublish it.
The difference is whether a real customer is looking at it — not what the product can do.
A site that is live on a subdomain or a custom domain and serving traffic. Sites you generate in the sandbox to inspect the output are not billed, and a site you unpublish stops counting in the next billing period.
No. That is the point of the product. The business owner keeps using your platform exactly as they do today, and their website follows the record they are already maintaining. There is no page editor, no separate account, and nothing for them to keep up to date.
If you send a webhook when a record changes, the affected site is regenerated and redeployed within minutes. If you would rather not emit events, we poll on a schedule you choose instead.
One mapping. You expose the fields you already have behind a scoped API key and tell us which field means what. That work is done once and then applies to every business on your platform, including ones you onboard years later.
You do. Every site is a real Git repository containing readable application code, not a proprietary page format. You can inspect it, diff two publishes, and take it with you.
Yes. Every site is reachable on a subdomain immediately, and a business that already owns a domain can point it at their site with certificates handled for them.
Every site is server-rendered, so the first response contains the complete page rather than an empty shell. Structured data is emitted from the same record that renders the page, which means a crawler or a language model reads the same hours, services, and licence numbers your customer typed into your platform.