What the product actually does
The builder, the reports that create themselves, the integrations, sharing, exports and self-hosting. Each page describes behaviour that exists rather than a roadmap.
The report builder
Drag blocks onto a twelve column grid, pick a measure and a dimension, and watch each block redraw. Publish when it is right, so a half finished edit is never what a teammate opens.
Reports that build themselves
When a project starts sending events the standard taxonomy recognises, the matching reports are created and published with real numbers already in them. Nothing to configure first.
Sending events from your stack
Packages for Stacks and Laravel translate the events your application already emits. Anything else posts JSON to one endpoint. Either way you are not writing tracking calls.
Sharing and embedding
A link shows one published report and nothing around it. Revoke it and it stops working on the next request. Embed it in a page of your own if you would rather.
Exports and scheduled delivery
CSV and XLSX in a shape a spreadsheet can pivot, and the headline numbers by email daily, weekly or monthly in your own timezone.
Running it yourself
A Stacks application with public source. Run it on your own machines and every tier limit falls away, because there is nothing left to enforce them against.