# Superset Reporting Layer

Apache Superset chosen as the reporting and visualization layer over the royalty office's read-only Postgres copies, with Evidence as the MIT fallback. The visible end of a staged AI transformation: one producer's records in one picture, every number carrying its source. Chosen, not built yet.

**Status:** Private · Projects · 2026

- **Explainer video:** https://ai-pricing.navonsimon.com/media/superset-postgres.mp4
- **News post:** https://projects.navonsimon.com/news
- **Where it runs:** No instance running. Needs the barak database, a dedicated read-only reporting role and a host inside the office or approved private zone.
- **Note:** Decision · not built yet

## Stack

Apache Superset, PostgreSQL, Evidence (MIT fallback)

## Deploy and where it runs

- Not built yet. Decision and design: ~/Developer/pil/docs/reporting.md

## Current state

Decision, not a deployment. Apache Superset is chosen as the reporting and visualization layer over the read-only Postgres copies; Evidence is the MIT fallback. Built after the first clean copies.

## Watch out

- Read-only: Superset never writes to Barak, Magic or the copies; a write path is not built.
- Data classes: reports contain IDs and PII, so the instance must stay inside the office or approved private zone, never public and never a hosted service holding the data.
- Hosting and auth are undecided; do not expose port 5432 or open a public tunnel.
- Licences were checked 2026-11-06; re-check before deploying or buying.

## Tags

Apache Superset, PostgreSQL, BI, Dashboards, Apache-2.0

---

Brief generated 2026-11-08 from `~/Developer/my-projects/context/`. Canonical URL: https://projects.navonsimon.com/context/superset.md
