Put analytics inside the product you sell, and give operators, CS, finance, and leadership the same hosted reporting layer for internal work. One platform. Two jobs.
Switch customers below. Same page, same product — different data for each customer. That is what "embedded" means in practice.
Short guided demos for embeds, internal reporting, and the console. More will land here as we ship them.
Key isolation, backend JWT mint, frontend mount, and a live embed — framework-agnostic walkthrough.
How teams publish Internal boards to /reports and share them with Viewers.
Operator console: connect data, register dashboards, keys, and day-two ops.
Prefer the interactive sample on this page? Jump to the live dashboard showcase.
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.
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.
Customer embeds and internal reporting share hosting, security, and operations — different audiences, same foundation.
Warehouse and sources once. Models and dashboards serve both product embeds and internal views.
Authors build in the dashboard workspace. Publish into your app for customers, or into team views for staff.
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 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 | Shared models and dashboards across audiences |
A hosted reporting platform for software businesses: dashboards inside the product you sell, and team reporting for people inside your company — same foundation, separate audiences.
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.
No. Audiences, permissions, and publish targets stay separate. What they share is hosting, security posture, and the underlying data work — 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.
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. More detail is in our trust center.
Platform is self-serve: your team builds dashboards; we host and operate the analytics layer. 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 checkout flow.
Customer embeds, internal reporting, or both — we'll walk through fit, data, and rollout for your product and your teams.