Define cron-based start/stop schedules for non-production environments. Dev and staging resources run only during business hours, automatically. ZopNight applies resource scheduling to non-production across AWS, GCP, and Azure, measured against real usage. See it by cloud or by service below, and the discipline in FinOps.
By cloud
By service
- Resource Scheduling for EC2
- Resource Scheduling for RDS
- Resource Scheduling for EKS
- Resource Scheduling for ECS
- Resource Scheduling for Lambda
- Resource Scheduling for ElastiCache
- Resource Scheduling for Redshift
- Resource Scheduling for SageMaker
- Resource Scheduling for EMR
- Resource Scheduling for ASG
- Resource Scheduling for S3
- Resource Scheduling for EBS
- Resource Scheduling for CloudFront
- Resource Scheduling for DynamoDB
- Resource Scheduling for App Runner
- Resource Scheduling for Compute Engine
- Resource Scheduling for Cloud SQL
- Resource Scheduling for GKE
- Resource Scheduling for Cloud Run
- Resource Scheduling for Memorystore
- Resource Scheduling for BigQuery
- Resource Scheduling for Cloud Functions
- Resource Scheduling for Artifact Registry
- Resource Scheduling for Azure VMs
- Resource Scheduling for AKS
- Resource Scheduling for Azure SQL
- Resource Scheduling for Azure Functions
- Resource Scheduling for VMSS
- Resource Scheduling for Databricks
- Resource Scheduling for ML Compute
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.