Composition
Compose once, without merging your sources
Enterspeed Core is an AI data orchestration platform that transforms source data into the shapes consumers need, at write time, and keeps them current as sources change. Schemas are declared in code with types.
The job is composition, not migration. Your product master, your PIM, your commerce engine and your content system stay independent, and domains are never merged into each other's records. When a source record changes, only the representations built from it are updated, so a correction reaches every surface without a source-specific export job.
Kentaur, a workwear manufacturer, brought five systems into unified views: Aspect4 ERP, Perfion PIM and Dynamics CRM feeding Relewise search, Commercelayer commerce and a headless Umbraco 13 frontend. Five systems in, four destinations out, custom code removed.
0.6s
TTFB, against a 0.8s target
~100
Legacy sites consolidated
Danish Crown, one year after launch, with FCP at 1.5s against 1.8s and LCP at 1.8s against 2.5s. No before figures are published, so this proves the site is in the green rather than that Core made it faster.
How it works
Ingest, store, compose, deliver
Transformations happen at write time rather than at read time, which is what makes one call enough.
Sync Connectors ingest
They read the systems you already run, detect what changed, and push only the changed records into Core. They ship as pre-built connectors or as an API, so there is no integration project and no migration.
The truth layer stores
Core holds the latest source version of product, profile, content, asset, marketing and brand-context data. Domains stay independent.
Compositions transform
Compositions are declared in code with types. Core detects a change, runs the transformation, and projects one representation into each channel dialect.
The delivery API serves
One call returns full attributes, the entitled price, per-variant stock and delivery promise, resolved per market and per customer.
When a source is down, the response is stale rather than absent, so the product page does not wait for five systems and the price does not arrive after the button.
Inside Core
The named parts
Five Enterspeed capabilities do the work, and each one changes what you can do.
Sync Connectors
Read the systems you already run, detect what changed, and push only the changed records into Core.
Campaign & Entitlement Pricing
Holds a price with its tier, its entitlement rule and its validity window as data, and resolves per caller at read time. An unentitled price is absent from the response, not hidden in it.
Preview and embargo
Returns unpublished or future-dated content to an authorised caller on the same URL the public will use. The public request returns 404 until the publish moment.
Versioned contracts
Pins each consumer to the contract version it was built for, so a source shape can change without a simultaneous cutover across every consumer.
Self-describing API
Derives and serves the API surface for each consumer from the representations published to it, as a schema or a standard specification, with a discovery surface for AI callers.
Scope
Your systems keep their authority
Core composes and delivers. It does not own the data.
Core carries
- The latest copy of every source, held together
- The composed shapes, per channel and per agent
- The entitlement rule deciding which price a caller may see
- The change detection that keeps every representation current
Your systems keep
- Your product master, commerce engine and content system: authority over their own data
- Your pricing engine: the calculation
- Your process tooling: orchestration between systems
Core is not a system of record and not a PIM. Sync Connectors are not an iPaaS and not a migration tool: they read what changed and the source stays where it is. The entitled price is carried to every surface that shows it, so the price on the shelf and the price in the portal are the same decision.
