feat(reports): Using Superset as reporting tool frontend (#316)

###  Summary: Apache Superset Selected as Frontend

To enable analysis on lakehouse data extracted from the FASE
application, the organization evaluated open-source BI tools Apache
Superset and Metabase
[#283](#283)
across data modeling, visualization, RBAC, and authentication criteria.

While both platforms offer comparable data visualization and modeling
features, internal security requirements heavily favored **Apache
Superset**. The organization’s analytics platform mandates centralized
identity integration (OIDC/SAML). The open-source version of Metabase
only supports LDAP, API keys, and Google OAuth, failing internal
standards. Choosing Superset ensures full compliance with institutional
security architecture without sacrificing vital business intelligence
capabilities.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Documented the architectural decision regarding reporting tool
platform selection and evaluation criteria.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: CodeRabbit <noreply@coderabbit.ai>

Author: 3 people

docs-devel/system-architecture/adrs/0008-use-superset-as-reporting-tool-frontend.md

@@ -0,0 +1,32 @@
+# 8. Use Superset as frontend replacement of reporting-tool
+
+Date: 2026-05-21
+
+## Status
+
+Accepted
+
+## Context
+
+Operational data from the FASE application is extracted and loaded into a central lakehouse environment. To enable reporting and data analysis against this lakehouse, we are exploring options for a new frontend BI tool. As part of this evaluation, we are assessing two popular open-source solutions:
+
+- [Superset](https://superset.apache.org/)
+- [Metabase](https://www.metabase.com/)
+
+## Decision
+
+We evaluated both Apache Superset and Metabase as potential frontend replacements for the legacy reporting tool. This evaluation was conducted locally across the following criteria to determine the best fit for our architecture:
+
+- Data Modeling & Representation: Assessed and compared how each tool models and presents lakehouse data relative to the current reporting tool.
+- Visualization & Charting Capabilities: Evaluated the chart types, formatting options, and visualization parity with existing reports.
+- Access Control (RBAC): Analyzed role-based access controls and granular data permissioning features in both platforms.
+- User Authentication: Studied integration capabilities with existing authentication providers (e.g., OIDC, SAML, or LDAP).
+
+## Consequences
+
+While both Apache Superset and Metabase are strong open-source candidates with robust data modeling capabilities, our organization's authentication requirements heavily favor Superset.
+
+- Security & Identity Alignment: Our analytics data platform relies strictly on a centralized identity service. Metabase Open Source only supports LDAP, API keys, and Google OAuth, which does not align with our internal authentication standards. Superset natively supports our required centralized identity integration (e.g., OIDC/SAML).
+- Feature Parity: Superset delivers reporting and data visualization capabilities comparable to Metabase, ensuring we do not compromise on core BI functionality.
+
+Outcome: Choosing Superset ensures full compliance with our security architecture without sacrificing data representation features, making it the preferred long-term solution.