Every change, approval, and agent action — timestamped, attributed, queryable by user, property, date, or change type. Exportable to your SIEM. Retained per your policy.
AUTOMATE YOUR OPERATIONS
Ship every change fast. Keep every change governed.
6
controls
built into every change
Save a Life I Clark Rubber I YMCA I Frontier Touring
Speed without governance is just faster chaos
Built so agents are safe to ship
Governance is what makes agentic operations possible. Core dna treats every agent the same way it treats every team member - scoped permissions, approval routing, audit trail, rollback. By default. The boundaries are the same, the controls are the same, the trail is the same.
- Without scoped permissions, an agent could touch any property
- Without approval routing, an agent could ship pricing without legal review
- Without an audit trail, you couldn't prove what the agent did
- Without rollback, you couldn't undo it
- With Core dna, every agent runs under the same controls as every human
Scope permissions to the work, not the person
Old governance asks who someone is. Modern governance asks what change they're proposing, on which property, against which content type. The permission lives with the work, not the title. A regional marketing manager publishes their region's content and proposes pricing for review - never touches corporate templates or another region.
- Per-property scopes, a permission can apply to one site, one region, or the whole network
- Per-content-type scopes, separate permissions for pages, products, prices, integrations, agents
- Per-action scopes, read, propose, approve, ship, rollback as distinct verbs
- Role templates for common shapes (marketing manager, regional admin, e-commerce lead)
- API-level enforcement, scopes apply to UI, headless API, and agent calls the same way
Route approvals to the right person, not everyone
Approval routing matches the risk of the change. Content edits route to a content lead. Pricing changes route to commerce and finance. Legal text routes to legal. Routes are configured once per change type. Every change of that type follows the route automatically.
- Per-change-type routing rules, configured once
- Multi-approver routes (any of, all of, in sequence)
- Conditional routing, different routes based on properties touched, price thresholds, or content fields
- SLA on approvals with escalation if a route stalls
- Approval-by-Slack, approval-by-email, or in-platform approval, the route handles all three
governance in practice
The same governance model. Every change type. Every property.
CONTENT
PAGES · CAMPAIGNS · MULTI-PROPERTY
Content changes, scoped per region and per role.
Page edits, campaign launches, hero swaps, translation rollouts - each carries its own approval route, audit trail, and rollback. A regional manager proposes a local campaign without touching the corporate site. A corporate marketer rolls a campaign across every property without approving each one.
Scoped to region Per-content-type routing Diff preview Rollback armed
COMMERCE
PRICING · CATALOG · CHECKOUT
Pricing, catalog, and checkout changes that need two sets of eyes.
Price changes route to commerce and finance. Catalog publishes route to merchandising. Checkout config routes to engineering. Each change shows the diff before approval and rolls back atomically.
Multi-approver routing Per-warehouse diff Threshold rules Atomic rollback
INTEGRATIONS
APIS · WEBHOOKS · DATA SYNC
API connections, webhooks, and data flows that auditors actually inspect.
ERP syncs, webhook endpoints, CRM mappings — governed changes, not configuration edits. Every change is approved, logged, and reversible. The audit shows what flowed through after.
Endpoint approval Mapping diffs Test before live Connection rollback
AGENTS
PERMISSIONS · POLICIES · CEILINGS
Govern the agent before the agent acts.
Agents act under scoped permissions, configured policies, and explicit ceilings. A translation agent is limited to specific languages, properties, and word counts per run. Every agent action runs through the same approval and audit pipeline as a human change.
Scoped permissions Policy per agent Cost ceilings Same audit trail
Procurement-ready
The compliance and audit detail your e-commerce lead and your CISO will ask for.
SOC 2 controls map directly to platform features: access control, change management, audit, business continuity. GDPR data subject rights map to the user record, consent log, and deletion workflow. Your auditor’s checklist becomes a platform screenshot.
The proposer cannot be the approver on critical change types. Separation is enforced at the platform layer, not by team convention.
Per-content-type retention. EU data in EU regions. Deletion workflows execute through the same audit-and-approval pipeline as every other change.
SAML SSO. MFA enforceable by role. IP allow-listing for admin access. Session timeouts configurable by environment. Identity controls map to your enterprise stack.
One-click rollback for any change. Point-in-time restore for catastrophic recovery. DR tested on the schedule your auditor expects — same surface as routine rollback.
built for the shape of your org
Governing the shape your
org actually has.
Whether you run 60 franchise storefronts, every branch in a regional network, a B2B dealer catalog, or a membership across chapters - the governance model fits the shape, not the other way around. Franchises · Multi-location · B2B distribution · Membership
60
Franchises, one governance model · Clark Rubber
Every
Branch scoped to its team · YMCA
12,847
SKUs with two-eyes pricing · RANDYS Worldwide
Every
Member action, audit-trailed · Save a Life
CUSTOMER STORIES
What our customers say
We didn't have to start from scratch every time. Core dna gave us the architecture to grow fast and stay in control.
We needed to stop depending on developers every time marketing wanted to update a page or launch a campaign. Core dna gave us one platform our team actually owns — across every property, every location, every service category.
60 storefronts on one platform. Marketing and eCom teams now manage everything in one place — no dev needed.
How approval & governance rolls out in your org
Most teams ship their first governed flow within two weeks. The team that builds the platform implements alongside yours.
WEEK 1
Discovery & policy mapping
Map your highest-risk change types, your existing permission groups, and the approval routes you actually need. Pick the first governance flow to ship.
WEEK 2-3
First governance flow live
Scoped permissions, approval routes, and audit log configured for your first change type. Your team ships the first audited change with an implementation engineer alongside.
WEEK 4-6
Expand the policy library
Three to five more flows added. Routes refined. SSO and IP scoping live. Your team starts authoring policies themselves.
WEEK 7+
Governed change library
Your team owns the governance library. Procurement signs off. Auditor mapping is documented. The platform extends as you need new change types.
FROM THE BLOG
Latest on platform & architecture
SEE IT ON YOUR CONTENT
Book a 20-minute walkthrough.
We’ll walk through a real change on a real multi-property setup — propose, preview, approve, ship, audit, roll back.