LYMRICEnterprise
Enterprise & developers
Your content infrastructure. Our engine underneath.
Run LYMRIC across a group, an agency network or your own product. White-label it, embed it, or build on the API. Governance comes with it.
LYMRIC can disappear without losing provenance.
Four deployment models
Same engine. Four amounts of LYMRIC.
Workspace · White-label · Embedded · Headless. Each model keeps the engine. Only what your users see changes.
What the customer buys · who it fits
The full application with enterprise governance: roles, approval policies, brand isolation, audit log, SSO. For groups, events, hospitality and multi-brand teams.
A hosted LYMRIC experience under your identity and domain. For agencies, platforms, media groups and franchises.
Campaign, approval or analytics surfaces inside your product. For SaaS, event platforms and DAM/CMS products.
API and MCP only; you own the whole front end. For technology platforms and internal systems.
Organization hierarchy
- Organization→
- Region / business unit→
- Brand / client→
- Campaign→
- Source / asset
Policies cascade down. Each brand keeps its own Brand Memory, rights and markets, and the Oracle never crosses brands without permission.
White-label
Your name on the product. Ours in the footnote.
Your name, logo, colours and domain, from login to client reports. Choose a stop below and watch LYMRIC step back. The provenance never does.
How much of LYMRIC your users see
Your product
Your Studio
Powered by
4 active · 2 awaiting client approval
11 processed this month
1 expiry in 30 days
Branded exposure report ready
campaign.propose → {
direction,
evidence: [{ tc: "00:34:18", speaker: "Amélie Martin" }],
rights: { organic: "EU + UK", paid: "blocked" }
}Source ✓ 00:34:18 Rights ✓ organic EU + UK
- Branded login, emails, client portals and reports
- Custom domain and colour tokens
- Custom navigation, terminology and module hiding
Where attribution is contractually required, it is one quiet wordmark in the chrome.
Governance, trust & security
Controls we’ve built, stated precisely.
Approval and Rights Gate are enforced on the server, never left to an agent.
We don’t claim certifications we don’t hold: SOC 2, ISO and data residency are roadmap or contracted until validated.
Custom roles, brand isolation, publishing limits by country, channel or team.
Policies by brand, market, channel and risk. Ambiguous rights go to a human queue.
SSO/SAML, SCIM where required, scoped service accounts and API scopes.
Ingest, edits, approvals, rights, publishing and API calls, logged by tenant and actor.
Encrypted in transit and at rest. Private sources behind short-lived signed URLs. Retention policy.
Templates are not legal advice. Rights Gate overrides need a permission and a reason, and are audited.
Developer platform
You build the experience. LYMRIC runs the intelligence.
Versioned REST, scoped MCP tools, signed webhooks. Endpoint names never depend on a model provider.
Resources
/organizations /brands /sources
/people /rights /campaigns
/assets /approvals /publications
/analytics /queries /capture-briefs
API keys for server-to-server, OAuth 2.0 for third-party apps, scoped service accounts for enterprise. Idempotency keys on every create, render and publish.
Scoped MCP tools
# Governed server-side, never by agent goodwill
brand.get_contextreturn scoped Brand Memory
source.ingestregister or import a source
source.searchfind evidence, quotes, moments
campaign.proposeask The Scribe for directions
campaign.generategenerate the campaign manifest
clips.findscored candidates, no render
clips.renderrender an approved clip spec
rights.checkvalidate a planned use
content.validatebrand · source · rights checks
publish.schedule// rejects unapproved assets
analytics.campaignnormalized performance
oracle.querypermissioned intelligence
director.briefnext capture brief
The MCP safety model
- Read tools and write/publish tools carry separate scopes
- An agent can propose or generate without the right to publish
- rights.check and content.validate are callable before publish.schedule
- publish.schedule rejects unapproved or blocked assets server-side
- Every call is logged by tenant, actor, tool and result
- Administrators can disable whole tool families
Webhooks
Ten events. No polling.
source.processed
campaign.proposed
campaign.ready
asset.rendered
asset.approved
rights.blocked
publication.scheduled
publication.published
publication.failed
analytics.updatedRate limits by plan, key and endpoint family. Contracts are versioned; schemas never break silently.
Developer tiers
Start in the sandbox. Publish when you’re ready.
Overage: $12 per source hour on Build, $10 on Platform.
Price · included
$0 — 1 developer workspace, 2 source hours a month, API, MCP, webhooks and sandbox rendering. No production publishing.
$499/month — 20 source hours, 3 active brands, 50k API/MCP calls, production render and publish, Brand Memory, Rights API and analytics.
$1,490/month — 100 source hours, 15 active brands, 250k calls, multi-tenant, The Oracle, Creative DNA, The Content Director and priority processing.
Custom — volume, custom SLA, white-label, SSO, security review, and custom region or integration where contracted.
Launch limits are validated against measured cost before public release.
The layer between what you know and what the market sees.
Recommended contract value from $30k a year, scoped on brands, source volume, users, markets and integrations.