The Case for One Dashboard Instead of Fifty
Why Piskes Analytics ships as one fixed dashboard instead of a builder you configure, and why that's a deliberate constraint rather than a missing feature.
Piskes Analytics gives you one dashboard: four stat cards, one traffic chart, one top-events chart. No builder, no custom widgets, no second page. The obvious reaction is that this is a smaller product than a configurable analytics suite. It's worth making the opposite case: that a fixed, opinionated view is sometimes the better design, not a lesser one.
What "more configurable" actually costs
Looker Studio — a widely used, well-resourced BI tool — has documented limits that show up specifically because it's built to be configured: it caps blended data sources at five per dashboard, caps charts at fifty per page, and 2026 coverage of the tool calls out that it has no version control and no real collaborative workflow for building dashboards together. None of that is a knock on Looker Studio specifically — it's the natural cost of being a builder. The more configurable a tool is, the more there is to configure, maintain, and eventually hit the edge of.
What a fixed dashboard avoids
A dashboard you can't misconfigure is a dashboard nobody on your team can quietly break. There's no risk of someone building a confusing custom view that only makes sense to them, no dashboard sprawl where five versions of "the real numbers" exist across different people's configurations, and no onboarding cost for a new team member trying to figure out which of fifty saved views is the one that matters. Everyone who opens Analytics sees the same four numbers and two charts every time.
The tradeoff, stated honestly
This isn't free. A fixed dashboard means you can't build the specific view your team actually wants if it doesn't match what's already there — there's no way to add a metric, swap a chart, or combine data from outside Piskes into the same view. If your team's reporting needs are genuinely more complex than four numbers and two charts, that complexity has nowhere to go inside Analytics today, and no amount of familiarity with the product will surface a configuration option that doesn't exist.
Why the constraint is defensible
The case for shipping one dashboard isn't that configurability is bad — it's that most teams checking "is anyone using this" don't need a BI platform to answer that question, and the ones that do need more are better served by a dedicated tool than by a dashboard builder bolted onto a workspace app. A single, consistent view that everyone reads the same way is a legitimate design choice for that audience, not a corner that got cut.