Personalisation that goes beyond aesthetics.
DIXP® rewrites your website content dynamically — matching the language, framing, and emphasis to the specific cognitive frames of each visitor segment. Deployed inside your infrastructure: your data, your control.
One website. Many audiences.
One message that lands for none of them.
When the same product is sold to engineers, to procurement, and to executives — or to specialists, to patients, to journalists — generic copy under-converts every segment. A/B testing changes the visuals. Traditional personalisation engines reorder the layout. Most require sending visitor data to a third-party SaaS. Neither the framing problem nor the data sovereignty problem is solved.
DIXP® personalises meaning, not aesthetics.
Same page. Same brand voice. Same factual content. Different framing — chosen automatically based on who is reading. All processed inside your own environment.
Reads existing page content
No rewriting workflow, no separate CMS layer — DIXP® ingests your pages as-is.
Identifies visitor segment
From intent signals: referrer, behaviour, declared interest — matched automatically.
Rewrites in real time
Within brand guardrails defined by your team — no creative liberty, no surprises.
Preserves message integrity
Only the framing changes; facts, claims, and brand voice do not.
Runs where you run
DIXP® is a software component, not a SaaS service. It deploys inside your infrastructure. Your visitors' data stays with you.
DIXP® solves a problem that existing personalisation tools were not built for.
DIXP® is not a variant testing engine — it does not pit versions against each other.
DIXP® does not rearrange components or adjust visuals — the page structure stays intact.
DIXP® rewrites static page content, not chat — it works on what you have published.
DIXP® enforces strict brand voice control — no creative liberty, ever.
Four steps. Inside your environment.
Deployed in your stack
DIXP® is installed in your infrastructure as a server-side component, integrated with your CMS or platform.
Page content ingested
Your team approves source pages and defines brand voice rules — DIXP® does the rest from there.
Visitor signal detected
Segment matched from signals authorised by your consent layer. DIXP® reads the consent state from your platform and acts only within that boundary.
Content rewritten in real time
Server-side, within milliseconds — edge-cached. The new framing is delivered to the visitor; the original meaning is preserved.
[Visitor]
│
│ HTTP request
▼
[Your CMS / platform] ◄───── DIXP® runs here
│ (server-side, your stack)
│ rewritten page
▼
[Visitor receives personalised content]
LinkedBrains is not in this diagram. We don't see any of it. Where the same message reaches different readers.
The same drug information page reads differently for healthcare professionals, patients, and payers. DIXP® reframes — without rewriting clinical claims.
The same equipment page reads differently for an engineer, a procurement officer, and a C-level buyer. DIXP® shifts emphasis — specifications, total cost of ownership, strategic fit — without changing facts.
The same landing page reads differently for a technical evaluator and a business decision-maker. DIXP® adjusts the proof on display — features and integrations vs ROI and references.
We chose not to be your processor.
Most personalisation tools require sending visitor data to a third-party SaaS. DIXP® does not.
DIXP® is a software component you deploy in your own infrastructure. It runs on your servers. Your visitors' data never reaches LinkedBrains — there is no API call to us, no copy stored elsewhere, no telemetry sent home. We have built it this way because we want neither the responsibility of being your data processor nor the leverage it would give us over your business.
The consequence is operational. You are the data controller. You define the lawful basis (typically explicit consent via your existing CMP). You own the visitor profiles that segmentation produces. Architecture documentation supports your DPIA out of the box.
For most deployments, LinkedBrains is not even a processor under GDPR. We sell you a component. You operate it. The data stays where it already was.
- WordPress module — production-ready
- LLM integration: Claude API (Anthropic) and OpenAI API
- Server-side rewrite, edge-cached output
- Self-hosted: runs in your environment
- Drupal module — in final release stage
- REST API — language-agnostic integration for any platform
- Native consent management platform integration
- Additional LLM providers
Personalised meaning requires personalised insight. We have built DIXP® so the insight is yours, not ours — structured, accountable, and revocable, inside the boundary you control.
Currently onboarding by waitlist.
DIXP® is in private beta with selected partners. We are accepting new beta participants on a case-by-case basis.
We are building more.
DIXP® is the most mature of our internal projects. Other ventures currently in development:
Public availability dates have not yet been set. Updates will appear here as products mature.
Want DIXP® for your organisation?
Request beta access above, or talk to us about a tailored deployment.
Start a conversation