Introduction

What is ZopDay

ZopDay is the platform engineering layer that AWS, GCP, and Azure don’t ship with. It is a control plane (not a proxy) that sits on top of the cloud account you already own and gives your team push-to-deploy speed without the six-month internal-platform project.

It runs on your cloud, with your keys, with your audit trail. Workloads execute as standard Helm releases on your clusters. If you leave, the workloads stay where they are.

ZopDay Deployment Spaces; registered clusters across GCP, AWS, and Azure, one control plane.

Three stages, one workspace

ZopDay covers the whole lifecycle in three coordinated stages:

• Landing Zone: Day 0. Production-grade clusters, datastores, and networks. 4–7 minutes from create to kubectl get nodes. EKS, GKE, AKS via one wizard with identical hardening defaults. RBAC, Network Policies, Pod Security Standards, autoscalers applied on provision.
• Deployment: Every day. Push code → production via Helm. No Dockerfile required. ZopDay auto-builds from your repo. Security scans on every build. DORA-grade visibility. One-click rollback. Sensitive env vars stored in your cloud-native secret manager (AWS Secrets Manager, Google Secret Manager, Azure Key Vault); never ours.
• Live State: Every minute. Real-time K8s state across every connected cluster. 21 resource pages with detail drawers. Cluster reachability probed every 60 seconds. Inactive cluster gates cleanly; no cryptic SDK errors.

Trust posture

• BYOC: your AWS, GCP, or Azure account. We never host your workloads.
• Cloud-native secrets: env vars land in your cloud’s secret store, never ours.
• Control plane, not a proxy: traffic never passes through ZopDay.
• ISO 27001:2022 and SOC 2 Type II: independently audited.
• IRDAI ICS 2023 and DPDP Act 2023: controls applied by default for India workloads.
• GCP India (Mumbai): MeitY-empaneled deployment available.
• Built on GoFr (Apache 2.0): open-source roots, no proprietary runtime.

Who uses ZopDay

McAfee runs platform engineering on ZopDay in production; 12 AWS accounts, 48 Kubernetes clusters, 1,000+ req/sec sustained through the platform. Same wizard, same hardening defaults, same audit trail across every cluster.

What you get on day one

• Multi-cloud landing zone with three clouds wired in one wizard.
• Dependency-aware deploy pipelines with rolling, canary, and blue/green strategies.
• Auto-built container images; no Dockerfile required.
• One-click rollback with secrets that stay in your cloud.
• Append-only audit trail forwardable to your SIEM.

Where to next

• Quickstart: sign in, connect a cloud account, register a cluster, and ship your first deploy.
• Pipelines: how the deploy pipeline works, from trigger to live URL.
• Rollbacks: one-click rollback semantics, secret handling, and safety gates.