Upfront: I did not build this. It is an open-source project on GitHub (evidence-dev/evidence, MIT). It is listed here on star count, maintenance activity and how well it fits day-to-day storefront operations.
What it does
- Reports as code — one
.mdfile holds the SQL and the commentary, and builds into a web report with charts, with every change in Git history. - Charts from queries — results render straight into line, bar and map components without a separate charting tool.
- Parameterised templates — a monthly report template regenerates with a new date parameter instead of being rebuilt by hand.
- Deploys as a static site — the build output is static, so any static host will serve it; no long-running service required.
How to use it
One install command, then scaffold a project:
curl -fsSL https://evidence.studio/install.sh | sh
evidence init my-project
cd my-project
evidence dev
Edit the Markdown files under pages/, with SQL in fenced code blocks. Data sources are configured in evidence.config.yaml — MySQL, Postgres, DuckDB and BigQuery among others.
When to use it, and when not to
A natural fit if your operating notes already live as Markdown files. For teammates who need a point-and-click UI, use Metabase.


