A new site starts from a template that already carries your structure, components, and rules, so it goes live in hours, not a fresh build. You configure what is different and publish.
MANAGE YOUR PROPERTIES
Launch a site in hours. Change every site safely.
86
marketplaces
one instance, zero new developers
Save a Life I Clark Rubber I YMCA I Frontier Touring
Add a site in hours, not sprints.
Clone a governed template, apply your rules, and launch. The eleventh site goes live the same way the second one did, so adding a property is a configuration step, not a project.
- Start from a template that carries your structure
- Reuse shared components from day one
- Go live without a new build or a new vendor
Build it in dev. Publish it to production.
Every change starts in a dev environment, where your team builds and tests without touching a live site. Dev and production run on the same instance and the same components, so what you test is what ships. There is no separate staging that drifts out of sync. When it is right, it is approved and published, and every version is kept, so going back is one click.
- A dev environment to build and test, separate from your live sites
- Approval before anything reaches production
- Every version kept, so rolling back is picking a version and publishing it
Permissions & access
Who can do what, on which site.
View, edit, or publish, by person
Set what each person can do on each site: view only, edit, or publish. Access is enforced by the platform, not left to good intentions.
Write now, publish on approval
Contributors can draft and edit without the power to push anything live. An approver reviews and publishes. The approval workflow is built in, not bolted on.
Scoped to the sites and environments they own
Give a person one site or several, and separate who can work in dev from who can publish to production. Teams stay in their lane across the whole portfolio.
Every change versioned, with who and when
Every edit is kept as a version, tagged with the person and the time. See what changed, who changed it, and roll back to any earlier version.
Access modelled to how your org works
Permissions map to your structure: by site, by environment, by role, down to which pages a person can touch. Internal teams, regional managers, and outside contributors each see only what they should.
One login across every site
No separate account per property. A person signs in once and works across every site and environment they are entitled to, governed by one set of permissions.
One change, every site it belongs to.
Update a global component once and it carries across every site that uses it. You see exactly which sites a change will touch before it ships, and any version is one click back, so a change across the portfolio never means a risk across the portfolio. Need one site to differ? Copy the global component down to a local one and change only that site. No copy-paste, no drift.
- Edit a global component once, every site updates
- Copy global down to local to override one site
- No copy-paste across properties, no drift
Or skip the clicks. Describe the change.
Everything on this page works through the admin. It also works through a prompt.
Agentic = describe the change in plain language; the platform ships it across every property, with approval and audit built in.
FAQ
Common questions about launching and changing sites
There is a real dev environment, separate from your live sites. Dev and production run on the same instance and the same components, so what you test is what ships. There is no separate staging that drifts out of sync.
Every change is versioned. To roll back, you pick an earlier version from the list and publish it. One step, not a restore from backup.
Yes. Permissions are set per person, per site, and per environment. You can let someone draft while only an approver publishes, and separate who edits in dev from who publishes to production.
You see exactly which sites a change touches before it ships, and any version is one step back. A change across the portfolio never has to mean a risk across the portfolio.
Yes. Moving from another platform is a common starting point. See how replatforming onto Core dna works.
FROM THE BLOG
Latest on platform & architecture
GET STARTED
Book a 20 min demo