ZopNight recommends the optimal instance type based on actual usage patterns, not vendor defaults or guesswork. ZopNight applies rightsizing 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
- Rightsizing for EC2
- Rightsizing for RDS
- Rightsizing for EKS
- Rightsizing for ECS
- Rightsizing for Lambda
- Rightsizing for ElastiCache
- Rightsizing for Redshift
- Rightsizing for SageMaker
- Rightsizing for EMR
- Rightsizing for ASG
- Rightsizing for S3
- Rightsizing for EBS
- Rightsizing for CloudFront
- Rightsizing for DynamoDB
- Rightsizing for App Runner
- Rightsizing for Compute Engine
- Rightsizing for Cloud SQL
- Rightsizing for GKE
- Rightsizing for Cloud Run
- Rightsizing for Memorystore
- Rightsizing for BigQuery
- Rightsizing for Cloud Functions
- Rightsizing for Artifact Registry
- Rightsizing for Azure VMs
- Rightsizing for AKS
- Rightsizing for Azure SQL
- Rightsizing for Azure Functions
- Rightsizing for VMSS
- Rightsizing for Databricks
- Rightsizing 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.