Every industry overspends on non-production in a slightly different way, but the lever is the same: schedule what nobody uses at night to your working hours, then clean up the idle and oversized. Pick your industry below, or see the approach on AWS EC2 and in FinOps.
Browse by industry
- Software as a Service
- Financial Technology
- Healthcare & Life Sciences
- E-Commerce & Retail Tech
- Gaming & Interactive Entertainment
- Media & Entertainment
- Education & EdTech
- Government & Public Sector
- Manufacturing & IoT
- Insurance & Insurtech
- Logistics & Supply Chain
- Real Estate & PropTech
- Travel & Hospitality
- Telecommunications
- Energy & Utilities
- Retail & Consumer Goods
- Legal & LegalTech
- Nonprofit & NGO
- Consulting & Professional Services
- Cybersecurity
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Where should I start?
Start with the FinOps overview for the discipline that ties it together, then use the specific guide, cloud, or location page for the task you are on.
Is production at risk?
No. Production is excluded by default; ZopNight acts only on the non-production resources you choose.
What access does ZopNight need?
A read-only role to start. Discovery, cost reporting, and recommendations all run read-only, and you enable actions when you are ready.
Which clouds are supported?
AWS, GCP, and Azure from one platform, including Databricks across all three. Schedules, groups, overrides, and recommendations work the same way regardless of provider.