Dashboards & data apps
Charts form dashboards, with drafts, releases and restores kept clear. Or have AI generate a data app and preview it in a sandbox.
A sentence you have heard
The report has had six versions. Which one is right?
Why it happens
Reports are edited on a personal laptop and posted to a group chat. A few weeks later nobody knows which data, or which definition, the version in the chat belongs to.
How Shuzi does it
Every change leaves a trace.
Every version can come back.
Charts form dashboards, drafts save automatically, and publishing fixes an immutable version. If something breaks, restore any earlier version. To move between environments, export to YAML.
Versions
- v7current
- v6·
- v5·
↺ Restore to v6
⇣ Export YAML
dashboard.yml · version 1 · dry-run → apply
- 01
Autosaved drafts
Edits are saved to the server as you work, so you can continue on another machine.
- 02
Publish and restore
Publishing fixes a historical version. Restoring first archives the current draft, then returns to the version you pick.
- 03
Reports as code
Charts and dashboards export to YAML. A batch is validated and imported as a whole, and any failure rolls everything back.
In detail
Folders and recycle bin
Folders, search, move and rename. Deleting goes to the recycle bin first and can be undone.
Conflicts never overwrite
If someone else edited first, you are told about the conflict instead of silently overwriting.
Space-based access
View, edit, publish and share are granted separately, and personal spaces can invite collaborators.
AI-generated apps
Generate a data app from plain language and preview it in a sandbox first.
Take your datafrom tangled to clear.
Try it on sample data first, then bring your own.