Platform & Architecture
For multi-property operators, the platforms that stand out model many sites, stores, brands, or locations as one estate and let you apply a change across all of them at once, instead of editing each site by hand.
When you compare options, weigh multi-site governance, a unified commerce and content surface, and whether AI agents can act across properties under your approval rules.
A request is a call to the Core dna engine that returns a dynamic page or structured content, such as a headless query or REST API call. Calls to static assets on the content delivery network do not count. Requests sit inside wide bands shown on your dashboard. There are no live meters, and if you are consistently growing past your band we start a planned upgrade conversation with you first.
The practical effect is that traffic spikes do not generate a bill. A campaign, a product launch or a seasonal peak moves you within your band rather than triggering a charge, and because the CDN absorbs the asset traffic that would dominate a metered model, the number that counts is much smaller than your pageviews. Operator includes capacity up to 4M requests a month, and higher tiers are sized to what you run. Sitting above your band consistently is a conversation about the right tier, not an invoice.
All platform applications, every update and new release, and the full cloud infrastructure: content delivery network, web application firewall, DDoS and bot protection, monitoring, backups and patching. Compliance attestations such as SOC 2 Type II and PCI DSS are available. There are no licence fees and no add-on charges as you scale.
What sits outside the plan is short and explicit: optional managed-services hours, reseller per-tenant arrangements, and request capacity beyond your band — which is a planned upgrade conversation, not an overage charge. There are no transaction fees on your sales, and adding users costs nothing, so the bill does not move as your team grows.
Usually yes. If you set the standards and each unit operates within them, that is the Network shape: you govern many independent units from one account, with per-unit variation where you allow it. If instead you host distinct businesses that own their own data and contract independently, talk to us, as that is priced differently.
The dividing line is governance, not legal structure — who approves a change and whose standards win. On Network, brand standards are enforced everywhere but editable locally, and one change pushes across every unit at once rather than being rekeyed per site. If that describes you, see how the tiers compare; if you are still weighing it up, which plan fits which shape is the faster read.
It is any organisation running many digital properties on a lean team: franchises, multi-brand retailers, multi-site manufacturers, membership networks and multi-location service businesses. If you make the same kinds of changes across many sites, stores or locations, you are who Core dna is built for.
The test is repetition, not headcount. If a price change, a campaign or a policy update has to be made by hand on ten sites, that is the work the platform removes — you make it once and it lands everywhere, inside your approval workflow. Most operators here run their whole estate with a team of two to ten. If you run a single site, a simpler platform will serve you better, and the tiers will not be the deciding factor.
Operator starts at $48,000 a year, and we publish it so you can tell quickly whether we are a fit. Network and Enterprise are priced to the shape and scale of what you run, so we size those with you rather than print a number that would not fit your situation.
Treat the published figure as a floor rather than a quote: it tells you the order of magnitude before anyone spends time on a call. It is not a cut-down tier either — what you get is the same across plans, so the higher tiers price governance, dedicated infrastructure and compliance rather than unlocking features. If you want a number against your own shape, work out which tier fits and then book a demo.
It comes down to your shape, not your size. Operator is for one business running several properties, like a main site, microsites and a B2B portal. Network is for an operator running many independent units under central governance, such as franchisees, brands or chapters. Enterprise is for dedicated infrastructure, compliance and scale.
If you are not sure which one you are, the useful question is who owns the units. If you set the standards and each unit works within them, that is the Network shape; if they are distinct businesses that contract independently, it is priced differently. Note that the tier does not change the feature list — every plan carries all applications, updates and infrastructure — what changes higher up is governance, dedicated infrastructure and compliance. Compare the three tiers, or book a demo and we will place you in a few minutes.
One subscription, priced to the shape of your business rather than the size of your team. You pick the plan that matches how you operate, and everything inside it is included: every application, the full cloud infrastructure, all updates and support. There are no per-seat fees, no licence fees and no live usage meters.
There are three tiers. Operator is for one business running several properties — a main site, microsites, a B2B portal — and starts at $48,000 a year, billed annually. Network is for an operator governing many independent units, such as franchisees, brands or chapters. Enterprise adds dedicated infrastructure, advanced SLAs and compliance attestations. Only the Operator price is published, because Network and Enterprise are sized to what you actually run. If you are not sure which shape fits, start here.
A new property starts from a governed template and inherits the core from day one: domain, brand identity, catalog scope, pricing, and integrations configured rather than rebuilt. It's a configuration step measured in hours to days, not a new platform contract or a months-long engineering project, so the cost of adding the tenth property looks nothing like building the second one from scratch.
You set shared elements such as templates, components, navigation, catalog, policies, once at the core, and every property inherits them. When a site needs to differ, you override that element in place: the local version takes over for that property only, and everything else keeps inheriting. Change the core later and the update flows down to everything still inheriting, while your local overrides stay put.
Yes. Each property can have its own domain, storefront identity, and pricing rules while drawing from one shared catalog. Products live once as a single source of truth; each storefront shows the slice it sells, at its own prices and promotions. So one brand can sit premium and another value, on the same SKU, without duplicating data or maintaining separate systems.
One platform, three relationships. Multi-site is the umbrella term: many websites or storefronts running on one shared core. Multi-store usually means one company running several branded storefronts from a single admin, often sharing a catalog and customer records. Multi-tenant means independent operators: franchisees, dealers, or separate businesses, each with isolated data and their own logins on shared infrastructure. Core dna supports all three on one instance: you decide what's shared at the core and what each property controls locally.
Yes. Core dna supports hybrid headless architecture, which means teams can deliver content and commerce through APIs while still using built-in editing and management tools.
This allows developers to build flexible front-end experiences while marketers retain control of content and operations.
Core dna acts as a centralized platform for managing content, campaigns, and digital experiences across dealer and franchise networks. It allows corporate teams to control brand and campaigns, while giving individual locations the flexibility to adapt messaging locally.
Core dna enables each location to manage its own content within a centralized structure. This allows local teams to tailor messaging, promotions, and information to their market, while maintaining consistent branding and user experience across the network.