Build a custom ZopNight dashboard for FinOps with 10 widget types, 4 presets, RBAC, and per-org default. Slot-based 6-column grid with per-widget error boundaries.
This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 20 minutes. Before you start you will want: Dashboard policies enabled for the role; A ZopNight account; Billing sync configured for cost widgets.
The steps
- Pick a starting preset.
- Clone to customise.
- Add and arrange widgets.
- Set as org default.
- Confirm RBAC.
- Watch quotas.
Why this is safe to do today
The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.
If you want the fuller context behind this task, the FinOps guide covers where it fits, and the AWS EC2 scheduling page shows the same loop applied to a specific resource.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Can I have per-user dashboards?
Not in v1. Everything is org-shared with a single default pointer. Per-user dashboards and per-user default pointer are explicitly out of scope.
What happens if a widget throws?
Each widget is wrapped in a per-slot WidgetErrorBoundary so one throwing widget falls back to a placeholder rather than unmounting the page.