What is BI tool integration?

Business intelligence (BI) tool integration means connecting your app to a dedicated reporting and analytics platform — Metabase, Power BI, Tableau, or Redash — and either embedding it directly within your app's UI or providing users with a seamless link to their own reporting environment.

Rather than building a custom report engine from scratch, you leverage a mature tool that already handles query building, chart rendering, scheduling, and export. Your job is connecting it to your data and ensuring users only see what they're authorised to see.

For small-to-medium Australian businesses that need flexible self-service reporting but don't want to pay for full enterprise BI licences, Metabase is particularly well-suited: it's open-source, self-hostable, and supports iframe embedding with row-level security — making it possible to surface reports inside your app so users never know they're looking at a separate tool.

When does your app need it?

• Your users need flexible, self-service reporting that goes beyond your app's pre-built reports
• You've been asked to build a custom report builder but want a faster, cheaper alternative
• Different users need significantly different views of the same underlying data — a BI tool handles this out of the box
• Your business already uses Power BI or Tableau and wants reports accessible from within the app, not in a separate tab
• You want to offer advanced analytics without hiring a specialist data engineer to build the infrastructure
• Your data lives in a cloud data warehouse (BigQuery, Redshift, Snowflake) and you need a reporting layer on top of it

How much does it cost?

BI tool integration typically adds 5–11 hours of development — roughly $1,000–$2,000 AUD at Australian boutique agency rates.

The lower end covers setting up a Metabase instance (typically self-hosted on a small cloud VM or managed service), connecting it to your database, creating initial dashboards, and linking to them from your app. The upper end covers Metabase embedding with signed JWT tokens (so users see an embedded dashboard inside your app UI) and row-level security (so each tenant only sees their own data).

Power BI and Tableau embedding are more complex and carry their own per-user licensing costs — these are typically more appropriate for enterprise deployments than SME apps.

How it's typically built

For Metabase embedding, the developer installs Metabase (self-hosted on an EC2 or similar instance, or via Metabase Cloud), connects it to a read-only replica of your production database, and creates the required dashboards and questions.

To embed Metabase securely within your app, the backend generates a signed JWT token for each user session — the token encodes the user's identity and the data filters they're allowed to see (e.g., organisation_id = 42). The frontend renders an iframe pointing to the Metabase embed URL with this token as a parameter. The result: users see a live, interactive dashboard inside your app without any Metabase branding.

The read-only database connection ensures BI tools cannot modify your production data. For sensitive applications, a dedicated reporting replica or data warehouse (rather than your live database) is worth the additional infrastructure cost.

For Power BI, Microsoft provides an embed API and SDK; the flow is similar but requires Azure AD authentication and Power BI workspace setup — adding time compared to Metabase.

Questions to ask your developer

• Should users see Metabase branding, or should it appear seamlessly integrated? Seamless embedding with signed tokens is more work than a simple link to a shared dashboard.
• Do different users need to see different data? Row-level security (each user's token restricts what data the queries return) is the key requirement for multi-tenant embedding — confirm your developer has done this before.
• Where will Metabase be hosted, and who manages it? Self-hosted is cheaper but adds an infrastructure component to maintain; Metabase Cloud is a managed option with a monthly fee.
• Do we need to connect to a data warehouse, or can we use the production database directly? For high query volumes, a read replica or separate analytics database avoids impacting production performance.
• What's the ongoing cost? Self-hosted Metabase is free; Metabase Cloud starts around $500 AUD/month. Power BI embed licensing can be significant — get a quote before scoping.

---

See also: Custom report builder · Analytics dashboard · Data visualisation and charts · App cost calculator