<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by 5000fish on Medium]]></title>
        <description><![CDATA[Stories by 5000fish on Medium]]></description>
        <link>https://medium.com/@5000fish?source=rss-fa7a4766af1d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tK_SxhmdZmc28vrg.jpeg</url>
            <title>Stories by 5000fish on Medium</title>
            <link>https://medium.com/@5000fish?source=rss-fa7a4766af1d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:09:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@5000fish/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Build Your Embedded Analytics Integration with the Yurbi API]]></title>
            <link>https://medium.com/@5000fish/build-your-embedded-analytics-integration-with-the-yurbi-api-1ea651df3c50?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ea651df3c50</guid>
            <category><![CDATA[embedded-analytics]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[yurbi]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 15:28:44 GMT</pubDate>
            <atom:updated>2026-11-03T15:29:00.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Yurbi - Self-Hosted BI Tool Integration" src="https://cdn-images-1.medium.com/max/600/0*YnB3c6kw9M1X53jV.jpg" /></figure><p>If you’re evaluating embedded analytics for your software, the question that matters after “does it look right?” is “how much work is the integration?” We’ve published the answer at <a href="https://developers.yurbi.com/">developers.yurbi.com</a>: a complete reference for the Yurbi embedded analytics API, guides for each common integration task, a Postman collection, and AI-ready files you can load into your coding assistant so it writes against real endpoints instead of guessing.</p><p><strong>The short answer:</strong> a working embed takes two API calls, a sign-in that returns a session token and an iframe URL that uses it. Everything else a software vendor needs (provisioning tenants, isolating each customer’s data, white-labeling, running reports from your own code) is documented step by step.</p><h4>What’s on the developer site</h4><p>The Yurbi API is deliberately simple. Every endpoint is an HTTP POST that accepts and returns JSON, all endpoints live under one base path on your own Yurbi server, and there is one authentication model: sign in once, then pass the session token on every call.</p><p>The site has three parts:</p><ul><li><strong>Getting started.</strong> A <a href="https://developers.yurbi.com/quickstart/">Quickstart</a> that gets you to a first successful call in a few minutes, plus how <a href="https://developers.yurbi.com/authentication/">sessions and tokens</a> work and the <a href="https://developers.yurbi.com/conventions/">conventions and error codes</a> shared by every endpoint.</li><li><strong>Guides.</strong> Use-case walkthroughs written for software teams building Yurbi into their own product.</li><li><strong>API reference.</strong> More than 80 endpoints, each with its parameters, a request body and a real example response. The <a href="https://developers.yurbi.com/reference/">Reference</a> page has a built-in “Try it”: enter your server’s address and a token, and send any request live or copy it as cURL.</li></ul><h4>The integration path, step by step</h4><p>Most embedded reporting integrations follow the same sequence. Each step below links to the guide that covers it.</p><h4>1. Sign users in without a second login</h4><p>You already authenticate users in your application, so they shouldn’t have to sign in to reporting separately. Your server calls the sign-in endpoint, receives a session token, and uses it either to embed specific content or to drop the user straight into the full Yurbi interface. The <a href="https://developers.yurbi.com/guides/single-sign-on/">Single Sign-On guide</a> covers both options and how to keep sessions alive.</p><h4>2. Provision each customer as a tenant</h4><p>Serving many customers from one Yurbi instance comes down to a repeatable structure: one security group per tenant, one library folder scoped to that group, and users who belong to exactly one tenant. The <a href="https://developers.yurbi.com/guides/multi-tenant-provisioning/">Multi-tenant provisioning guide</a> gives you the calls in order, so onboarding a new customer becomes part of your own signup flow rather than a manual admin task.</p><h4>3. Isolate each tenant’s data with row-level security</h4><p>A single report should serve every customer while returning only the rows each one is entitled to. Yurbi does this with data tags and data security policies applied when the report runs, so the same restriction covers the interface, embeds, exports and scheduled email. The <a href="https://developers.yurbi.com/guides/data-security/">Row-level data security guide</a> shows how to set it up and, just as important, how to verify it.</p><h4>4. Embed dashboards and reports</h4><p>With a token in hand, build an embed URL for a dashboard or report and place it in an iframe. You can pre-fill report prompts in the URL, too. The <a href="https://developers.yurbi.com/guides/embedding/">Embedding guide</a> covers finding item IDs, prompts and session handling.</p><h4>5. Run reports from your own code</h4><p>Sometimes you want the data, not the visualization: to feed your own UI, a data export or another system. The <a href="https://developers.yurbi.com/guides/running-reports/">Run reports from your app guide</a> walks through finding a report, supplying prompt values and reading the rows and columns that come back.</p><h4>6. Make it look like your product</h4><p>Branding profiles control logos, colors, fonts, the login page and which features each audience sees, and they can be assigned per tenant group. See <a href="https://developers.yurbi.com/guides/branding/">Branding and white-labeling</a> and, for pixel-level control, <a href="https://developers.yurbi.com/guides/custom-css/">Custom CSS</a>.</p><h4>7. Keep integration accounts working as security tightens</h4><p>If your customers turn on two-factor authentication or password rules, the accounts your application signs in with should keep working. The <a href="https://developers.yurbi.com/guides/login-security/">Login security and two-factor guide</a> explains how to flag those accounts as service accounts so automated sign-ins are never interrupted.</p><p>There’s also a guide to <a href="https://developers.yurbi.com/guides/building-apps-and-reports/">building apps and reports through the API</a> for teams that generate the reporting layer at provisioning time or migrate reports in from another tool.</p><h4>Get running in minutes with Postman and OpenAPI</h4><p>You don’t need to write code to explore the API. On the <a href="https://developers.yurbi.com/spec/">API spec and tooling page</a> you’ll find:</p><ul><li><strong>A Postman collection</strong> with every documented endpoint as a ready-to-send request, grouped by area. Set your server address, run the sign-in request, and the collection captures the token for every other call.</li><li><strong>An OpenAPI 3.1 spec</strong> you can import into Swagger UI or Insomnia, or use with a code generator to scaffold a typed client in your language.</li></ul><p>Both are generated from the same source as the documentation, so they always match the published reference.</p><h4>Let your AI coding assistant write the integration</h4><p>This is the part we’re most excited about. The developer site publishes two files written for AI models:</p><ul><li><a href="https://developers.yurbi.com/llms.txt">llms.txt</a>, a compact index of the documentation.</li><li><a href="https://developers.yurbi.com/llms-full.txt">llms-full.txt</a>, the complete documentation, guides and endpoint reference in a single file.</li></ul><p>Load llms-full.txt into Claude, ChatGPT, Copilot, Cursor or whichever assistant your team uses, and it can answer questions and write integration code against the real endpoints, parameters and response shapes. A few prompts to try:</p><ul><li>“Using the Yurbi API documentation, write a Node.js function that signs a user in and returns an embed URL for dashboard 123. Cache the token on the server.”</li><li>“Write a Python script that provisions a new tenant: create the security group, the library folder scoped to it, and a first user with an Agent role.”</li><li>“Given the Yurbi API docs, how do I run a report with two prompts and return the rows as JSON?”</li></ul><p>As with any generated code, review it, keep credentials on your server, and test against a non-production Yurbi instance before you ship.</p><h4>Why this beats vibe-coding the whole reporting layer</h4><p>We recently wrote about <a href="https://claude.ai/blog/vibe-coded-dashboards-vs-embedded-analytics/">vibe-coded dashboards vs. embedded analytics</a>: AI tools can build a working dashboard in an afternoon, but the long-term cost of customer-facing reporting is everything around that dashboard.</p><p>Using AI to write your integration with Yurbi is a different thing, and it’s the approach we recommend:</p><ul><li><strong>Vibe-coding the reporting layer</strong> means AI generates the dashboards, queries, permissions and tenant isolation, and your team owns, tests and maintains all of it, along with every new report request that follows.</li><li><strong>AI-assisted integration</strong> means AI writes the small amount of glue code between your application and Yurbi: sign-in, tenant provisioning, embed URLs. Yurbi supplies the report builder your customers use themselves, tenant isolation enforced at the query level, scheduling, exports, permissions and white-labeling.</li></ul><p>The code you own stays small and well-defined, because it targets a documented API instead of reinventing a reporting product. That’s also what makes AI assistance reliable here: the assistant is working from an accurate reference rather than inventing an architecture.</p><h4>Built for software vendors who self-host</h4><p>Yurbi runs on your own infrastructure, Linux, Docker or Windows, so your customers’ data stays where it already lives and the API talks to your own server. That keeps the integration simple to reason about for your security reviews, and it means the documentation describes exactly what you’ll deploy.</p><h4>Start building</h4><ul><li>Explore the docs at <a href="https://developers.yurbi.com/">developers.yurbi.com</a>, starting with the <a href="https://developers.yurbi.com/quickstart/">Quickstart</a>.</li><li><a href="https://claude.ai/trial/">Start a free trial</a> and make your first API call against your own server today.</li><li>Prefer a walkthrough? <a href="https://claude.ai/demo/">Book a demo</a> and we’ll go through the integration path for your product.</li></ul><p>If there’s a call you need that isn’t documented yet, tell us what you’re trying to accomplish. We’re glad to help, and to add it to the docs if it fits.</p><h4>Frequently asked questions</h4><h4>How long does it take to embed Yurbi in a SaaS application?</h4><p>A basic embed takes two API calls: one to sign the user in and get a session token, and an iframe that uses that token. Most of the remaining work is provisioning tenants and setting up row-level security, which the developer guides walk through step by step.</p><h4>Does the Yurbi API support multi-tenant embedded analytics?</h4><p>Yes. The recommended structure is one security group and library folder per tenant, with data security policies that constrain every query to the tenant’s own rows. The Multi-tenant provisioning guide lists the API calls to automate it.</p><h4>Can I use AI coding assistants to build a Yurbi integration?</h4><p>Yes. The developer site publishes llms.txt and llms-full.txt, which you can load into Claude, ChatGPT, Copilot or Cursor so the assistant writes code against the real endpoints. Review and test generated code before using it in production.</p><h4>Is there a Postman collection or OpenAPI spec for the Yurbi API?</h4><p>Yes. Both are available on the API spec and tooling page at developers.yurbi.com and are generated from the same source as the documentation.</p><h4>How is AI-assisted integration different from vibe-coding dashboards?</h4><p>Vibe-coding builds the reporting layer itself, which your team then maintains. AI-assisted integration only generates the glue code between your application and Yurbi, while Yurbi provides the report builder, tenant isolation, scheduling, exports and white-labeling.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ea651df3c50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embedded Analytics for .NET and SQL Server SaaS Apps (2026)]]></title>
            <link>https://medium.com/@5000fish/embedded-analytics-for-net-and-sql-server-saas-apps-2026-8d7b5d3519da?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d7b5d3519da</guid>
            <category><![CDATA[sql-server]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 01:53:55 GMT</pubDate>
            <atom:updated>2026-10-27T01:54:23.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Yurbi - Embedded Analytics for .net and sql server saas apps" src="https://cdn-images-1.medium.com/max/600/0*uNnJ02DjDAdi22Oo.jpg" /></figure><p>​<strong>Short answer:</strong> If your SaaS product runs on .NET and SQL Server, look for embedded analytics that connects natively to SQL Server, supports Windows and Active Directory sign-in, runs on Windows Server or in your own Azure account, and embeds without rewriting your front end. SSRS still works but is getting no new versions, Power BI Embedded is strong but cloud-only and capacity-billed, and building it in-house means owning a reporting product. Yurbi is built on .NET, recommends SQL Server as its own backend, and embeds with an API call and an iframe — from $10,000 a year, flat.</p><p>A lot of the embedded analytics conversation assumes a JavaScript-first app sitting on a cloud data warehouse. Plenty of real software doesn’t look like that. Many ISVs run on ASP.NET with SQL Server underneath — on-premise, in Azure, or shipped to customers’ own servers — and they’ve been delivering reports to customers for years, often through SSRS or Crystal Reports.</p><p>If that’s your stack, this guide covers what to look for, how the common options compare, and what a move off legacy reporting actually involves.</p><h4>What .NET and SQL Server teams need from embedded analytics</h4><p>The requirements are different from a cloud-native startup’s. These are the ones that usually decide the shortlist:</p><ul><li><strong>Native SQL Server performance.</strong> Reports should query your SQL Server database directly through a native driver, not through an ODBC layer or a nightly copy into a warehouse.</li><li><strong>Azure SQL and Managed Instance support.</strong> If you’ve moved to Azure, the same tool should work against Azure SQL Database and Managed Instance without changes.</li><li><strong>Windows and Active Directory sign-in.</strong> Many .NET products run in domain-joined environments. Reporting should be able to use the same identity.</li><li><strong>Runs where your app runs.</strong> Windows Server, IIS, your own Azure subscription, or a customer’s server — not a separate vendor cloud your customers’ security teams have to review.</li><li><strong>No front-end rewrite.</strong> Embedding shouldn’t require adopting a new JavaScript framework in a mature ASP.NET or Blazor app.</li><li><strong>A path off SSRS or Crystal.</strong> Most teams on this stack already have a report library. The new tool has to connect to the same databases and let you rebuild it.</li></ul><h4>The options, compared</h4><p>Option How it works Where it runs Pricing model Customer self-service <strong>Option</strong> <strong>How it works</strong> <strong>Where it runs</strong> <strong>Pricing model</strong> <strong>Customer self-service</strong> <strong>Stay on SSRS</strong> RDL reports in Report Server Your servers Included with SQL Server Limited <strong>Power BI Report Server</strong> Paginated and Power BI reports Your servers SQL Server or Power BI licensing Limited for embedding <strong>Power BI Embedded</strong> Power BI in your app via Azure Azure cloud only Capacity, billed hourly Yes <strong>Build it in .NET</strong> Your own charts, grids, and exports Anywhere Engineering time Whatever you build <strong>Yurbi</strong> Iframe plus REST API Your servers or Azure account Flat annual, $10K–$30K Yes, no-code builder</p><h4>SSRS: still supported, but the roadmap is closed</h4><p>SSRS has been the default reporting layer for .NET products for two decades, and it still works. But Microsoft has confirmed there will be no new versions: SQL Server 2025 shipped without SSRS, and SSRS 2022 is the last release, with security support through January 11, 2033. Microsoft points customers to Power BI Report Server instead.</p><p>That’s real runway, but it isn’t a future. SSRS was built for developer-authored reports — every new report or change goes back to your team — and it was never designed for multi-tenant, customer-facing self-service.</p><h4>Power BI Report Server: the Microsoft-recommended successor</h4><p>Power BI Report Server hosts paginated RDL reports and Power BI reports on your own servers, so it’s the most familiar step for an SSRS shop that’s staying fully inside Microsoft. It’s a reasonable choice for internal reporting. For customer-facing, multi-tenant embedding inside your product, it’s a harder fit — per-tenant branding and self-service report building for your customers aren’t what it was designed for.</p><h4>Power BI Embedded: powerful, but cloud-only and capacity-billed</h4><p>Power BI Embedded puts Power BI visuals inside your app and has strong .NET SDK support. It’s billed by the hour for the capacity you provision (A and F SKUs) — roughly $740 a month for A1 at continuous use — and capacity doesn’t autoscale, so heavy customer usage slows reports until you move to a larger tier, with each step roughly doubling the cost. It runs only in Azure, which matters if your customers need data to stay on their own servers.</p><h4>Building it yourself in .NET</h4><p>There are excellent .NET charting and grid libraries, and a capable team can ship a first dashboard quickly — faster still with AI coding tools. The work that never ends is everything around it: per-customer data isolation, a report builder so customers stop filing report requests, scheduling, exports, permissions, and maintenance as your schema changes. We covered that trade-off in <a href="https://yurbi.com/blog/vibe-coded-dashboards-vs-embedded-analytics/">Vibe-Coded Dashboards vs. Embedded Analytics</a>.</p><h4>Why Yurbi fits a .NET and SQL Server stack</h4><p>Yurbi is a self-hosted embedded analytics platform, and its stack lines up closely with a typical .NET ISV’s:</p><ul><li><strong>Built on .NET.</strong> Yurbi itself runs on .NET 9 and installs on Windows Server (or Windows 10/11) using IIS or its built-in web server, on Linux, or with Docker.</li><li><strong>SQL Server first.</strong> Yurbi connects to SQL Server, Azure SQL Database, and Azure SQL Managed Instance through its native driver. Microsoft SQL Server is also the recommended backend for Yurbi’s own configuration database in high-volume, multi-tenant deployments.</li><li><strong>Windows and Active Directory sign-in.</strong> When the Yurbi server is domain-joined, Windows authentication routes sign-in through your Active Directory — no separate LDAP setup. Built-in two-factor sign-in and Cisco Duo are also available.</li><li><strong>Query your database directly.</strong> Reports query your SQL Server tables, views, and stored procedures in place, read-only. No ETL, no warehouse, no data copy.</li><li><strong>Multi-tenant by design.</strong> Tenant isolation is enforced in the SQL query itself, and each customer can have their own branding. It works whether your customers share one database, have their own schemas, or have their own SQL Server instances.</li><li><strong>Flat pricing.</strong> $10,000 a year for 75 users up to $30,000 a year for unlimited users, with every feature in every plan.</li></ul><h4>How embedding works in an ASP.NET app</h4><p>Embedding doesn’t touch your front-end framework. From your .NET backend:</p><ol><li>Call Yurbi’s DoLogin API with the signed-in user’s Yurbi credentials. It returns a session token scoped to that user’s permissions.</li><li>Build the embed URL for a dashboard or report, adding the session token.</li><li>Render that URL in an iframe in your Razor page, MVC view, or Blazor component.</li></ol><p>Your customer lands on their analytics already signed in, already filtered to their data, under your brand. The full REST API also lets your backend create tenants, users, and data source connections automatically when a new customer signs up. Details are in the <a href="https://developers.yurbi.com/">Yurbi developer docs</a>.</p><h4>Moving off SSRS, Crystal Reports, or Izenda</h4><p>Most .NET teams aren’t starting from zero — they have a report library. Here’s what a migration typically looks like:</p><ol><li><strong>Connect Yurbi to the same SQL Server databases.</strong> Read-only, no schema changes.</li><li><strong>Build the semantic layer once.</strong> Map tables to business-friendly names, define joins, and add calculated fields. This is what makes self-service possible.</li><li><strong>Set up tenant security.</strong> Configure Tenant Mode and data-level policies so each customer sees only their own rows.</li><li><strong>Rebuild your core reports.</strong> There’s no automated import of RDL or Crystal report definitions, but rebuilding in a no-code builder is usually faster than maintaining the old library — and customers can build the long tail themselves.</li><li><strong>Embed and roll out.</strong> Swap the old report viewer for the iframe, beta with a few customers, then go live.</li></ol><p>Most teams reach production in 4 to 8 weeks, and Yurbi’s services team can handle the migration if your developers are busy. See <a href="https://yurbi.com/solutions/legacy-replacement/">Legacy Replacement</a>, <a href="https://yurbi.com/vs/ssrs/">Yurbi vs SSRS</a>, and <a href="https://yurbi.com/vs/izenda/">Yurbi vs Izenda</a> for more.</p><h4>Frequently asked questions</h4><h4>What is the best embedded analytics tool for a .NET application?</h4><p>It depends on where your app runs and who uses the reports. For customer-facing, multi-tenant embedding on SQL Server — especially self-hosted — Yurbi is built for that use case: it runs on .NET, connects natively to SQL Server, supports Active Directory sign-in, and embeds with an API call and an iframe. Power BI Embedded is a strong choice for Azure-only, Microsoft-centric products, and Power BI Report Server suits internal reporting.</p><h4>Is SSRS being discontinued?</h4><p>Microsoft has stopped releasing new versions of SSRS. SQL Server 2025 shipped without it, and SSRS 2022 is the final release, with security support through January 11, 2033. Microsoft recommends Power BI Report Server as the replacement.</p><h4>Can Yurbi use Active Directory for sign-in?</h4><p>Yes. When the Yurbi server is domain-joined, Windows authentication routes sign-in through your Active Directory, with no separate LDAP configuration. Yurbi also supports session-token single sign-on for embedding, built-in two-factor sign-in, and Cisco Duo.</p><h4>Does Yurbi work with Azure SQL Database?</h4><p>Yes. Azure SQL Database and Azure SQL Managed Instance use the same native SQL Server driver as on-premise SQL Server. Yurbi can run in your own Azure account or on your own servers.</p><h4>Can I migrate SSRS reports to Yurbi?</h4><p>Yes, by rebuilding them. Yurbi connects to the same SQL Server databases, so there’s no data migration, but RDL report definitions aren’t imported automatically. Most teams rebuild their core reports in Yurbi’s no-code builder and let customers build the rest themselves. Yurbi’s services team can do the migration for you.</p><h4>How much does Yurbi cost for a .NET SaaS product?</h4><p>Yurbi’s published pricing is $10,000 a year for up to 75 users, $18,000 for 250, $24,000 for 500, and $30,000 for unlimited users, with every feature in every plan. Startup pricing is available for qualifying early-stage companies — ask at <a href="https://yurbi.com/contact/?topic=startup">https://yurbi.com/contact/?topic=startup</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d7b5d3519da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Metabase Embedding Alternatives for SaaS in 2026: When Open Source Stops Being Free]]></title>
            <link>https://medium.com/@5000fish/metabase-embedding-alternatives-for-saas-in-2026-when-open-source-stops-being-free-4b3b3863203f?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b3b3863203f</guid>
            <category><![CDATA[reveal-bi]]></category>
            <category><![CDATA[microsoft-power-bi]]></category>
            <category><![CDATA[sisense]]></category>
            <category><![CDATA[apache-spark]]></category>
            <category><![CDATA[metabase]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 01:45:13 GMT</pubDate>
            <atom:updated>2026-10-27T01:45:57.669Z</atom:updated>
            <content:encoded><![CDATA[<p>​</p><figure><img alt="Yurbi - Alternative to Metabase Embedded" src="https://cdn-images-1.medium.com/max/600/0*XmzNkYEK0nLg_VSl.jpg" /></figure><p><strong>Short answer:</strong> Metabase is a great place to start, and its guest embeds are free on the open-source edition. Teams look for an alternative when they need what customer-facing embedding really requires: no “Powered by Metabase” banner, sign-in embeds, row-level security, and per-tenant isolation. Those features start at Metabase Pro, which bills every signed-in viewer as a user — roughly $135,000–$149,000 a year at 1,000 customer users. If you need white-label, multi-tenant embedding at a flat price, Yurbi starts at $10,000 a year and tops out at $30,000 for unlimited users.</p><p>Metabase is usually the first embedded analytics tool a SaaS team tries, and for good reason. It’s open source, it installs quickly, and a developer can have a chart inside your product the same afternoon. Many teams stay on it happily.</p><p>The question usually comes later, when the embedding moves from “a chart on a page” to “analytics our customers log into and rely on.” That’s when the plan details start to matter.</p><h4>Why teams outgrow Metabase embedding</h4><p>Metabase’s own pricing and embedding docs (checked October 2026) lay out where the lines are. Here’s what product teams typically run into.</p><ul><li><strong>The banner.</strong> Guest embeds on the open-source edition and the Starter plan show a “Powered by Metabase” banner. Removing it, along with white-labeling, custom colors, fonts, and themes, requires Pro or Enterprise.</li><li><strong>Sign-in embedding is a paid feature.</strong> Guest embeds are free, but SSO embeds (JWT or SAML), full-app embedding, and the React SDK require Pro or Enterprise. So do the self-service pieces customers ask for inside an embed, like the query builder and drill-through.</li><li><strong>Multi-tenant security is a paid feature.</strong> Tenants, row- and column-level security, impersonation, and one database per tenant are Pro and Enterprise features.</li><li><strong>Every signed-in viewer is a billable user.</strong> Guest viewers don’t count, but each person who signs in to an SSO or full-app embed counts as a user — the same as your own team. Pro is $575 a month including 10 users, plus $12 per user per month ($6,210 a year plus $130 per user on yearly billing).</li><li><strong>The license.</strong> The open-source edition is licensed under AGPL v3. If you modify Metabase and serve it to customers over a network, that license has obligations worth reviewing with your counsel.</li></ul><p>None of this makes Metabase a bad product. It means the cost of customer-facing embedding scales with your customer count, and that’s exactly when teams start comparing.</p><h4>What the math looks like as you grow</h4><p>Here’s Metabase Pro on yearly billing for sign-in embedding, next to Yurbi’s published plans. Metabase figures are from its pricing page; your actual quote may differ, especially on Enterprise.</p><p>Customer users Metabase Pro (yearly) Yurbi (yearly) <strong>Customer users</strong> <strong>Metabase Pro (yearly)</strong> <strong>Yurbi (yearly)</strong> <strong>75</strong> About $14,700 $10,000 (Starter) <strong>250</strong> About $37,400 $18,000 (Growth) <strong>500</strong> About $69,900 $24,000 (Scale) <strong>1,000</strong> About $134,900 $30,000 (Unlimited)</p><p>Metabase Enterprise starts at $20,000 a year with custom pricing, including per-tenant or flat-fee options, so it’s worth getting a quote if you’re heading that way.</p><h4>What to look for in a replacement</h4><p>If you’re embedding analytics for your customers rather than your own team, these are the questions that matter most:</p><ul><li><strong>Tenant isolation.</strong> Is it enforced in the query itself, or is it something your code has to get right every time?</li><li><strong>White-label on every plan.</strong> Can each customer see their own branding, with no vendor badge?</li><li><strong>A pricing model that doesn’t punish growth.</strong> Per-viewer, per-capacity, and flat pricing behave very differently at 1,000 users.</li><li><strong>Self-service.</strong> Can customers build their own reports, or does every new question become a ticket for your developers?</li><li><strong>Where it runs.</strong> Do you need it in your own cloud account or data center for your customers’ security reviews?</li></ul><h4>Metabase embedding alternatives compared</h4><p>Platform Pricing model White-label Self-hosted Best for <strong>Platform</strong> <strong>Pricing model</strong> <strong>White-label</strong> <strong>Self-hosted</strong> <strong>Best for</strong> <strong>Yurbi</strong> Flat annual, $10K–$30K Every plan, per tenant Yes, every plan ISVs embedding for many customers <strong>Apache Superset</strong> Free, open source Custom work per tenant Yes Internal BI and technical teams <strong>Power BI Embedded</strong> Capacity, billed hourly Yes No, cloud only Microsoft-centric products <strong>Sisense</strong> Quote only Yes Yes, Kubernetes Larger budgets wanting AI features <strong>Reveal BI</strong> Quote only, flat rate Yes Yes Teams that want an SDK-first build</p><h4>1. Yurbi — flat pricing built for multi-tenant embedding</h4><p>Yurbi is a self-hosted embedded analytics platform built specifically for software companies embedding analytics for their customers. Tenant isolation is enforced at the query level: security policies are injected into the SQL itself, so it applies to every report, dashboard, scheduled email, and export. Every plan includes per-tenant white-label branding with no vendor badge, a no-code report builder customers use themselves, scheduling, exports, and a full REST API.</p><p>Pricing is published and flat: $10,000 a year for 75 users up to $30,000 a year for unlimited users, with every feature in every plan. Embedding is two API calls — a sign-in that returns a session token, then an iframe. Yurbi runs on your own Windows, Linux, or Docker servers, including your own AWS, Azure, or GCP account, so it adds no outside data processor to your customers’ security reviews.</p><p><strong>Limitations:</strong> Yurbi embeds with iframe and API — there’s no JavaScript SDK yet. Native SAML/OIDC sign-in is in development. It’s self-hosted only, so you run the server.</p><h4>2. Apache Superset — powerful, free, and built for internal BI</h4><p>Superset is a strong open-source BI platform, and recent releases (6.0 in December 2025) brought a new design system, theming, and embedded SDK improvements. For a technical team building internal analytics, it’s excellent.</p><p>For customer-facing embedding, the gaps are architectural. Theming applies system-wide or per dashboard, not per tenant, and multi-tenant data isolation is a custom engineering project. It’s free to license, but your team owns the build and the maintenance.</p><h4>3. Power BI Embedded — strong if you’re all-in on Microsoft</h4><p>Power BI has excellent visuals and a large ecosystem. Embedded is billed by the hour for the capacity you provision (A and F SKUs) — roughly $740 a month for A1 at continuous use. Capacity doesn’t autoscale, so as customer usage grows, reports slow down until you move to a larger tier, and each step up roughly doubles the cost. It’s cloud-only.</p><h4>4. Sisense — capable, with AI features, at enterprise prices</h4><p>Sisense has genuine AI and machine-learning strengths and supports SaaS, dedicated cloud, or on-premise deployment through Kubernetes. It no longer publishes pricing — its Launch and Grow list prices were removed in June 2026 — and customer-reported embedded costs commonly land in the $60,000–$150,000+ per year range.</p><h4>5. Reveal BI — SDK-first embedding</h4><p>Reveal BI advertises a single flat rate with unlimited end users, available through a quote. It supports self-hosted deployment, including private cloud and air-gapped environments. The trade-off is the embedding model: Reveal is SDK-first, so your developers own a significant integration and ongoing maintenance effort.</p><h4>When to stay on Metabase</h4><p>Metabase is still the right answer for a lot of teams. Stay on it if:</p><ul><li>Your embeds are view-only and the “Powered by Metabase” banner is fine with you</li><li>Guest embeds with locked parameters cover your needs, so viewers never sign in</li><li>You have a modest number of signed-in customer users, and Pro pricing works at that size</li><li>Your team is comfortable owning the setup and the AGPL considerations</li></ul><p>If those stop being true, that’s the moment to compare.</p><h4>The option you might be weighing instead: building it yourself</h4><p>Some teams leave Metabase and decide to build their own dashboards — especially now that AI coding tools make the first version fast. The first dashboard is the cheap part. Tenant isolation, self-service report building, scheduling, permissions, and years of upkeep are still yours to own. We wrote about that trade-off in <a href="https://yurbi.com/blog/vibe-coded-dashboards-vs-embedded-analytics/">Vibe-Coded Dashboards vs. Embedded Analytics</a>, and the <a href="https://yurbi.com/calculator/">Build vs Buy calculator</a> puts numbers on your own situation.</p><p>For a deeper side-by-side, see <a href="https://yurbi.com/vs/metabase/">Yurbi vs Metabase</a>. If you’re an early-stage company, <a href="https://yurbi.com/solutions/startups/">see how startups embed Yurbi</a> — startup pricing is available, just ask.</p><h4>Frequently asked questions</h4><h4>Is Metabase embedding free?</h4><p>Guest embeds are free on Metabase’s open-source edition and every paid plan, but on the open-source edition and Starter they show a “Powered by Metabase” banner. Sign-in (SSO) embeds, full-app embedding, the React SDK, white-labeling, and row-level security require Metabase Pro or Enterprise.</p><h4>How much does Metabase cost for embedded analytics?</h4><p>Metabase Pro is $575 a month including 10 users, plus $12 per user per month, or $6,210 a year plus $130 per user on yearly billing. Every person who signs in to an SSO or full-app embed counts as a user, so at 1,000 customer users Pro costs roughly $135,000–$149,000 a year. Enterprise starts at $20,000 a year with custom pricing.</p><h4>Can I remove the “Powered by Metabase” banner?</h4><p>Yes, on Metabase Pro or Enterprise. Guest embeds on the open-source edition and the Starter plan show the banner.</p><h4>What is the best Metabase alternative for SaaS embedding?</h4><p>It depends on your needs. For multi-tenant, white-labeled embedding at a flat price, Yurbi is built for that use case and costs $10,000 to $30,000 a year with unlimited users at the top tier. Apache Superset suits technical teams building internal BI, Power BI Embedded suits Microsoft-centric products, and Sisense and Reveal BI are quote-based options.</p><h4>Is there a self-hosted alternative to Metabase for embedding?</h4><p>Yes. Yurbi is self-hosted on every plan and runs on Windows, Linux, or Docker, including in your own AWS, Azure, or GCP account. Apache Superset, Reveal BI, and Sisense also support self-hosted deployment, while Power BI Embedded is cloud-only.</p><h4>How hard is it to move from Metabase to Yurbi?</h4><p>Yurbi connects directly to the same databases Metabase does, read-only, so there’s no data migration. You build a semantic layer once, rebuild your reports and dashboards in Yurbi’s no-code builder, and swap the embed to a session token and iframe. Most teams reach production in 4 to 8 weeks, and Yurbi’s services team can do the work for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b3b3863203f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vibe-Coded Dashboards vs. Embedded Analytics: What AI Builds Overnight — and What It Leaves You]]></title>
            <link>https://medium.com/@5000fish/vibe-coded-dashboards-vs-embedded-analytics-what-ai-builds-overnight-and-what-it-leaves-you-5aad013b9dfb?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5aad013b9dfb</guid>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 01:01:10 GMT</pubDate>
            <atom:updated>2026-10-27T01:01:16.813Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Yurbi - White Label Embedded Dashboards and Reports" src="https://cdn-images-1.medium.com/max/600/0*2UKaL9g5yoj7Oh9e.jpg" /></figure><p>​<strong>Short answer:</strong> AI coding tools can build a working dashboard in an afternoon, and for internal reports or a prototype that may be all you need. Customer-facing reporting is different. Tenant isolation, self-service report building, scheduling, permissions, and years of upkeep are still code your team owns. For most software companies, the better split is to use AI to build the product faster and embed a reporting platform you don’t have to maintain.</p><p>A year ago, “should we build our own reporting?” meant estimating a quarter of engineering time. Today a developer can open an AI coding assistant, describe a dashboard, and have charts on screen before lunch. So it’s a fair question for any software company: why pay for an embedded analytics platform when your team can vibe-code the dashboards overnight?</p><p>The honest answer is that AI really has changed the first step. It just hasn’t changed the steps that come after it — and those are where the cost of customer-facing reporting has always lived.</p><h4>What AI genuinely gets you</h4><p>Credit where it’s due. With a modern coding assistant, a competent developer can produce in hours what used to take weeks:</p><ul><li>A chart page wired to a handful of queries against your database</li><li>A clean, modern UI that looks great in a demo</li><li>Filters, a date picker, maybe a CSV export</li></ul><p>If what you need is an internal page for your own team, or a prototype to test whether customers care about analytics at all, that may be all you need. Vibe-coding it is a perfectly reasonable choice.</p><h4>What your customers actually need — for years</h4><p>Customer-facing reporting inside a product you sell is a different job. The first dashboard is the easy part. What follows is a list that never really ends:</p><ul><li><strong>Tenant isolation.</strong> Every customer must see only their own data — in every chart, every export, every scheduled email, every edge case. A mistake here isn’t a bug; it’s a data breach and a very difficult conversation.</li><li><strong>Self-service.</strong> The first dashboard answers the questions you predicted. Customers will immediately ask different ones. Without a report builder they can use themselves, every new question becomes a ticket for your developers.</li><li><strong>Scheduling and delivery.</strong> “Email me this every Monday as a PDF” sounds small. It’s a scheduler, a renderer, a mail pipeline, retries, and per-recipient security.</li><li><strong>Permissions.</strong> Admins, viewers, report builders, per-customer roles, per-user overrides.</li><li><strong>White-labeling.</strong> Your branding — or each customer’s branding — on everything.</li><li><strong>Performance.</strong> Queries that are fine for one tenant in a demo behave very differently when dozens of customers load dashboards at once.</li><li><strong>Upkeep.</strong> Every schema change, every new customer, every framework upgrade touches the reporting code again.</li></ul><p>None of these are UI problems, which is exactly what AI makes cheap. They’re architecture and maintenance problems. AI-generated code is still code your team owns, tests, secures, and supports — and it can help you build the wrong version faster.</p><h4>The reporting tax doesn’t go away — it just starts sooner</h4><p>Teams that build customer-facing reporting in-house commonly describe the same pattern: it starts as one feature request and slowly becomes a standing chunk of every sprint. The work isn’t the first build; it’s the steady stream of new report requests, fixes, and changes that follows. Vibe-coding makes the first build faster, so teams reach that maintenance phase sooner — with code nobody designed from the start to handle multiple tenants.</p><p>For a startup or small software vendor, that matters even more. Your engineering hours are your scarcest resource, and every one spent on a report builder is one not spent on the product that makes you different.</p><h4>A simple way to decide</h4><p>Vibe-coding your dashboards is a reasonable choice when:</p><ul><li>The reporting is internal-only, for your own team</li><li>You’re prototyping to see whether customers want analytics at all</li><li>You have one customer, or every customer sees the same data</li><li>Analytics itself is the core product you sell</li></ul><p>Embedding a platform makes more sense when:</p><ul><li>Many customers each need to see only their own data</li><li>Customers expect to build and change their own reports</li><li>Your buyers send security questionnaires</li><li>You’d rather your engineers spent the next three years on your product, not your reporting layer</li></ul><h4>Use AI for your product. Let the reporting layer be someone else’s job.</h4><p>This isn’t an argument against AI coding tools — use them to build your core product faster. It’s an argument about where your team’s ownership should end. Yurbi is a self-hosted embedded analytics platform built for exactly this: tenant isolation enforced at the query level, a no-code report builder your customers use themselves, scheduling, exports, white-labeling, and an API, all running inside your own stack. Embedding takes two API calls: a sign-in that returns a session token, then an iframe.</p><p>If you want to put numbers on your own situation, the <a href="https://yurbi.com/calculator/">Build vs Buy calculator</a> uses your team’s headcount, salaries, and sprint time. For a side-by-side look, see <a href="https://yurbi.com/vs/building-it-yourself/">Yurbi vs building it yourself</a>. And if you’re an early-stage company, <a href="https://yurbi.com/solutions/startups/">see how startups embed Yurbi</a> — startup pricing is available, just ask.</p><h4>Frequently asked questions</h4><h4>Can AI coding tools build a customer-facing dashboard?</h4><p>Yes — an AI coding assistant can produce a working dashboard quickly. The harder part is everything a customer-facing product needs afterward: per-customer data isolation, self-service report building, scheduling, permissions, white-labeling, and ongoing maintenance as your schema and customer list change.</p><h4>Is vibe-coding reporting cheaper than buying an embedded analytics platform?</h4><p>The first build usually is. The total cost often isn’t, because the long-term expense of customer-facing reporting is maintenance and new report requests rather than the initial dashboard. AI-generated code is still code your team owns, tests, and supports.</p><h4>When does it make sense to vibe-code dashboards?</h4><p>When the reporting is internal-only, when you’re prototyping to see whether customers want analytics, when every user sees the same data, or when analytics is the core product you sell.</p><h4>What does an embedded analytics platform handle that a vibe-coded dashboard doesn’t?</h4><p>A platform like Yurbi provides tenant isolation enforced at the query level, a no-code report builder customers use themselves, scheduled delivery and exports, role-based permissions, white-labeling, and an API — maintained by the vendor instead of your team.</p><h4>How do startups add analytics to their product without a BI sprint?</h4><p>By embedding a platform rather than building one. Yurbi installs with one Docker command and embeds with two API calls, so customers get self-service reporting while a small team stays focused on the core product. Startup pricing is available on request.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5aad013b9dfb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Fabric + DashboardFox: Dashboards Without a Power BI License for Every Viewer]]></title>
            <link>https://medium.com/@5000fish/microsoft-fabric-dashboardfox-dashboards-without-a-power-bi-license-for-every-viewer-d6b179e85ae9?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6b179e85ae9</guid>
            <category><![CDATA[microsoft-power-bi]]></category>
            <category><![CDATA[data-repository]]></category>
            <category><![CDATA[fabric]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 20:55:11 GMT</pubDate>
            <atom:updated>2026-10-25T20:55:39.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="DashboardFox - Alternative to Power BI" src="https://cdn-images-1.medium.com/max/600/0*6Oh_STgyzHBsB6Vv.jpg" /></figure><p><strong>Short answer:</strong> If your data already lives in Microsoft Fabric, you don’t have to move it or give up Power BI to deliver dashboards more cheaply. DashboardFox connects directly to Fabric SQL databases, so customers, partners and occasional internal viewers can get secure, branded dashboards without a Power BI license each. Your analysts keep Power BI, your data stays in Fabric, and you stop paying per viewer on capacities below F64.</p><h4>The per-viewer problem below F64</h4><p>Fabric made Microsoft’s data platform more capable, but it didn’t change the basic Power BI licensing rule. On every Fabric capacity smaller than F64 (F2 through F32), <strong>each person who views a Power BI report needs a Pro license ($14/user/month) or Premium Per User ($24/user/month)</strong>. Only at F64 can viewers with a free license open reports. F64 costs about $5,000/month with a one-year reservation, or about $8,400/month pay-as-you-go.</p><p>That leaves a wide gap. Most mid-sized organizations run Fabric on F2 to F16 because that’s what their data workloads need. But the moment they share dashboards with a few dozen customers, franchisees, board members or field staff, the Pro licenses add up. External viewers make it harder still: each one typically needs a Microsoft Entra guest account in your tenant, which brings onboarding friction and often an IT or compliance review.</p><p>Microsoft’s other route, Power BI Embedded (A SKUs, from about $735/month for A1), avoids per-viewer licenses, but you have to build the portal, authentication and embedding yourself. That’s a development project, not a setting.</p><p>Many teams are reassessing this now for another reason. Microsoft is retiring Power BI Premium P SKUs. When each customer’s agreement ends, they move to Fabric F capacity, and existing Premium discounts don’t carry over automatically. If your renewal is coming up, it’s a good moment to look at what you’re paying for viewers. For the full picture, see our <a href="https://app.storychief.io/blog/everything-you-need-to-know-about-microsoft-power-bi-pricing/">Power BI pricing breakdown</a>.</p><h4>The cost comparison</h4><p>Here’s what it costs each month to share dashboards from a Fabric-based setup with viewers who don’t build reports. Analyst licenses are the same in every option, so they’re left out.</p><p><strong>ViewersF2 + Power BI Pro per viewerF64, free viewersF2 + DashboardFox</strong> 25$506$5,003$405 (Growth) 100$1,556$5,003$655 (Scale) 500$7,156$5,003$1,655 (Enterprise)</p><p><em>Assumptions: F2 and F64 at Microsoft’s one-year reservation rates (about $156 and $5,003/month, US list price); Power BI Pro at $14/user/month; DashboardFox at monthly list prices (Growth $249 for 30 active users, Scale $499 for 100, Enterprise Dedicated Cloud from $1,499/month billed annually). Your Microsoft pricing depends on your agreement and region.</em></p><p>Two things make the DashboardFox column cheaper than it looks on paper:</p><ul><li><strong>You pay for active users, not accounts.</strong> A monthly active user is anyone who logs in that month. Create accounts for every customer contact; the ones who don’t log in don’t count.</li><li><strong>Email recipients are free.</strong> Many viewers only need a scheduled PDF or Excel report. Recipients who never log in don’t count as active users on any plan.</li></ul><p>One caveat: F2 is Fabric’s smallest capacity. DashboardFox queries run against your Fabric capacity (more on that below), so heavy dashboard traffic may mean a larger F SKU. Size the capacity to your query load, not your viewer count.</p><h4>How DashboardFox connects to Fabric</h4><p>Fabric SQL databases accept only Microsoft Entra ID authentication; SQL logins are disabled. DashboardFox connects using the SQL Server driver it already includes and an Entra service principal (an app registration with read access to the database). It’s confirmed working on a live Fabric tenant, and setup takes a few minutes for someone with Azure admin access.</p><p>What that means in practice:</p><ul><li><strong>Your data stays in Fabric.</strong> DashboardFox runs live queries against the database. Nothing is copied into DashboardFox, and results are discarded after each dashboard renders.</li><li><strong>One identity, read-only.</strong> The service principal needs only read access, and you control it in Entra like any other app registration.</li><li><strong>No per-viewer Microsoft accounts.</strong> Your customers sign in to DashboardFox under your brand, not to your Microsoft tenant.</li></ul><p>Fabric Warehouses and Lakehouse SQL analytics endpoints use the same login method and connection protocol. If that’s where your data lives, <a href="https://app.storychief.io/contact/?topic=engineer">talk to an engineer</a> and we’ll confirm the setup with you. See all supported sources on our <a href="https://app.storychief.io/integrations/">integrations page</a>.</p><h4>Delivering dashboards to customers</h4><p>The per-viewer savings matter most when the viewers are outside your organization, which is also where Power BI is weakest out of the box:</p><ul><li><strong>White-label on every plan.</strong> Your logo, colors, custom domain and branded login page. Customers never see DashboardFox or Microsoft branding.</li><li><strong>Row-level security on every plan.</strong> Data Tags filter every query on the server by customer, location or any field you choose. Build one dashboard and each customer sees only their own rows, including in scheduled emails and exports. See our <a href="https://app.storychief.io/guides/row-level-security-guide/">row-level security guide</a>.</li><li><strong>Self-service without risk.</strong> Customers can filter, drill down and build their own reports inside the security you’ve set. They can’t remove the filter.</li><li><strong>Security reviews.</strong> DashboardFox has passed full customer security reviews, and our <a href="https://app.storychief.io/security/review-kit/">security review kit</a> is public. A HIPAA BAA is available on any plan with the Compliance Tier.</li></ul><h4>What still runs on Fabric</h4><p>Adding DashboardFox doesn’t take Fabric out of the picture, and we’d rather you know the trade-offs up front:</p><ul><li><strong>Queries use Fabric capacity.</strong> Every dashboard query is a T-SQL query against your Fabric database, and Fabric bills it in capacity units like any other workload. Monitor it in the Fabric Capacity Metrics app.</li><li><strong>A paused capacity means no dashboards.</strong> If you pause your F SKU overnight to save money, DashboardFox dashboards that query Fabric won’t load until it resumes.</li><li><strong>Fabric stays your data platform.</strong> Pipelines, data modeling, governance and storage all remain in Fabric. DashboardFox is the delivery layer, not a replacement for any of that.</li><li><strong>Check your licensing.</strong> Microsoft’s documentation supports service principal access to Fabric SQL databases. If you have questions about how your Microsoft agreement treats data shown through a third-party tool, confirm with your Microsoft licensing contact.</li></ul><h4>Where Power BI stays the better tool</h4><p>This isn’t a case for ripping out Power BI. Keep it for:</p><ul><li><strong>Analysts who live in Power BI Desktop.</strong> DAX, complex semantic models and Power Query are Power BI’s strengths. DashboardFox is intentionally simpler.</li><li><strong>Copilot and Microsoft AI features.</strong> If you’re paying for Fabric capacity partly for Copilot, those features stay in Power BI.</li><li><strong>Deep Microsoft 365 integration.</strong> Reports in Teams and SharePoint for internal users who already have Pro licenses.</li><li><strong>Associative cross-filtering.</strong> Clicking one chart to filter every other visual on the page is a Power BI strength. In DashboardFox, filters sit at the top of the dashboard and clicks drill into detail.</li></ul><p>The common pattern is both tools: Power BI for the internal analysts who already have licenses, DashboardFox for customers, partners and the long tail of occasional viewers. For a full side-by-side, see <a href="https://app.storychief.io/vs-power-bi/">DashboardFox vs Power BI</a>. If you’re weighing a full move away from Microsoft, see our <a href="https://app.storychief.io/blog/best-alternatives-to-microsoft-power-bi/">Power BI alternatives</a>.</p><h4>The bottom line</h4><p>Fabric is a strong data platform, and nothing here asks you to leave it. But below F64, Power BI charges for every viewer, and customer-facing delivery needs guest accounts or a development project. If your viewers mostly need to see their own numbers, branded and secure, a dashboard layer that connects to Fabric and charges by active user can cost a fraction of the per-viewer route. You can try it on your own Fabric data during a free trial.</p><h4>Frequently asked questions</h4><h4>Can DashboardFox connect to Microsoft Fabric?</h4><p>Yes. DashboardFox connects to Fabric SQL databases using its built-in SQL Server driver and a Microsoft Entra service principal, and this is confirmed working on a live Fabric tenant. Fabric Warehouses and Lakehouse SQL analytics endpoints use the same authentication and protocol; contact us to confirm your setup.</p><h4>Do Power BI report viewers need a Pro license on Fabric?</h4><p>On Fabric capacities below F64 (F2 through F32), yes. Each viewer of Power BI content needs a Pro or Premium Per User license. From F64 up, users with a free license can view reports. Report creators need Pro or PPU on every capacity size.</p><h4>Do DashboardFox viewers need a Microsoft license?</h4><p>No Power BI license is needed to view DashboardFox dashboards, which DashboardFox serves itself and bills by monthly active user. DashboardFox reads data from Fabric through a single service principal. If you have questions about how your Microsoft agreement treats this, confirm with your Microsoft licensing contact.</p><h4>Do DashboardFox queries use Fabric capacity?</h4><p>Yes. Queries against a Fabric database consume capacity units like any other T-SQL workload, and dashboards can’t load while the capacity is paused. Size your capacity to query load and monitor it with the Fabric Capacity Metrics app.</p><h4>Do we have to stop using Power BI?</h4><p>No. Most teams that add DashboardFox keep Power BI for internal analysts and use DashboardFox for customer-facing and occasional viewers, both reading from the same Fabric data.</p><p><em>Microsoft pricing reflects US list rates published for 2026 and can vary by agreement, region and currency. DashboardFox is our product.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6b179e85ae9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Domo Acquired by Progress: 5 Domo Alternatives (2026)]]></title>
            <link>https://medium.com/@5000fish/domo-acquired-by-progress-5-domo-alternatives-2026-8dc739af9d1e?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8dc739af9d1e</guid>
            <category><![CDATA[zoho-analytics]]></category>
            <category><![CDATA[tableau]]></category>
            <category><![CDATA[microsoft-power-bi]]></category>
            <category><![CDATA[domo]]></category>
            <category><![CDATA[qlik]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 20:35:57 GMT</pubDate>
            <atom:updated>2026-10-25T20:36:08.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="DashboardFox - Alternative to Domo" src="https://cdn-images-1.medium.com/max/600/0*IM1LXcp9rZbACFI7.jpg" /></figure><p><strong>Short answer:</strong> Progress Software bought substantially all of Domo’s business for $400 million, and the deal closed on September 22, 2026. Domo is not shutting down, and your contract carries over to Progress. Nothing has been announced about pricing or the roadmap yet. Your renewal is when you’ll find out what changed. If you mostly use Domo for dashboards on data that already lives in a database or warehouse, you have cheaper options with published pricing, including DashboardFox from $99/month. If you depend on Domo’s 1,000+ connectors and Magic ETL, you’ll need a replacement for the data pipeline as well as the dashboards, so plan the move carefully.</p><h4>What happened to Domo</h4><p>Domo spent most of 2026 under financial pressure. Here’s the sequence:</p><p><strong>DateWhat happened</strong> June 2026Domo said it was exploring strategic alternatives and issued a going-concern warning. July 22, 2026Progress Software announced it would acquire Domo’s AI and data platform business for $400 million in cash. The deal was an asset purchase, not a merger. September 22, 2026The deal closed. Progress took over the platform, its intellectual property, the customer contracts, and the employees. Domo will become part of Progress’s existing data platform offerings. After closingThe listed company that sold the business kept its cash and tax assets and changed its name and ticker (reported as Huckleberry.ai). Founder Josh James stayed with that company, not with the product.</p><p>Progress says Domo brings more than 2,400 business customers. Its stated plan is to pair Domo with the Progress Data Platform to help customers “connect, govern, and activate enterprise data for AI.” It has not published a Domo roadmap, a pricing change, or a rebrand.</p><p>If this sounds familiar, it’s the same pattern we covered when <a href="https://app.storychief.io/blog/mode-analytics-was-acquired-by-thoughtspot-best-mode-alternatives-in-2026/">ThoughtSpot absorbed Mode</a> and when <a href="https://app.storychief.io/blog/datapine-was-acquired-the-best-datapine-alternatives-in-2026/">Qlik acquired Datapine</a>. The product keeps running, and the changes arrive later.</p><h4>What changes for Domo customers, and what doesn’t</h4><p><strong>What doesn’t change right away:</strong> your dashboards, data, users and login. Progress has said it will continue serving Domo customers and supporting the platform. The signed terms of your agreement still apply.</p><p><strong>What has already changed:</strong> the company on the other side of your contract. Because this was an asset purchase, customer agreements were assigned to Progress. Your written terms carry over, but verbal promises, roadmap commitments and “we’ll take care of you at renewal” conversations with your old account team generally don’t.</p><p><strong>What could change at renewal:</strong> Domo already used a credit-based consumption model, where data ingestion, storage, ETL runs and AI features all draw from one pool of credits. That gives a new owner several quiet ways to change what you pay without touching the list price:</p><ul><li>How many credits a given activity consumes</li><li>Which features draw from which credit pool</li><li>Rate cards for new workloads, especially AI</li><li>Minimum contract size and term length at renewal</li><li>Packaging, if Domo is folded into a larger Progress bundle</li></ul><p>None of these has been announced. But these are the levers that typically move after an acquisition, and with Domo they’re already built into how billing works. For more on how the credit model works today, see <a href="https://app.storychief.io/blog/how-much-does-domo-cost/">How Much Does Domo Cost?</a></p><h4>Before your Domo renewal: a 6-step checklist</h4><p>Whether you stay or go, do these before you sign anything new:</p><ol><li><strong>Pull your signed agreement and order forms.</strong> Check the assignment clause, any renewal price cap, the auto-renewal notice window, and what happens to your data when the contract ends.</li><li><strong>Run an export test now.</strong> Export your most important DataSets and note what doesn’t come out cleanly. Magic ETL dataflows, Beast Mode calculations and card logic don’t move to another tool as files. Knowing what it costs to leave is your best negotiating leverage.</li><li><strong>Measure your credit consumption.</strong> Get three to six months of credit usage by activity. If refreshes and ETL runs drive most of it, that’s where any repricing will hit.</li><li><strong>Keep the term short.</strong> Unless Progress puts a price cap, frozen credit definitions and a roadmap commitment in writing, a 12-month renewal keeps your options open.</li><li><strong>Ask for a change-of-control or material-change exit.</strong> If the product is renamed, repackaged or merged into another platform, you want the right to leave without penalty.</li><li><strong>List what you actually use.</strong> Most teams use a fraction of an all-in-one platform. If the list is “dashboards, scheduled reports, and per-user data filtering on our own database,” you don’t need to replace all of Domo.</li></ol><h4>What to look for in a Domo replacement</h4><p>The right alternative depends on which half of Domo you rely on.</p><p><strong>If Domo is your data pipeline</strong> (pulling from dozens of SaaS apps through pre-built connectors and transforming the data with Magic ETL), you need a replacement for that layer first. That usually means a data integration tool feeding a warehouse, or a platform that bundles both. Expect a real project.</p><p><strong>If Domo is your dashboard layer</strong> (your data already lives in SQL Server, PostgreSQL, Snowflake, BigQuery or similar, and Domo mostly visualizes it), the move is much simpler. You need a tool that connects to that database, rebuilds the dashboards, and handles per-user data security.</p><p>Either way, weigh these:</p><ul><li><strong>Pricing you can see before a sales call.</strong> If unpredictable credits are part of why you’re looking, don’t swap one opaque model for another.</li><li><strong>Where your data lives.</strong> Domo ingests a copy of your data into its cloud. Some alternatives query your database live instead, which simplifies security reviews.</li><li><strong>Row-level security.</strong> If you use Domo’s Personalized Data Permissions (PDP), confirm the replacement enforces per-user filtering on the server, and find out which plan it’s on.</li><li><strong>Who’s likely to be acquired next.</strong> Vendor stability is a fair question to ask after this year.</li></ul><h4>Quick comparison</h4><p><strong>ToolPublished pricingBilling modelBuilt-in ETL / connectorsBest fit for Domo users who…</strong> DashboardFoxYes, $99–$499/month; Enterprise from $1,499/monthFlat tiers by monthly active usersNo ETL; live queries to 30+ databases, plus REST API and file sourcesUse Domo for dashboards and client or departmental reporting on their own database Power BIYes, $14/user/month (Pro)Per seat, plus Fabric capacity for advanced featuresYes, via Power Query and FabricAlready run on Microsoft 365 and Azure Zoho AnalyticsYes, by planPer plan, capped by users and data rowsYes, with Zoho citing 500+ data sourcesWant an all-in-one cloud tool with lots of connectors at a lower price TableauYes, $15–$75/user/month (Standard)Per seat by role, annual onlyTableau Prep with Creator licensesNeed best-in-class visual analysis Qlik Cloud AnalyticsYes, from $300/month (Starter)Capacity-based tiers, annualYes, with Qlik Talend Cloud sold separatelyNeed enterprise data integration plus associative analysis</p><p>Competitor pricing is based on each vendor’s published pricing pages as of October 2026 and changes often. Verify before you decide.</p><h4>1. DashboardFox: for Domo users who mainly need dashboards on their own database</h4><p>DashboardFox is our product, so weigh this accordingly. It’s a fit if your data already sits in a database or warehouse and what you need from Domo is dashboards, scheduled reports and secure sharing.</p><p><strong>Where it’s strong for Domo users:</strong></p><ul><li><strong>Published, flat pricing.</strong> Starter $99/month, Growth $249/month, Scale $499/month, billed by monthly active users rather than credits or seats, with month-to-month billing available. Enterprise Dedicated Cloud starts at $1,499/month billed annually. See <a href="https://app.storychief.io/pricing/">pricing</a>.</li><li><strong>Your data stays put.</strong> Database connections are live queries, so nothing is copied into our platform. That’s a different security posture from ingesting everything into a vendor’s cloud.</li><li><strong>Row-level security on every plan.</strong> Data Tags filter every query by user, which covers what most teams use Domo’s PDP for.</li><li><strong>White-label on every plan.</strong> Custom domains and full branding for client-facing dashboards.</li><li><strong>Self-hosted option.</strong> A one-time license from $4,995 if you want off vendor clouds entirely. Domo is cloud-only.</li><li><strong>Healthcare.</strong> A HIPAA BAA is available on any plan with the Compliance Tier.</li></ul><p><strong>Where it falls short of Domo:</strong> there’s no built-in ETL and no library of pre-built SaaS connectors. You connect to databases, REST APIs and files. There’s no native mobile app (ours is being rebuilt), and no AI features yet. If Magic ETL and Domo’s connectors do the heavy lifting for you, pair DashboardFox with a pipeline tool and a warehouse, or look at the all-in-one options below.</p><p>For a full side-by-side, see <a href="https://app.storychief.io/vs-domo/">DashboardFox vs Domo</a>.</p><h4>2. Power BI: for Microsoft-centric organizations</h4><p>Power BI is the lowest entry cost for organizations already on Microsoft 365. Pro is $14 per user per month, Power Query covers lightweight data prep, and Microsoft Fabric provides a full data platform (pipelines, warehousing, notebooks) that can replace much of what Domo did.</p><p><strong>Trade-offs:</strong> pricing is per seat, so every viewer needs a license unless you buy Fabric capacity. Copilot and other advanced features require a paid Fabric capacity. Power BI Desktop is Windows-only. White-label delivery requires Power BI Embedded and developer work. Moving from Domo’s credits to Microsoft’s capacity model trades one kind of complexity for another.</p><h4>3. Zoho Analytics: the closest all-in-one at a lower price</h4><p>If you liked Domo’s “connect everything” approach and want to keep it, Zoho Analytics is the most similar model at a far lower price. It offers pre-built connectors for business apps (Zoho cites more than 500 data sources), drag-and-drop building, an AI assistant (Zia), and cloud or on-premises deployment. Pricing is published by plan.</p><p><strong>Trade-offs:</strong> every plan caps both users and data rows, so a growing dataset can push you up a tier even if your team doesn’t grow. It works best inside the Zoho ecosystem. White-label setup goes through Zoho’s team rather than being self-service.</p><h4>4. Tableau: when visual analysis is the priority</h4><p>Tableau has the strongest visualization and exploration of any tool on this list, plus a large community and training ecosystem. Tableau Prep, included with Creator licenses, handles data preparation.</p><p><strong>Trade-offs:</strong> pricing is per seat by role ($75 Creator, $42 Explorer, $15 Viewer on Standard, higher on Enterprise), and all plans require an annual commitment. Centrally managed row-level security requires Enterprise. Tableau isn’t a lower-cost destination. Teams usually choose it for analytical depth, not to save money.</p><h4>5. Qlik Cloud Analytics: enterprise data integration plus analytics</h4><p>Qlik’s associative engine lets users explore relationships across the whole dataset, and Qlik Talend Cloud provides enterprise-grade data integration. Together they’re the closest match to Domo’s breadth for larger organizations. Qlik Cloud Analytics publishes its tiers: Starter at $300/month for 10 users, Standard at $825/month and Premium at $2,750/month, all billed annually.</p><p><strong>Trade-offs:</strong> pricing is based on data capacity, so cost grows with data volume, and Talend is a separate purchase. There’s a learning curve, and Qlik has made a string of acquisitions of its own. If vendor change is what you’re trying to get away from, factor that in.</p><h4>Migrating off Domo: what actually moves</h4><p>Most of the work in a Domo migration isn’t the dashboards. It’s everything Domo did before the data reached them.</p><ul><li><strong>Magic ETL and dataflows:</strong> these don’t export to other tools. Rebuild the logic as SQL views, stored procedures or warehouse models. Start with the dataflows that feed your most-used dashboards.</li><li><strong>Connectors:</strong> list every source Domo pulls from. Sources that already sit in a database connect directly. SaaS sources need either a data integration tool or a BI tool with native connectors.</li><li><strong>Beast Mode calculations:</strong> recreate these as calculated fields or in a semantic layer, so every report uses the same definitions.</li><li><strong>PDP policies:</strong> map each policy to the new tool’s row-level security, and test with real user accounts before go-live.</li><li><strong>Cards and pages:</strong> rebuild the 20% of dashboards that get 80% of the views first. Retire the rest.</li><li><strong>Run both tools side by side</strong> for a reporting cycle or two, and compare the numbers before you cancel.</li></ul><p>If you’re moving to DashboardFox, we’ll help you rebuild your top dashboards, and you’ll talk directly with the engineers who build the product. <a href="https://app.storychief.io/contact/?topic=engineer">Talk to an engineer</a> about your Domo setup.</p><h4>The bottom line</h4><p>Domo isn’t going anywhere this month, and there’s no reason to panic. But your contract is now with a different company, and its plans for pricing and packaging are still unknown. Use the time before your renewal to run an export test, measure what you actually use, and get quotes. If your needs come down to dashboards, reports and secure sharing on data you already own, the alternatives cost a fraction of a typical Domo contract and publish their prices.</p><h4>Frequently asked questions</h4><h4>Is Domo shutting down?</h4><p>No. Progress Software bought Domo’s platform business in September 2026 and has said it will continue serving Domo customers and supporting the platform. The product keeps running, and existing contracts carry over to Progress.</p><h4>Who owns Domo now?</h4><p>Progress Software, a publicly traded infrastructure software company, owns the Domo platform, its intellectual property, customer contracts and employees. The deal closed on September 22, 2026. The original listed company kept its cash and tax assets and changed its name.</p><h4>Will Domo pricing change after the Progress acquisition?</h4><p>Progress hasn’t announced any pricing changes. Because Domo bills through consumption credits, changes are most likely to show up at renewal: credit definitions, rate cards for new workloads, minimum contract sizes, or new bundles. Get any commitments in writing before you renew.</p><h4>Can I export my data from Domo?</h4><p>Yes. DataSets can be exported, for example to CSV or Excel, or through Domo’s APIs. Magic ETL dataflows, Beast Mode calculations and card designs don’t transfer to other tools and need to be rebuilt. Run an export test before your renewal so you know the real effort involved.</p><h4>What’s the best Domo alternative for small and mid-sized teams?</h4><p>It depends on where your data lives. If it’s already in a database or warehouse, a dashboard-focused tool with published pricing, such as DashboardFox from $99/month, covers the reporting side for far less. If you depend on many SaaS connectors, Zoho Analytics is the closest all-in-one at a lower price. Microsoft-centric teams usually land on Power BI.</p><p><em>Acquisition details are from Progress Software’s announcements of July 22 and September 22, 2026, and contemporary reporting. Competitor pricing was checked against vendors’ published pricing pages in October 2026 and can change. DashboardFox is our product.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dc739af9d1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[​White-Label Reporting With PHI: How Healthcare Software and Services Companies Give Customers…]]></title>
            <link>https://medium.com/@5000fish/white-label-reporting-with-phi-how-healthcare-software-and-services-companies-give-customers-7e7eb0e09ccd?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e7eb0e09ccd</guid>
            <category><![CDATA[data-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hipaa]]></category>
            <category><![CDATA[phi]]></category>
            <category><![CDATA[use-cases]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 16:55:32 GMT</pubDate>
            <atom:updated>2026-09-29T16:56:22.899Z</atom:updated>
            <content:encoded><![CDATA[<h3>​White-Label Reporting With PHI: How Healthcare Software and Services Companies Give Customers Self-Service Analytics Safely</h3><figure><img alt="DashboardFox - White-Label Reporting" src="https://cdn-images-1.medium.com/max/600/0*jMDQ0-xPsvZ2NcOT.jpg" /></figure><p><strong>Short answer:</strong> If your company holds protected health information on behalf of health plans, provider groups, or other clients, you can give those clients self-service dashboards and ad-hoc reports under your own brand, as long as four things are true. Every query is filtered by tenant at the server, not in the report. Each client sees a curated data model, not raw tables. The features that would let a client user see behind the curtain are switched off. And the platform runs under a Business Associate Agreement on infrastructure that serves only you. This post walks through each, using a real deployment that replaced pre-built spreadsheet exports for more than 400 client organizations.</p><h4>The problem: spreadsheets out, questions in</h4><p>Most healthcare data services companies start the same way. Clients need to see the results of the work you do on their data, so someone builds a nightly job that produces a set of spreadsheets per client and posts them to a portal. It works. Then the questions start: can we get this by month, can we filter to one facility, can we add the field your analysts use, can we see it as a chart. Each request becomes a ticket, a developer change, and a new file in the nightly job. The portal fills up with variations, the clients keep asking, and a growing share of your engineering time goes to reporting instead of the product.</p><p>The obvious next step is dashboards. The obvious tool is whichever BI product your team already knows. And that is where the project usually stalls, because general-purpose BI tools were built for analysts inside one company, not for hundreds of outside organizations that must never see each other’s data. The per-seat pricing doesn’t fit thousands of occasional client users. The branding is the vendor’s. Row-level security exists but is configured per report and per user. And the vendor may not sign a Business Associate Agreement, or only at a price that ends the conversation.</p><h4>A worked example</h4><p>The deployment below is a DashboardFox customer we can describe but not name: a healthcare data services company that analyzes clinical and claims data on behalf of health plans and provider organizations, with more than 400 client organizations, many of them heavy users of the reporting.</p><p>Their previous solution generated pre-built spreadsheets that clients downloaded from a portal. It answered the standard questions and nothing else. They were evaluating Power BI for dashboards when they reviewed DashboardFox, and they chose it for three reasons that had nothing to do with charts: it passed their security review, it could be deployed on a server dedicated to them under a signed BAA, and it let their clients build their own reports without exposing the underlying data model.</p><p>Today each client logs into a portal on the company’s own domain, with the company’s logo, colors, and terminology. They see dashboards, which the spreadsheet portal never had. They open a curated data model and build their own reports with a drag-and-drop composer, schedule them by email, or export them. And no client can see another client’s rows, because the filter is applied by the server to every query based on who is logged in.</p><h4>The four things that make it safe</h4><h4>1. Tenant isolation at the query level</h4><p>The mechanism that makes multi-client reporting work is row-level security tied to a tenant identifier. In DashboardFox this is done with data tags: each user carries a profile tag such as a client ID, and a data security policy tells the server to append the matching condition to every query that user runs against tables carrying that tag. The user never sees the filter, cannot remove it, and cannot reach the underlying dataset through another route. A client who builds a brand-new ad-hoc report from scratch still gets only their own rows, because the constraint lives below the report.</p><p>This is different from the approach several tools take, where each dashboard is filtered per user or per copy, and the vendor’s own documentation warns not to rely on that filtering for security. For PHI across hundreds of tenants, the filter has to be a server-side policy, or it is not a control.</p><h4>2. A curated data model instead of raw tables</h4><p>Self-service does not mean giving clients your schema. DashboardFox sits a semantic layer, called an App, between the database and the report builder. You decide which tables and views are in it, how they join, which fields appear and under what names, and which fields are hidden. A client building a report in the Composer picks from “Member,” “Visit Date,” “Facility,” and “Diagnosis Category,” not from column names, and never from tables you did not expose. The App is where minimum-necessary gets enforced: a client can explore freely inside a model that contains only what they are entitled to see.</p><p>Field-level security adds a second layer. Within an exposed table, individual fields can be hidden from particular groups, so an identifier that internal analysts need can be invisible to client users.</p><h4>3. Hiding what clients should not see</h4><p>White-label is usually described as logos and colors, and it is that: custom domain, logo, palette, login page, email templates, and a phrase manager that renames product terms to the ones your industry uses. But the part that matters for client-facing PHI reporting is what white-label lets you remove. In this deployment, the client-facing branding policy hides:</p><ul><li>The vendor’s support links and help content, so clients contact you, not us</li><li>The ability to view the SQL behind a report, which would reveal table and column names</li><li>Report library metadata such as author, creation date, and modification time, which can leak internal names and workflow</li><li>Administrative and configuration features that have no place in a client’s hands</li></ul><p>Branding policies apply per group, so internal analysts and client users can share one platform with different experiences. The default should be to expose the smallest feature set that lets a client answer their own questions, and to add features only when a client asks for one you are comfortable with.</p><h4>4. Dedicated infrastructure under a BAA</h4><p>Everything above is application design. The fourth requirement is where the application runs. This customer’s environment is a dedicated server and a dedicated PostgreSQL database that serve their organization alone, provisioned by us, in a US region that is a HIPAA/HITECH-attested facility. They evaluated on-premise first and chose the dedicated cloud because it gave the same single-tenant isolation without waiting for internal server provisioning. We operate it as their business associate under a signed BAA, with BAAs in place with our own hosting and backup providers before any PHI was provisioned, database audit logs retained for six years, and the arrangement backed by a standalone $5 million cyber liability policy.</p><p>The BAA question deserves a direct answer from any vendor you evaluate: will they sign one, on which plan, and is your data on shared or dedicated infrastructure? Our comparison of <a href="https://dashboardfox.com/blog/which-bi-tools-are-hipaa-compliant/">which BI tools sign a BAA</a> covers the major vendors.</p><h4>What changed for the business</h4><p><strong>BeforeAfter</strong> Pre-built spreadsheets generated per client and downloaded from a portalClients log into a branded portal and run reports on demand Every new question became a development ticketClients build ad-hoc reports themselves from a curated model No dashboards or visualizationsDashboards and charts, which the company had been evaluating Power BI to provide Delivery was a file; freshness was whenever the job ranLive queries against the source data, with scheduled email delivery for clients who still want a file Isolation was “each client gets their own files”Isolation is a server-enforced policy on every query, by tenant ID Per-seat BI pricing would have charged for every client userFlat pricing for a dedicated environment, unlimited active users within capacity</p><h4>A checklist for your own deployment</h4><p><strong>DecisionWhat to settle before you build</strong> Tenant keyWhich field identifies a client in every table you will expose? It must exist, be reliable, and be stamped on the user’s profile. Data model scopeWhich tables, views, joins, and fields belong in the client-facing App? Start small; add on request. Internal vs. client groupsOne group per client, plus internal groups with wider access and a different branding policy. Feature exposureWhich Composer and library features clients may use. Hide SQL view, metadata, admin, and vendor support links by default. DeliveryWhich clients want scheduled email or export, and through whose mail server. Use your own SMTP so PHI never transits shared mail infrastructure. EnvironmentDedicated server and database, BAA executed, sub-processor BAAs confirmed, audit retention set to six years. OnboardingA repeatable script: create group, assign profile tag, assign App role, apply branding policy, test with a client-role account before go-live.</p><h4>How DashboardFox is built for this</h4><p>DashboardFox is our product, and this use case is one it was designed around. Row-level security with data tags, field-level security, the App semantic layer, the Composer, per-group branding policies, custom domains, phrase management, and scheduled delivery are included on every plan. Client-facing deployments with PHI run on Enterprise Dedicated Cloud, from $1,499 per month billed annually, where we sign a Business Associate Agreement with the Compliance Tier. Self-hosted is available for organizations that must keep everything in-house, in which case no BAA from us is needed because we never have access to the data.</p><p><a href="https://dashboardfox.com/deployment/">Compare deployment options →</a> · <a href="https://dashboardfox.com/blog/hipaa-compliant-bi-software/">What to require from a cloud BI vendor for PHI →</a> · <a href="https://dashboardfox.com/security/review-kit/">Security review kit →</a> · <a href="https://dashboardfox.com/contact/?topic=engineer">Talk to an engineer about client reporting →</a></p><h4>Frequently asked questions</h4><h4>Can clients build their own reports without seeing other clients’ data?</h4><p>Yes, if row-level security is a server-side policy tied to a tenant identifier on the user’s profile. Every query the client runs, including brand-new ad-hoc reports, carries the filter, and nothing in the report builder can remove it.</p><h4>Do we have to copy PHI into the BI tool?</h4><p>Not with DashboardFox. It queries your database in place and stores only report definitions and metadata. Your PHI stays where it already is, under controls you already audit.</p><h4>What should we hide from client users?</h4><p>At minimum: the vendor’s support and help links, the ability to view a report’s SQL, report library metadata such as author and timestamps, and any administrative features. Expose the smallest feature set that lets a client answer their own questions.</p><h4>Is a dedicated environment required for client-facing PHI reporting?</h4><p>HIPAA does not require it, but it simplifies the risk analysis and most security reviewers prefer it. DashboardFox signs a BAA only on its dedicated Enterprise tier for that reason.</p><h4>How is this priced compared to per-seat BI tools?</h4><p>Per-seat tools charge for every client user who logs in, which makes hundreds of client organizations expensive fast. DashboardFox Enterprise Dedicated Cloud is a flat annual fee for a dedicated server, with unlimited monthly active users within server capacity and fair use.</p><p><em>The deployment described is a real DashboardFox customer that has asked not to be named. Details have been generalized; nothing in this post identifies the organization or its clients. This post is not legal advice.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e7eb0e09ccd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[​The BI Vendor Security Questionnaire: 43 Questions to Ask, and What Good Answers Look Like]]></title>
            <link>https://medium.com/@5000fish/the-bi-vendor-security-questionnaire-43-questions-to-ask-and-what-good-answers-look-like-9d44dfbaa7de?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d44dfbaa7de</guid>
            <category><![CDATA[buying-decisions]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[data-security]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 16:41:47 GMT</pubDate>
            <atom:updated>2026-09-29T16:41:57.565Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="DashboardFox - Cloud and On-Premise BI Software" src="https://cdn-images-1.medium.com/max/600/0*TP49Ah223hrzVtN-.jpg" /></figure><p><strong>Short answer:</strong> A BI tool is different from most SaaS. It holds credentials to your databases, runs queries against your most sensitive tables, and shows the results to people across your organization and sometimes outside it. So the standard SaaS questionnaire misses the questions that matter most: how the tool connects to your data, whether it copies it, how it decides who sees which rows, and where the audit trail lives. Below are 43 questions grouped into 13 topics, with the answer that should satisfy a reviewer and the answer that should worry one. Use it as your questionnaire, or as a checklist against the vendor’s.</p><h4>Why BI needs its own questionnaire</h4><p>Most vendor security questionnaires were written for tools that hold a slice of your data: a CRM, a ticketing system, a file share. A BI tool is closer to a database client with a web interface. It stores connection credentials for your warehouse, ERP, or clinical system. It executes SQL against them on demand. It renders results to users whose only qualification is a login, and it may email those results out on a schedule. A weakness anywhere in that chain, from a credential in plaintext to a row filter a user can remove, exposes the source data, not just the tool’s own records.</p><p>That is why the questions below spend as much time on data handling and access design as on the vendor’s own controls. It is also why the answers matter more than certifications. SOC 2 tells you a vendor has controls over its own environment; it says nothing about whether the product can leak one customer’s rows to another user.</p><h4>The 43 questions</h4><p>Each topic maps to a section of our own <a href="https://dashboardfox.com/security/review-kit/">security review kit</a>, where we answer these questions for DashboardFox. Where we have a weak spot, it is stated there too.</p><h4>1. Deployment and tenancy</h4><p><strong>QuestionA good answerA warning sign</strong> Is the service multi-tenant, single-tenant, or available both ways?Both, with a clear description of what isolation each provides, and single-tenant available without an enterprise contract”Multi-tenant, but it’s secure” with no detail In the multi-tenant case, what separates customers: separate databases, separate schemas, or a tenant ID column?Separate database per customer with unique credentialsA tenant ID column in shared tables, which puts every customer one query bug away from another’s data Can we choose the region where our data and metadata are stored?Yes, named regions, and data stays there”We use global infrastructure” Is a self-hosted option available if our requirements change?Yes, same product, on your infrastructureCloud only, or a self-hosted version that lags the cloud product by years</p><h4>2. Hosting and sub-processors</h4><p><strong>QuestionA good answerA warning sign</strong> Who hosts the service, and where are its attestations?A named provider with published SOC 2 or ISO 27001 reports, and the vendor knows which facilityThe vendor cannot name the data center or provider Which sub-processors can access our data, and is the list published?A short published list with what each one does; every one that stores data is under a DPA or BAAA long list, or one that includes analytics and AI providers the vendor did not mention Will you notify us before adding a sub-processor?Yes, with a stated notice periodSilence, or “see our terms”</p><h4>3. How the tool handles our data</h4><p><strong>QuestionA good answerA warning sign</strong> Does the tool copy our data into its own storage, or query our database in place?Queries in place; holds only report definitions and metadataRequires importing your data into the vendor’s store to work, which doubles your breach surface What is cached, for how long, and is the cache encrypted?A specific answer with a retention period”Results are cached for performance” with no detail Are database credentials stored encrypted, and who can retrieve them?Encrypted secrets store; retrieval requires elevated, logged accessCredentials visible to support staff, or stored in configuration files Do operational logs contain our report data or personal data?No; logs are configured to exclude customer dataThe vendor has not thought about it Do any AI or machine-learning features process our data, and where does it go?A clear yes or no, naming the model provider if yes, with an opt-outAI features enabled by default that send prompts and data to a third party not on the sub-processor list</p><h4>4. Encryption and secrets</h4><p><strong>QuestionA good answerA warning sign</strong> How is data encrypted at rest and in transit?AES-256 at rest, TLS 1.2 or higher in transit, applied to every database and backupEncryption only for “sensitive fields,” or the vendor cannot say which version of TLS Are backups encrypted before they leave the server, and who holds the key?Encrypted client-side; key held offline by the vendor, not by the backup providerBackups encrypted only by the storage provider, which means the provider can read them Are scheduled reports sent through our mail system or yours?Through your SMTP, so report data never transits shared mail infrastructureOnly through the vendor’s shared mail relay</p><h4>5. Workforce access</h4><p><strong>QuestionA good answerA warning sign</strong> How many people can access our environment, and how?A small number of named people; key-based access to hardened hosts; no contractorsUnknown, or a large support team with shared credentials How is elevated access to our data granted and recorded?Just-in-time, with a logged reason, and credentials rotated after useA standing admin account that support uses when needed Are staff background-checked, and is access reviewed and revoked on departure?Yes, with a review cadenceNo policy</p><h4>6. Authentication and authorization in the product</h4><p><strong>QuestionA good answerA warning sign</strong> What password policy is enforced, and is it configurable?A minimum length, breached-password screening, and lockout, aligned to NIST 800–63BEight characters and no lockout Is multi-factor authentication available for end users, and can we require it?Yes, and it can be enforcedMFA for admins only Do you support SSO with our identity provider?SAML or OIDC, or an honest statement of what is available now and what is in development”Yes” that turns out to mean a shared password page How does row-level security work, and can a user remove it?A server-side policy applied to every query for that user; nothing on the report side can bypass itPer-report filters, URL parameters, or anything the vendor’s own documentation says not to use for security Can we restrict access by IP, and control session length and concurrency?Yes to all threeNone available below an enterprise tier</p><h4>7. Logging and audit</h4><p><strong>QuestionA good answerA warning sign</strong> What does the audit trail record?Logins, report executions, data source access, permission changes, exports, and printsLogins only Where is the audit trail stored, and can we query it ourselves?In your own database, queryable in the product, not ingested into the vendor’s systemsOnly available by asking support How long are logs retained?A stated period that meets your regulatory need (six years for HIPAA)Thirty days</p><h4>8. Security testing and vulnerability management</h4><p><strong>QuestionA good answerA warning sign</strong> What penetration testing do you do, by whom, how often, and can we see results?Recurring third-party testing that covers cross-tenant access control, with results shared under NDA”We have a security team” and no report Do you have a published vulnerability disclosure policy?Yes, with response timesNo way for a researcher to report a flaw How quickly are critical vulnerabilities patched?Emergency maintenance for critical fixes; automatic OS patchingA quarterly release cycle with no exception process</p><h4>9. Change management and secure development</h4><p><strong>QuestionA good answerA warning sign</strong> Is every production change reviewed by someone other than its author and tied to a record?Yes, pull-request review and ticket traceabilityDevelopers deploy directly Are development and production separated, and are secrets kept out of code?Yes and yesShared environments, or a past incident involving a leaked key</p><h4>10. Incident response and breach notification</h4><p><strong>QuestionA good answerA warning sign</strong> Is there a written incident response plan, and how fast will you tell us about an incident?A documented plan with named roles; acknowledgement within hours and updates on a stated cadence”We’ll let you know” What is your breach notification commitment?A contractual period, such as 72 hours, that lets you meet your own deadlinesNothing in writing</p><h4>11. Business continuity and disaster recovery</h4><p><strong>QuestionA good answerA warning sign</strong> How often are backups taken, how long are they kept, and where?A schedule, a retention period, and an offsite location in your regionThe vendor has to check When did you last test a restore?A date within the last year, with results recordedNever, or “backups are automatic” What is your uptime commitment, and how is downtime credited?A published SLA with a percentage and a credit”Best effort” What happens if your company goes out of business?An honest answer: data export on demand, and ideally a self-hosted edition you could run yourselfNo plan</p><h4>12. Physical and endpoint security</h4><p><strong>QuestionA good answerA warning sign</strong> Who is responsible for physical security of production, and can we see their attestation?The hosting provider, with reports availableThe vendor runs servers in an office Are staff workstations encrypted, patched, and protected?Full-disk encryption, automatic updates, host firewall, anti-malware, documented standardNo standard</p><h4>13. Compliance and insurance</h4><p><strong>QuestionA good answerA warning sign</strong> Which agreements will you sign: DPA, BAA, FERPA addendum, others?A list, with the plans on which each is available”We’re compliant with everything” Do you hold SOC 2, and if not, what do you offer instead?Either a current report, or a documented policy set mapped to questionnaire items with a stated plan and date for SOC 2No report and no documentation What cyber liability insurance do you carry, and can we see the certificate?A specific limit and a certificate on requestThe vendor does not know What happens to our data at termination?Return or deletion on a stated schedule, backups purgedUnstated</p><h4>Reading the answers</h4><p>Three patterns separate vendors quickly.</p><p><strong>Specificity.</strong> Good answers contain numbers, names, and dates: TLS 1.2, six years, tested in March, two named engineers. Weak answers contain adjectives: robust, industry-standard, enterprise-grade. A vendor that answers “how long are logs kept?” with “we take security very seriously” has told you the answer is “we don’t know.”</p><p><strong>Admitted gaps.</strong> No small vendor has everything. A vendor that says “native SAML is in development; here is what we offer today” is telling you the truth about one thing, which makes the rest of its answers more credible. A vendor that claims a clean sheet is either very large or not reading the questions.</p><p><strong>Documents on request.</strong> Ask for the incident response plan, not a summary of it. Ask for the last penetration test report under NDA. Ask for the certificate of insurance. Vendors that have done the work can produce these in a day. Vendors that have not will stall, and the stall is your answer.</p><h4>How DashboardFox answers these</h4><p>Every question above is answered for DashboardFox on our <a href="https://dashboardfox.com/security/review-kit/">security review kit</a> page, in the same 13 topics, with links to the underlying policy where one is published. The short version: shared, dedicated, and self-hosted deployment; OVHcloud hosting in US and EU regions with a published sub-processor list; queries in place with no copying of your data; AES-256 at rest and TLS 1.2 or higher in transit; backups encrypted before they leave the server with the key held offline; production access limited to a small number of named people over key-based connections with just-in-time, logged elevated credentials; NIST 800–63B password policy with breach screening and lockout; server-enforced row-level and field-level security on every plan; an audit trail that lives in your own database and is not ingested into ours; continuous third-party penetration testing with results under NDA; a published vulnerability disclosure policy; documented incident response, continuity, and change management; 72-hour breach notification; a 99.5% uptime SLA; and a BAA available on Enterprise Dedicated Cloud, backed by a standalone $5 million cyber liability policy.</p><p>The gaps, since a questionnaire should surface them: SOC 2 Type II is on our roadmap and not yet complete, and our controls are documented instead in an 18-policy set with a traceability matrix that maps each control to standard questionnaire items. Native SAML and OIDC single sign-on for end users is in development; today end users get session-token SSO plus optional MFA through Cisco Duo, and administrators get SSO through an identity-aware proxy. We would rather you learn both of those here than in the middle of a review. We have passed enterprise security reviews on this documentation, including one for a healthcare organization that now runs PHI on DashboardFox under a signed BAA.</p><p><a href="https://dashboardfox.com/security/review-kit/">Open the security review kit →</a> · <a href="https://dashboardfox.com/images/docs/DashboardFox-Security-Overview.pdf">Download the security overview (PDF) →</a> · <a href="https://dashboardfox.com/contact/?topic=security-review">Request the full security pack →</a></p><h4>Frequently asked questions</h4><h4>Does a BI vendor need SOC 2 to pass a security review?</h4><p>No. SOC 2 is a convenient package of evidence, and many reviewers ask for it first, but the requirement is the controls, not the report. A vendor without SOC 2 can pass with documented policies, test results, and honest answers; a vendor with SOC 2 can still fail on product-level questions like row-level security or credential storage, which SOC 2 does not examine.</p><h4>What is the most important question to ask a BI vendor?</h4><p>Whether the tool copies your data into its own storage or queries it in place. Everything else about your exposure follows from that answer: how many copies exist, where they are, how they are encrypted, and what has to be deleted when you leave.</p><h4>How is row-level security supposed to work in a BI tool?</h4><p>As a policy applied by the server to every query a user runs, based on who they are, with nothing on the report or dashboard side able to remove it. Per-report filters, URL parameters, and separate copies of dashboards per audience are not security controls, and several vendors’ own documentation says so.</p><h4>Should we send our standard SaaS questionnaire or a BI-specific one?</h4><p>Send your standard one for the vendor’s own controls, and add the product questions from topics 1, 3, 6, and 7 above. Those are the ones generic questionnaires miss, and they are where BI tools differ most.</p><h4>How long should a BI vendor security review take?</h4><p>With a vendor that has its documentation ready, one to two weeks including a call. If it is taking longer, the delay is usually the vendor assembling answers for the first time, which is itself useful information.</p><p><em>This is a practitioner’s checklist, not legal advice. Your security and compliance teams decide what your organization requires.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d44dfbaa7de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[​Which BI Tools Are HIPAA Compliant? BAA Availability Compared (2026)]]></title>
            <link>https://medium.com/@5000fish/which-bi-tools-are-hipaa-compliant-baa-availability-compared-2026-de99d597443d?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de99d597443d</guid>
            <category><![CDATA[hipaa]]></category>
            <category><![CDATA[buying-decisions]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 16:31:00 GMT</pubDate>
            <atom:updated>2026-09-29T16:31:15.816Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Dashboardfox - HIPAA Compliant Dashboards and Reports" src="https://cdn-images-1.medium.com/max/600/0*4EXKdhCFEUJY-YkK.jpg" /></figure><p><strong>Short answer:</strong> No BI tool is HIPAA certified, because HHS certifies nothing. The question that matters is whether the vendor will sign a Business Associate Agreement, and under what conditions. As of September 2026: Microsoft covers Power BI under its standard BAA; Google covers Looker and Looker Studio under its Cloud BAA, but not Looker Studio Pro; Salesforce covers Tableau Cloud but excludes Tableau Server and Tableau Bridge; Domo, Qlik Cloud, Sisense, and Zoho Analytics sign BAAs, with conditions; Metabase, Klipfolio, Databox, and Geckoboard publish no BAA. DashboardFox signs a BAA on Enterprise Dedicated Cloud. Details, exclusions, and how to verify each are below.</p><h4>What “HIPAA compliant” can and cannot mean for a BI tool</h4><p>HIPAA regulates covered entities and their business associates. When a BI vendor can access protected health information in the course of providing its service, by querying it, caching it, displaying it, or logging report activity, the vendor is a business associate, and the covered entity may use it only under a written Business Associate Agreement. That agreement makes the vendor directly liable for its own HIPAA failures, which is why vendors are careful about when they sign one.</p><p>So a vendor’s HIPAA position comes down to three facts: whether it signs a BAA at all, which products and plans the BAA covers, and what the BAA excludes. Marketing pages rarely state all three. The comparison below does, with the source for each, so you can verify before you rely on it.</p><h4>BAA availability by vendor</h4><p>Checked against each vendor’s own legal, trust, or compliance pages in September 2026. Where a vendor publishes nothing, that is stated rather than guessed. Vendors change these terms, so confirm in writing before PHI is provisioned.</p><p><strong>ToolSigns a BAA?Conditions and coverageNotable exclusionsSelf-hosted option</strong> Microsoft Power BIYesIncluded by default in the Microsoft Online Services Data Protection Addendum for customers that are covered entities or business associates. No separate signature required.Covers in-scope services only; preview features and some connectors may fall outside scopePower BI Report Server (Windows only; licensed via SQL Server 2025 or Fabric F64+ reserved capacity) Google LookerYesGoogle Cloud BAA covers Looker hosted deployments. Request through your account manager.Third-party services, insecure API integrations, and any feature not generally available, including previewsCustomer-managed deployment Google Looker StudioYes, with a catchCovered under the Google Cloud Platform BAA. The older standalone Looker Studio BAA is no longer offered to new customers.Looker Studio Pro is expressly excluded from the covered servicesNone Tableau (Salesforce)Yes, Tableau Cloud onlySalesforce Business Associate Addendum, arranged through your account representative. Tableau Cloud must be named as a covered service.Tableau Server, Tableau Bridge, and Tableau Data Connect are excluded. Tableau Public terms prohibit PHI outright.Tableau Server, but it is outside the BAA; you carry the compliance burden DomoYesSigns BAAs for customers that require them; lists HIPAA alongside SOC 2, HITRUST, and ISO 27001. Public documentation does not state which subscription tiers qualify.Public embed is not available on HIPAA-configured instances; some AI configurations route requests to external providersNone, cloud only Qlik CloudYes, with conditionsCustomers may host PHI when using Customer Managed Keys, and must execute a BAA with Qlik. Qlik Cloud holds a SOC 2 Type 2 + HITRUST attestation.Qlik Sense Business does not support Customer Managed Keys, so it cannot hold PHIQlik Sense Enterprise on Windows SisenseYesSigns a BAA; SOC 2.Third-party services, custom code, and uncertified plugins. A 2024 security incident exposed customer credentials, which reviewers will ask about.Yes Zoho AnalyticsYes, on requestZoho provides a BAA template on request and describes itself as a business associate for customers handling PHI.Coverage varies by product and plan; confirm Zoho Analytics is includedZoho Analytics On-Premise MetabaseNo published BAAMetabase Cloud advertises SOC 2 Type II but publishes no BAA. Metabase’s own guidance for HIPAA workloads is to self-host.n/aYes, open source or Pro/Enterprise self-hosted KlipfolioNo published BAANo HIPAA statement or BAA found on Klipfolio’s site or documentation as of September 2026.n/aNone DataboxNo published BAANo HIPAA statement or BAA found as of September 2026.n/aNone GeckoboardNo published BAANo HIPAA statement or BAA found as of September 2026.n/aNone DashboardFoxYes, on Enterprise Dedicated CloudBAA with the Compliance Tier. PHI runs on a dedicated server and database; sub-processor BAAs with hosting and backup providers are executed before PHI is provisioned. Not offered on shared plans.Shared Starter, Growth, and Scale plansYes, perpetual license; no BAA needed because the vendor has no access</p><h4>What the table doesn’t tell you</h4><h4>A BAA covers named services, not a brand</h4><p>The pattern across the large vendors is the same: the agreement is scoped to specific products, and adjacent products with similar names are left out. Google covers Looker Studio but not Looker Studio Pro. Salesforce covers Tableau Cloud but not Tableau Server or Tableau Bridge, which means a hybrid setup that pulls on-premise data into Tableau Cloud through Bridge has a gap in the middle. Microsoft’s BAA covers in-scope services, and new features usually enter scope after general availability, not at preview. Read the covered-services list, not the press release.</p><h4>Self-hosted removes the BAA question, not the compliance question</h4><p>Where the software runs on your own infrastructure and the vendor has no access to your data, the vendor is not a business associate and no BAA is needed from it. Power BI Report Server, Tableau Server, self-hosted Metabase, Qlik on Windows, and DashboardFox Self-Hosted all work this way. The trade is that every safeguard, from patching and backups to audit logging and access control, becomes your job. That suits organizations with a strong IT function and is a poor fit for those without one.</p><h4>AI features are the newest gap</h4><p>Several vendors now route natural-language and AI features through third-party model providers. Google excludes non-GA features from its Looker BAA; Domo’s AI can be configured to call external APIs; Tableau’s AI features have raised the same question. If your users will type questions about patient data into an AI assistant, confirm in writing whether that feature is inside the BAA and where the prompts go.</p><h4>Shared infrastructure is permitted, but it shifts the risk analysis</h4><p>Most of the tools above run multi-tenant: many customers on shared application servers, separated by software logic. HIPAA does not prohibit that, and the big vendors’ BAAs cover it. But your risk analysis has to account for it, and cross-tenant access-control flaws are among the most common findings in web application testing. Dedicated single-tenant hosting, where your PHI sits on a server and database that serve only you, removes that class of risk. Few of the vendors above offer it below enterprise pricing; DashboardFox offers it from $1,499 a month.</p><h4>How to verify a vendor’s HIPAA position in ten minutes</h4><p><strong>StepWhat you’re looking for</strong> 1. Find the BAA document, not the compliance pageA legal document with a covered-services definition. If the only thing on offer is a page that says “HIPAA compliant,” ask for the agreement. 2. Read the covered-services and exclusions sectionsYour exact product, plan, region, and add-ons named. Anything not named is not covered. 3. Ask which plan you must be onMany vendors sign only on enterprise or top tiers. Get the plan name in writing. 4. Ask about sub-processorsThe vendor’s hosting and backup providers must have BAAs with the vendor. Ask for the list. 5. Ask where your data actually livesShared or dedicated? Which region? Is anything cached or copied? 6. Ask what happens at terminationReturn or destruction of PHI on a stated schedule, backups included.</p><p>For the full list of what to require beyond the BAA, including audit log retention, enforced row-level security, and evidence for your security review, see <a href="https://dashboardfox.com/blog/hipaa-compliant-bi-software/">HIPAA-Compliant BI and Dashboard Software: What to Require From a Cloud Vendor</a>.</p><h4>Where DashboardFox fits</h4><p>DashboardFox is our product, so read this section with that in mind. We sign a Business Associate Agreement on Enterprise Dedicated Cloud with the Compliance Tier. PHI runs on a server and PostgreSQL database that serve your organization alone, in a US region that is a HIPAA/HITECH-attested facility, with BAAs executed with our hosting and encrypted-backup providers before any PHI is provisioned. Database audit logs are retained for six years, row-level and field-level security are enforced server-side on every plan, and the work is backed by a standalone $5 million cyber liability policy. A healthcare organization runs PHI on this arrangement in production today under a signed BAA.</p><p>We do not sign a BAA on our shared Starter, Growth, or Scale plans. A BAA makes us responsible for your PHI, and we are not willing to take that on for data sitting on shared infrastructure. If you would rather keep everything in-house, DashboardFox Self-Hosted is a perpetual license that runs entirely on your servers, and no BAA from us is needed because we never touch the data.</p><p><a href="https://dashboardfox.com/deployment/">Compare deployment options →</a> · <a href="https://dashboardfox.com/legal/baa/">Read our BAA terms →</a> · <a href="https://dashboardfox.com/security/review-kit/">Security review kit →</a> · <a href="https://dashboardfox.com/contact/?topic=engineer">Talk to an engineer →</a></p><h4>Frequently asked questions</h4><h4>Is Power BI HIPAA compliant?</h4><p>Power BI can be used with PHI under Microsoft’s BAA, which is included in the Online Services Data Protection Addendum for covered entities and business associates without a separate signature. Coverage applies to in-scope services; confirm that any preview features or third-party connectors you use are in scope. Power BI Report Server runs on your own infrastructure and needs no BAA from Microsoft.</p><h4>Is Tableau HIPAA compliant?</h4><p>Tableau Cloud can be, under a Salesforce Business Associate Addendum that names Tableau Cloud as a covered service. Tableau Server, Tableau Bridge, and Tableau Data Connect are excluded, and Tableau Public’s terms prohibit PHI. The BAA is arranged through a Salesforce account representative, not self-service.</p><h4>Is Looker Studio HIPAA compliant?</h4><p>Looker Studio is covered under the Google Cloud Platform BAA, and Google publishes an implementation guide for configuring it with PHI. Looker Studio Pro is expressly excluded from that BAA. Customers must execute the Google Cloud BAA before using Looker Studio with PHI.</p><h4>Is Metabase HIPAA compliant?</h4><p>Metabase publishes no Business Associate Agreement for Metabase Cloud. Its own guidance for customers with HIPAA requirements is to self-host, in which case Metabase has no access to the data and no BAA is needed. Self-hosted Metabase can be part of a HIPAA-aligned stack if you supply the safeguards yourself.</p><h4>Does a BI tool need a BAA if it only connects to a database and never stores PHI?</h4><p>Yes, if the vendor can access PHI while providing the service. Querying, caching, rendering, and logging all count as access. The exception is self-hosted software, where the vendor has no access at all.</p><h4>Which BI tools offer dedicated single-tenant hosting for PHI?</h4><p>Most cloud BI vendors run multi-tenant and cover it under their BAA. Dedicated single-tenant hosting is usually an enterprise-contract item at the large vendors. DashboardFox offers a dedicated server and database as Enterprise Dedicated Cloud from $1,499 per month, and that is the only tier on which it signs a BAA.</p><p><em>Vendor terms were checked against the vendors’ published legal and compliance pages in September 2026 and can change. This post is not legal advice; confirm coverage in writing with each vendor and with your own counsel before provisioning PHI.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de99d597443d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[​HIPAA-Compliant BI and Dashboard Software: What to Require From a Cloud Vendor]]></title>
            <link>https://medium.com/@5000fish/hipaa-compliant-bi-and-dashboard-software-what-to-require-from-a-cloud-vendor-1906a7dfcda9?source=rss-fa7a4766af1d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1906a7dfcda9</guid>
            <category><![CDATA[hippa]]></category>
            <category><![CDATA[buying-decisions]]></category>
            <dc:creator><![CDATA[5000fish]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 16:20:05 GMT</pubDate>
            <atom:updated>2026-09-29T16:20:19.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="DashboardFox - HIPAA-Compliant Cloud BI Software" src="https://cdn-images-1.medium.com/max/600/0*tgC1VuFevwKZ_o6w.jpg" /></figure><p><strong>Short answer:</strong> No BI tool is “HIPAA certified,” because no such certification exists. A cloud BI vendor can be used with protected health information if it will sign a Business Associate Agreement, keeps your PHI off shared infrastructure or can show you exactly how tenants are isolated, encrypts data at rest and in transit, retains audit logs for six years, has BAAs with its own hosting and backup providers, and can pass your security review with documentation rather than assurances. Most vendors fail on the second, fourth, or fifth of those, and the ones that pass usually put it all behind an enterprise tier. This post lists the compliance requirements that apply to a BI tool, why each item matters for data privacy, and what to ask.</p><h4>Why “HIPAA compliant” on a vendor’s website means very little</h4><p>HIPAA regulates covered entities and their business associates. It does not certify software. When a vendor says its product is HIPAA compliant, the claim can only mean one of two things: the vendor operates its service in a way that lets a covered entity use it without breaching the rules, or the vendor is repeating a phrase it has seen on competitor websites. You cannot tell which from the marketing page.</p><p>What you can verify is the vendor’s willingness to become a business associate. Under the Privacy Rule, a covered entity may share PHI with a vendor only under a written agreement that binds the vendor to HIPAA’s safeguards, and that agreement makes the vendor directly liable to regulators for its own failures. A vendor that will not sign a BAA is telling you it is not prepared to carry that liability, whatever its website says. That is the first filter, and it removes most of the market.</p><h4>What HIPAA actually requires of a BI tool handling healthcare data</h4><p>A dashboard tool sits in an unusual position. It usually does not own the health records; it queries the systems that do. But if it connects to a database containing PHI, displays PHI to users, caches query results, emails scheduled reports, or writes audit logs that contain patient identifiers, it is handling PHI and the vendor is a business associate. The requirements that follow are the ones that bear on that position. Most come from the HIPAA Security Rule’s technical safeguards; the BAA and minimum-necessary obligations come from the Privacy Rule.</p><p><strong>RequirementWhere it comes fromWhat it means for a BI vendor</strong> Business Associate AgreementPrivacy Rule, 45 CFR 164.502(e) and 164.504(e)The vendor signs a BAA before any PHI is provisioned, and has its own BAAs with every subcontractor that touches PHI, including hosting and backup providers Access controls and unique user identificationSecurity Rule, 164.312(a)Named accounts, role-based access controls, and a way to limit each user to the rows and fields they are entitled to see Audit controlsSecurity Rule, 164.312(b)Logs of who ran which report, when, against which data source, and what they exported Encryption in transit and at restSecurity Rule, 164.312(a)(2)(iv) and (e)(2)(ii)Currently “addressable,” meaning required unless the entity documents why an alternative is reasonable. In practice every reviewer expects both. Documentation retentionSecurity Rule, 164.316(b)(2)Policies, procedures, and records of security activity kept for six years from creation or last effective date. Vendors should retain audit records on the same schedule. Breach notificationBreach Notification Rule, 164.404 and 164.410A business associate must notify the covered entity of a breach without unreasonable delay and within 60 days of discovery, so the covered entity can meet its own deadline Minimum necessaryPrivacy Rule, 164.502(b)The tool should let you expose only the fields a role needs, not the whole table</p><p>Two things about this table. First, the Security Rule is under revision. HHS published a proposed update in January 2025 that would remove the “addressable” category and make encryption, multi-factor authentication, asset inventories, and regular penetration testing mandatory for everyone. As of this writing it is still a proposal, and HHS has signaled that a final rule is not expected before 2027. Treat the proposed items as the direction of travel: a vendor that already meets them will not need to scramble when the rule lands. Second, none of these requirements say anything about where the software runs. Cloud is permitted. What matters is whether the vendor can demonstrate the controls.</p><h4>Six things to require from a cloud BI vendor</h4><h4>1. A signed business associate agreement, and BAAs behind it</h4><p>Ask for the business associate agreement before the demo. Read it for two things: whether it covers the vendor’s subcontractors, and whether it lists them. A vendor whose hosting provider has not signed a BAA cannot lawfully hold your PHI there, no matter what the vendor’s own agreement says. Ask directly: “Which of your providers store or process our data, and do you have a BAA with each?” The answer should be a list, not a shrug.</p><h4>2. Isolation you can describe on a diagram</h4><p>Most cloud BI products are multi-tenant: many customers on the same application servers and often the same database, separated by software logic. That is not forbidden by HIPAA, but it puts the entire burden of isolation on the vendor’s code being correct, and cross-tenant access-control bugs are among the most common findings in web application testing. For PHI, prefer one of two stronger arrangements: a dedicated server and database that serve your organization alone, or self-hosted software on your own infrastructure. If you accept multi-tenant, get the vendor to draw the data path and show you the test results that cover cross-tenant access.</p><h4>3. Query in place instead of copying</h4><p>Some BI tools import your data into their own storage to make it fast to chart. Every copy is another place PHI lives, another backup set, another breach surface, and another thing to delete when the contract ends. Tools that query your database live and hold only report definitions and metadata keep the PHI where it already is, under controls you already audit. Ask where query results are cached, for how long, and whether cached data is encrypted.</p><h4>4. Row-level and field-level security that is enforced, not filtered</h4><p>Clinical and operational reporting almost always needs the same report to show different rows to different people: a clinic manager sees their clinic, a payer sees their members, a physician sees their panel. Many tools handle this with per-user filters that a determined user can bypass by editing a URL or opening the underlying dataset. What you want is a policy applied by the server to every query for that user, with no way to remove it from the report side. Ask the vendor to show you a user attempting to remove the filter, and what happens.</p><h4>5. Audit logs you own, retained for six years</h4><p>The audit log is your evidence in an investigation. It should record logins, report executions, data source access, permission changes, exports, and prints. Two details matter: retention, which should match HIPAA’s six-year documentation period, and ownership. If the vendor ingests your activity logs into its own analytics systems, that is another flow of PHI-adjacent data to account for. Better vendors keep the audit trail in your own database, queryable by you, and stay out of it.</p><h4>6. Evidence for the security review</h4><p>Your security team will send a questionnaire. What separates a vendor that passes from one that stalls is having the answers already written: an architecture summary, a data-flow diagram, policies for access control, incident response, business continuity, change management, vendor management, recent penetration test results, the sub-processor list, and a certificate of insurance. SOC 2 is a convenient package for all of that, but it is not a HIPAA requirement, and a vendor without SOC 2 can still pass if it can produce the underlying documentation. A vendor with SOC 2 but no BAA cannot.</p><h4>Cloud, dedicated, or self-hosted: which fits PHI</h4><p>Healthcare BI projects often start by ruling out cloud. That instinct is reasonable but usually solves the wrong problem, and it can add months to implementation. The issue with cloud BI for PHI is shared infrastructure and vendor access, not the cloud itself. There are three arrangements worth comparing.</p><p><strong>ArrangementIsolationWho runs itBAA needed from the BI vendor?Best for</strong> Shared cloud (multi-tenant)Software-level separation on shared serversVendorYes, and many vendors will not sign one for this tierNon-PHI reporting, or PHI only with a vendor whose isolation you have tested Dedicated cloud (single-tenant)Your own server and database, no other customer on the machineVendorYesPHI workloads without the time or staff to provision servers internally Self-hostedYour infrastructure, your networkYouNo, because the vendor never has access to the dataAir-gapped environments, strict on-premise policy, or when internal IT can provision and patch servers promptly</p><p>The dedicated option deserves more attention than it usually gets. In our experience, healthcare teams frequently arrive wanting self-hosted, then discover that getting a server approved, provisioned, hardened, and patched through internal IT takes longer than the reporting project itself. Vetting one cloud vendor is often faster. A dedicated server gives the same single-tenant isolation with the vendor doing the operations work, and the vendor signs a BAA because it is the one with access.</p><h4>Questions to put in your RFP</h4><p>These are the questions that separate vendors quickly. Most of them have one-word answers, which is the point.</p><p><strong>QuestionThe answer you want</strong> Will you sign a BAA, and on which plans?Yes, with the plan named Do your hosting and backup providers have BAAs with you?Yes, executed before PHI is provisioned Is our data on shared or dedicated infrastructure?Dedicated, or a clear description of shared-tenant isolation with test evidence Do you copy our data into your platform, or query it in place?Query in place; caches described and encrypted How is row-level security enforced?Server-side policy per user, not a report-side filter How long are audit logs retained, and who can read them?Six years; the customer owns and queries them Which staff can access our environment, and how?A small number of named people, key-based access, logged and rotated elevated credentials What penetration testing do you do, and can we see results?Recurring third-party testing, results shared under NDA What cyber liability insurance stands behind the BAA?A specific policy and limit What happens to our data when we leave?Returned or destroyed on a stated schedule, with backups purged</p><h4>How DashboardFox handles PHI</h4><p>DashboardFox is our product, so weigh this section accordingly. We built it to answer the questions above the way we would want them answered.</p><p>We sign a Business Associate Agreement on Enterprise Dedicated Cloud with the Compliance Tier, where PHI runs on a server and a PostgreSQL database that serve your organization alone, in a US region that is a HIPAA/HITECH-attested facility. BAAs with our hosting and encrypted-backup providers are executed before any PHI is provisioned. Data is encrypted with AES-256 at rest and TLS 1.2 or higher in transit, backups are encrypted before they leave the server, and the decryption key is held offline. Row-level and field-level security are enforced by the server on every query and are included on every plan. The audit trail lives in your own DashboardFox database, is queryable by you, is not ingested into our systems, and database audit logs are retained for six years. Production access is limited to a small number of named personnel over key-based connections, with elevated credentials that require a logged reason and are rotated after each use. The work is backed by a standalone $5 million cyber liability policy. A healthcare organization runs PHI on this arrangement in production today, under a signed BAA, after passing its own security review.</p><p>We do not offer a BAA on our shared Starter, Growth, or Scale plans, because a BAA makes us responsible for your PHI and we are not willing to carry that responsibility on shared infrastructure. Self-hosted customers do not need a BAA from us, because we never have access to their data. SOC 2 Type II is on our roadmap; in the meantime our controls are documented in a policy set mapped to standard questionnaire items, and we complete security reviews directly.</p><p><a href="https://dashboardfox.com/deployment/">Compare deployment options →</a> · <a href="https://dashboardfox.com/security/review-kit/">Security review kit →</a> · <a href="https://dashboardfox.com/legal/baa/">Business Associate Agreement →</a> · <a href="https://dashboardfox.com/contact/?topic=engineer">Talk to an engineer about your healthcare reporting →</a></p><h4>Frequently asked questions</h4><h4>Is there such a thing as HIPAA-certified BI software?</h4><p>No. HHS does not certify software or vendors. A vendor can operate in a way that lets a covered entity use it lawfully, and can document that with a BAA, policies, and test results, but “certified” is a marketing word.</p><h4>Can a cloud BI tool be used with PHI at all?</h4><p>Yes. HIPAA does not prohibit cloud services. It requires a BAA with the vendor, appropriate safeguards, and a risk analysis that considers where the data lives. Dedicated single-tenant hosting makes that analysis much easier than shared multi-tenant hosting.</p><h4>Does a BI tool need a BAA if it only displays PHI and doesn’t store it?</h4><p>If the vendor can access PHI in the course of providing the service, which includes querying it, caching results, or logging report activity, it is a business associate and needs a BAA. “We only display it” is not an exception under the rule.</p><h4>Is SOC 2 required for HIPAA?</h4><p>No. SOC 2 is a voluntary attestation. Many reviewers ask for it because it is a convenient package of evidence, but the requirement is the safeguards themselves and a BAA. A vendor without SOC 2 can pass a security review with the underlying documentation.</p><h4>How long should a BI vendor keep audit logs for PHI?</h4><p>HIPAA’s documentation requirement is six years. Vendors that retain audit records for shorter periods leave the covered entity to fill the gap, so ask for six years or export the logs yourself on a schedule.</p><h4>Is self-hosted BI safer for PHI than cloud?</h4><p>It keeps healthcare data entirely on your own infrastructure and removes the vendor from the picture, which simplifies the risk analysis and eliminates the BAA. But security then depends entirely on your own patching, backups, access control, and monitoring. For organizations with a strong IT function that is the safest option. For those without, a dedicated cloud server run by a vendor under a BAA is often more secure in practice than a self-hosted server nobody has time to maintain.</p><p><em>This post describes what to require from a vendor. It is not legal advice; your compliance officer and counsel decide what your organization needs.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1906a7dfcda9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>