Predict environment (dev, test, stage, prod) and noStop tags from naming patterns, existing tags, and instance config. Accept or reject predictions, optionally sync back to AWS, GCP, or Azure. Tag Coverage widget on the dashboard tracks tagged vs untagged. ZopNight applies smart tags 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
- Smart Tags for EC2
- Smart Tags for RDS
- Smart Tags for EKS
- Smart Tags for ECS
- Smart Tags for Lambda
- Smart Tags for ElastiCache
- Smart Tags for Redshift
- Smart Tags for SageMaker
- Smart Tags for EMR
- Smart Tags for ASG
- Smart Tags for S3
- Smart Tags for EBS
- Smart Tags for CloudFront
- Smart Tags for DynamoDB
- Smart Tags for App Runner
- Smart Tags for Compute Engine
- Smart Tags for Cloud SQL
- Smart Tags for GKE
- Smart Tags for Cloud Run
- Smart Tags for Memorystore
- Smart Tags for BigQuery
- Smart Tags for Cloud Functions
- Smart Tags for Artifact Registry
- Smart Tags for Azure VMs
- Smart Tags for AKS
- Smart Tags for Azure SQL
- Smart Tags for Azure Functions
- Smart Tags for VMSS
- Smart Tags for Databricks
- Smart Tags 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.