CEDX Embedded · Data & Analytics
Embedded puts the estate's analytics inside your product — tiles, dashboards, charts, explores and answer cards — with a p75 load budget per embed, scoped guest tokens, and tenant isolation tracked as a queue, not a promise.
The over-budget table doesn't round: Checkout health report at 5.6s p75 against the 2.0s budget, score 118.9. Embeds that miss the budget are listed, not excused.
Runs on demo data — the header reads “embed lag ~1m · demo seed” on the screen itself.
What it is
320 embeds list kind, render mode, p75 and payload: web components average 1.5s at 154 KB against the iframe's 2.0s at 378 KB. The 76 live embeds over budget are a filter chip away.
220 minted tokens carry scope — read:embed, guest:view, admin:theme — plus TTL, use counts and last-used. 35 expired tokens are still receiving traffic, and that alert names the grace TTL as the cause.
48 tenants on the isolation map, 17 open high-and-critical risks, strict isolation at 33.3%. Diagnosed alerts read symptom, cause, fix: the cross-tenant explore filter gap names the missing locked row filter.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/embedded.
01 — Overview
235 live embeds, 41.2K sessions a day, 1.7s p75, 129 active tokens, 17 isolation risks. Platform health reads 86 with budget breaches, isolation, expired tokens and over-budget counts itemized.
02 — Embeds
Orders day tile at 977ms and 48 KB; a cohort LTV dashboard at 1.8s and 327 KB; the ship-delay explore on SDK at 383 KB. Kind, render, status, p75, payload and sessions on every row.
03 — Tokens
A read token at 60m TTL with 23K uses; a guest token at 15m with 22K. Admin tokens for theme work sit beside guest tokens for viewing — scope decides, and the ledger counts.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Ships the web components and SDK integrations, and owns the payload budget — the 154 KB average says the wrapper work is paying off.
web component · 1.5s p75
Decides which tiles and answer cards ship to which tenants, and reads sessions-per-embed before the next rollout.
30 answer embeds · 63K questions
Works the isolation queue and the token ledger: rotates the 35 expired tokens still receiving traffic and closes the explore filter gap.
isolation open · 17The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Tiles, dashboards and answer cards are authored in the estate and published to the embed catalog.
A tenant gets scoped tokens — guest:view for readers, admin:theme for branders — with TTLs on the ledger.
Embeds render as iframe, web component or SDK; p75 and payload are metered against the 2.0s budget per embed.
Over-budget embeds, expired tokens and isolation gaps land in diagnosed queues with causes, not just counts.
One record
Embedded is not a screenshot service. Its tiles and answer cards execute against the estate's governed definitions — the same ones the metric layer certifies and the warehouse stores.
The tiles and answer cards in the embed catalog are Insight's governed metrics and Ask answers, rendered elsewhere.
CEDX WarehouseEvery embed executes against the warehouse's governed views — payload budgets meet query credits here.
CEDX ReportsBoard packs and embeds share the same definitions; what ships as a scheduled PDF can ship as a live tile.
CEDX Product AnalyticsEmbed sessions and answer-card questions are product events; the usage tab reads like its cousin's Live screen.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your product, our charts
Embedded with the rest of it
Questions
Yes. Every screenshot is a capture of the running build, and you can open the same build at /app/embedded. It runs on demo data, which the header states on screen.
Three, with the trade-offs printed: iframe (70 live, 2.0s p75, 378 KB average payload), web component (104 live, 1.5s, 154 KB — it inherits the host DOM and skips the frame wrapper), and SDK (61 live, 1.6s, 186 KB).
They are scoped — guest:view for readers, read:embed for embedding, admin:theme for brand work — with TTLs from 15 to 240 minutes, and every use counted against the ledger. The 35 expired tokens still receiving traffic are flagged, with the grace TTL named as the cause.
Per-tenant risk tracking: 17 open high-and-critical items, strict isolation at 33.3%, and tenants whose migration is paused named in the alert. It reads as a work queue because that is what it is.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Start with the chart your users keep asking support for.