Skip to main content

Multi-Tenant SaaS

Administrator Developer & ISV

Building a Software-as-a-Service (SaaS) product often requires embedding analytics and reporting for your customers. However, building a secure, multi-tenant analytics layer from scratch is complex, expensive, and difficult to maintain.

DataCentral is designed from the ground up as a multi-tenant SaaS enablement platform. It acts as the missing control plane between your Power BI or Tabular data models and your end-users, allowing you to monetize data without building custom BI infrastructure.

1. The SaaS Analytics Challenge​

When SaaS vendors attempt to embed Power BI or other analytics tools natively, they typically face several hurdles:

  • Security & Isolation: Ensuring that Customer A cannot see Customer B's data requires complex, custom Row-Level Security (RLS) logic that is hard to audit and prone to human error.
  • User Management: Managing external customer identities, invites, and role assignments outside of your core application database.
  • White-Labeling: Providing a seamless, branded experience so the analytics portal looks like a native part of your SaaS product.
  • Tiered Packaging: Offering different levels of analytics (e.g., Basic vs. Pro dashboards) based on the customer's subscription tier.

2. How DataCentral Solves It​

DataCentral provides a turnkey, white-labeled analytics portal that handles the "last mile" of data delivery for your SaaS product.

True Multi-Tenancy​

You can deploy DataCentral using a Host/Tenant model. You act as the Host Administrator, provisioning isolated DataCentral "Tenants" for each of your SaaS customers.

  • Each customer gets their own branded subdomain (e.g., customer-a.yoursaas.com).
  • Each customer has their own isolated user list and roles.
  • DataCentral automatically enforces RLS boundaries, ensuring strict data isolation.

Seamless White-Labeling​

Your customers never need to know they are using DataCentral or Power BI.

  • Apply your SaaS branding (logos, primary colors, fonts) to the portal.
  • Use custom CSS to perfectly match the UI of your core application.
  • Configure custom domains using Azure Front Door or Cloudflare.

Flexible Authentication​

DataCentral integrates with your existing identity provider.

  • If your customers use Entra ID (Azure AD), they can use Single Sign-On (SSO).
  • If you manage identities in a custom database, you can use the Embedding API to securely inject reports directly into your own application frontend, bypassing the DataCentral UI entirely.

Tiered Analytics Offerings​

Using DataCentral's Editions and Feature Flags, you can package and monetize your data.

  • Create a "Basic" Edition that only grants access to standard operational reports.
  • Create a "Premium" Edition that unlocks advanced dashboards, data export capabilities, and DAX Query Links for raw data extraction.
  • Assign these Editions to your customer Tenants based on their subscription level.

3. Implementation Approaches​

Depending on your engineering resources and time-to-market goals, you can implement DataCentral in your SaaS product in two ways:

Approach A: The Standalone Portal (Fastest Time to Market)​

You provision a white-labeled DataCentral Tenant for your customer. You provide them with a URL (e.g., analytics.yoursaas.com) and they log in to view their reports.

  • Pros: Requires zero custom coding. You can launch a new analytics product tier in days.
  • Cons: The user experience is slightly disjointed, as users must leave your core application to view reports.

Approach B: API Embedding (Seamless UX)​

You use the DataCentral Embedding API to request encrypted report tokens and render the Power BI iframes directly inside your existing SaaS application's UI.

  • Pros: A perfectly seamless user experience. Users never leave your app.
  • Cons: Requires backend and frontend development work to integrate the API and handle the iframe rendering.

4. Next Steps​