Embedded analytics for SaaS products, portals, and enterprise apps
Why embedded analytics works inside the product
Not just dashboards in a frame. Datafor helps product teams embed analytics as part of the application experience.
Embed natively
Not a separate BI workspace. Keep users inside your product.
Control runtime context
Pass tenant, account, region, workflow state, or record context from your app.
Secure by identity
Apply SSO, JWT, permissions, and branded delivery without exposing raw BI complexity.
Choose your integration model
iFrame embedding
Fastest way to launch secure in-app dashboards.
SDK embedding
More control for UI, callbacks, and product integration.
Runtime filters
Analytics that respond to tenant, page, or workflow context.
SSO and JWT
Trusted access aligned with enterprise identity and permissions.
How teams usually start
Most teams begin with a fast embed path, then add more control as product requirements grow.
Start with iFrame
Launch quickly.
Add runtime context
Reflect product state.
Layer on trusted identity
Match enterprise access.
Use SDK where needed
Go deeper where more control is required.
Where embedded analytics fits best
Customer-facing SaaS analytics
Give each customer in-app dashboards without sending them to a standalone BI portal.
ERP, CRM, and business portals
Place analytics directly into operational screens so reporting supports the workflow instead of interrupting it.
Partner and dealer reporting
Deliver controlled analytics to external audiences with tenant-aware access and branded presentation.
Internal embedded workflows
Bring reports into finance, service, operations, or approval flows where decisions happen every day.
Built to feel native from the first release
A more refined integration layer for teams building analytics into the product, not around it.
Minimal example
Visualizer SDK
// App-side initialization
new Datafor.Visualizer({
el: container,
path: '/reports/sale.datafor',
parameters: appState
});