Rayfin Data App: Power BI + TypeScript

Key insights

• This video demonstrates a new approach to Power BI delivery using the Rayfin Data App template that combines a TypeScript/React frontend with a Power BI Semantic Model backend.
  The presenter shows how this shifts reporting from static PBIX files to full web applications.
• The app architecture uses Microsoft Fabric Apps features: managed SQL, GraphQL/REST endpoints, and static hosting are provisioned for you.
  Rayfin works with Fabric to remove manual infrastructure setup and speed development.
• The video explains cost gains: host the app on a low-cost F2 Fabric capacity and share with free Fabric users instead of buying a Power BI Pro license per viewer.
  For large audiences this reduces licensing costs and improves user reach.
• Development becomes code-first: the Rayfin CLI and TypeScript model classes auto-generate APIs and database schemas.
  The demo also shows using GitHub Copilot prompts to speed enhancements without manual coding.
• Security and governance stay centralized: the Semantic Model remains the trusted data layer and the apps use Microsoft Entra ID for authentication.
  This avoids data duplication and removes the need for embed tokens.
• Practical impact: teams can build custom, type-safe apps with richer UX while keeping a single source of truth.
  The approach scales distribution, preserves governance, and leverages existing Power BI investments.

Introduction

In a recent YouTube video, Reza Rad (RADACAD) [MVP] presents a new approach to distributing Power BI analytics by demonstrating the Rayfin Data App template paired with a TypeScript/React frontend and a Power BI semantic model backend. He argues that this combination shifts reporting from static PBIX files shared via workspaces to fully managed web applications that many users can access without individual Pro licenses. Consequently, the model promises both cost savings and richer user experiences, while maintaining a governed data layer. As a result, organizations should reassess how they deliver analytics at scale.

How Rayfin and Fabric Apps Work

Reza explains that the Rayfin template and the broader Fabric Apps layer let developers define backends in code using TypeScript classes and decorators, which then provision managed resources automatically. For instance, the system can create SQL storage, GraphQL endpoints, authentication via Microsoft Entra ID, and static hosting without manual configuration. Moreover, the approach connects directly to existing semantic models so applications can query and interact with governed logic through standard APIs. Therefore, teams can reuse a single source of truth while exposing data in a custom web app surface.

Developer Experience and Live Demo

In the live demo, Reza builds a Rayfin Data App from scratch and shows how GitHub Copilot can accelerate development by generating code snippets and scaffolding components. He demonstrates the TypeScript-first workflow that produces type-safe models and auto-generated APIs, which reduces the chance of runtime errors and speeds up iteration. Additionally, the integration with VS Code makes it familiar for modern web developers who already work with React and TypeScript, and with developer tools. Consequently, development teams can deliver richer interfaces while retaining governance and data integrity.

Cost and Licensing Implications

One of the most significant points Reza makes is the cost story: hosting the app on a low-tier Fabric capacity such as F2 and sharing with free Fabric users can be far cheaper than buying Power BI Pro licenses for every viewer. Thus, organizations with large, read-heavy audiences could see dramatic savings while still controlling access and governance through the semantic model. However, the real savings depend on usage patterns, capacity sizing, and expected concurrency, so finance and IT teams must model costs carefully. Therefore, while promising, the cost advantage is not automatic and requires operational planning.

Tradeoffs and Operational Challenges

Although the approach offers flexibility and lower per-user costs, it introduces tradeoffs that teams must weigh. For example, building and maintaining a custom frontend adds development and support overhead compared with publishing standard Power BI reports, and custom logic sometimes requires additional testing and deployment discipline. Furthermore, while using the semantic model avoids data duplication, it can create tighter coupling between apps and central models, so governance processes must ensure backward compatibility and performance under load. In short, organizations will need to balance the benefits of richer UX and cost savings against ongoing engineering effort and governance complexity.

Security, Governance, and Scaling

Reza emphasizes that security and governance remain central: Fabric Apps include built-in authentication and handle the handshake to semantic models, which reduces the need for custom token management and embed tokens. Consequently, this simplifies secure access while preserving enterprise controls, but teams must still configure roles and monitor access patterns to meet compliance requirements. Additionally, performance and scaling depend on choosing the right Fabric SKUs, testing concurrency, and optimizing DAX queries used by the semantic model. Therefore, planning capacity, caching strategies, and query performance is essential to avoid surprises in production.

Practical Considerations for Adoption

Practically speaking, adopting this pattern requires skills in both Power BI semantics and modern web development, which can be a barrier for some teams that lack full-stack developers. Thus, organizations should consider pilot projects, training, and possibly partnering with consultants to bridge gaps while evaluating the long-term maintainability of custom apps. Moreover, teams should weigh vendor and platform lock-in risk, testing whether their architecture remains flexible as needs change. Ultimately, a phased approach helps prove the model while containing risk.

Future Outlook

Reza frames this shift as more than a technical demo; he sees it as a new distribution model where semantic models become central, multi-surface assets that power both Power BI reports and custom web applications. As a result, analytics delivery can become more consistent, governed, and adaptable to diverse user experiences across an organization. Nevertheless, the pace of adoption will hinge on how well teams manage the tradeoffs of development cost, governance, and operational complexity. In conclusion, the Rayfin Data App approach offers a compelling direction, but success depends on careful planning and skillful execution.

Keywords

Power BI reporting, Rayfin Data App, TypeScript for Power BI, Power BI semantic model, semantic modeling BI, Power BI developer tools, TypeScript data apps, modern BI reporting