Help Articles – Page 4
There is no single best enterprise CMS; the right one depends on what you are running.
If you manage one large site, a traditional or headless platform may be enough. If you run many properties (multiple sites, stores, brands, or locations) on a lean team, look for cross-property reach, unified commerce and content, and AI agents that work inside your approval workflow.
Governed autonomy means an agent can act across your properties while a human approves changes, every action is logged, and any change can be rolled back. It gives a team speed without giving up control of live sites.
Core dna is built for agentic operations: running many properties from one platform by prompt, with approval, audit and rollback. It is not a consumer shopping-agent or a checkout protocol, though an operator can still sell through agentic commerce channels alongside it.
No. Agentic commerce sits on the customer's side and is about buying. Agentic operations sits on the operator's side and is about running the business. A company can use both for different purposes.
Agentic operations is when a business user prompts their platform in plain language to make operational changes, such as content, catalog and pricing updates, across multiple websites or stores at once. The agent works for the operator, not the shopper.
Agentic commerce is online buying carried out by an AI agent on a shopper's behalf. The agent searches, compares and completes the purchase, often inside an assistant such as ChatGPT or Gemini, using open standards like the Agentic Commerce Protocol (ACP) or the Universal Commerce Protocol (UCP).
You move onto Core dna without ripping out what already works, connecting existing systems through the APIs and shipping your first change early rather than waiting for a big-bang cutover. A dedicated success manager and onboarding are included, and standard plans run without a long lock-in contract.
In practice the estate moves property by property. The systems that already earn their keep stay where they are and talk to Core dna over the platform APIs, and you consolidate at the pace your team can absorb rather than freezing the roadmap for a year. If the goal is pulling several sites onto one platform, that is a replatforming conversation, and standard plans carry no fixed contract if you want to start small.
Agentic operation means you describe a change in plain language and the platform makes it across your properties, with human approval and a full audit trail. It runs on a free MCP server on every account, with 80+ tools and 400+ APIs. You bring your own AI model, so your model spend stays on your own provider contract.
Because you bring the model, there is no AI margin inside your subscription and no per-seat AI add-on — you connect Claude, ChatGPT, Gemini, Copilot or Cursor with your own key. Every action runs inside your roles, approvals and audit trail, so an agent can only do what the person driving it is already allowed to do, and anything it changes can be reviewed or rolled back. See how agentic workflows run across properties.
No. Your sales are yours. You pay your plan, and nothing is taken as a percentage of revenue.
This matters most as you grow. On platforms that take a revenue share, a good year raises your platform bill even though nothing about your usage changed — you are taxed on your own success. Here the plan is the plan. Commerce is native to the platform rather than a bolt-on, so there is no separate commerce licence either, and payment gateway fees stay between you and your processor. See what every plan includes.
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.