Put analytics inside the product you sell, and give operators, CS, finance, and leadership the same hosted reporting layer for internal work. Named metrics stay consistent in the app, in embeds, and on internal boards.
Already have an account? Sign in · Governed metrics
One platform · One semantic layer · We operate the runtime
Start with customer-facing embeds, internal team reporting, or both. You don't need a separate BI stack for the office and a second project for the product. Governed metrics keep the numbers the same across both.
Ship dashboards inside your software. Customers stay in your product — no separate analytics login, no white-label detour.
Use the same hosted dashboard layer for people inside your company — ops, customer success, finance, product, and leadership — without standing up a second analytics program.
Define KPIs once against your warehouse. Your app can query them as named metrics. The hosted builder charts the same definitions. Tenant isolation is built in — not a filter you remember to add.
Browse warehouse tables, define measures and joins visually. The catalog is the contract — not a copy of SQL in every chart.
Headless KPIs via the Embedded Canvas SDK for in-app widgets and backend jobs. Same names your analysts use in dashboards. Every query is tenant-scoped.
Sync the catalog into hosted datasets so customer embeds and internal boards plot the same metric — not a second warehouse model.
Your product calls the metric API. The builder charts the published dataset. Both resolve Revenue the same way, filtered to the customer.
App query APIHosted dashboardsCustomer embedsCustomer embeds and internal reporting share hosting, security, operations, and the metric catalog — different audiences, same definitions.
Snowflake, BigQuery, Postgres, Redshift. Connected once, read-only.
Isolated runtime, semantic layer, embed sessions, audit, and day-two care — operated by us.
Inside your product, their login, your brand.
Ops, CS, finance, leadership — role-governed.
Warehouse once. Governed metrics sit on that warehouse so product embeds and internal views share the same KPI definitions.
Authors build in the hosted dashboard workspace. Register boards for customer embeds in your app, or share them with staff viewers and builders.
Runtime, isolation, and day-two care stay with us — whether the viewer is a customer or a teammate.
If you sell software and your own teams still live in spreadsheets or a bolted-on BI tool, this is the dual path.
Ship customer analytics — and in-app KPIs — without owning a forever BI platform project.
Live operational views on the same trusted warehouse your product uses.
Internal dashboards with governed access — not another shadow spreadsheet.
One reporting partner for external product value and internal visibility.
A customer-embed project plus a separate internal BI suite usually means duplicate modeling, duplicate ops, and conflicting numbers.
| Question | Separate embed + BI tools | Embedded Canvas |
|---|---|---|
| Where do customers see dashboards? | Inside your app (if you build embeds) | Inside your app — first-class embed path |
| Where do internal teams work? | Often a second BI product or spreadsheets | Same hosted reporting layer, team access |
| Who runs the analytics infrastructure? | You — twice, if stacks diverge | We host and operate one foundation |
| Do metrics stay consistent? | Easy to drift between product and office tools | Governed metrics — one semantic layer for app queries and dashboards |
A hosted reporting platform for software businesses: dashboards inside the product you sell, team reporting for people inside your company, and a governed semantic layer so KPIs mean the same thing in the app and on the board.
The semantic layer included in Platform. You name measures once (revenue, utilization, conversion), join the warehouse tables behind them, and reuse those names from your product API and from hosted dashboards. Tenant isolation is applied on every query. It is not a second BI tool you buy — it is how Embedded Canvas keeps product and office numbers aligned.
It often is if any of these sound familiar:
Your customers have been asking for reporting. or Your own teams need operational dashboards. or You don't want a separate BI stack for the office and another project for the product.
Yes. Many teams start with embeds for customers, or with internal dashboards for ops — then expand. Same control plane either way. Governed metrics ship with Platform.
No. Audiences, permissions, and delivery paths stay separate. What they share is hosting, security posture, and the underlying metric definitions — not the same view by default.
No. They stay in your product. When they open analytics, it feels like part of your software.
Typically a focused integration for embeds — not a platform rewrite. Internal reporting can roll out on the same operated layer without a second infrastructure program. Named metrics can be queried from your app via the Embedded Canvas SDK.
Each customer only sees their own data. Internal access is role-governed. We provide the controls and proof points your security and procurement reviewers expect. Ask us for a security packet if you need it in writing.
Platform is self-serve: your team builds dashboards; we host and operate the analytics layer. Governed metrics are included. Managed is premium: we build and operate dashboards for you via statement of work — useful for both customer packs and internal scorecards.
That's fine. Most teams start with a conversation about fit, data, and rollout — not a purchase decision.
Customer embeds, internal reporting, or both — we'll walk through fit, data, governed metrics, and rollout for your product and your teams.