Skip to main content
v1.5 Live Kubernetes cluster state

Your cloud advisor showed you 14%. The other 86% is where the savings live.

450+ rules across AWS, GCP, and Azure. Read-only in five minutes. Every finding is reconciled against your actual bill before it reaches your dashboard.

AWS · GCP · Azure · ISO 27001 · SOC 2 Type II · read-only by default

FMCG enterprises
5 of 20
India's top 20 FMCG enterprises
cloud spend
$15M+
under management
teams
154+
on the platform
trust posture

Read-only by default. Audit-ready by design.

see the product

The architecture canvas.
Every resource, every dependency, mapped.

Switch between Globe and Canvas. Filter by provider, account, region, or category. Click any resource to drill into its config + cost.

Architecture

Globe Canvas
$ Cost
Search resources… 15 resources
PROBLEM
section 1 · the problem

Cloud spend grew.
Cloud governance didn’t.

Three clouds. Eight dashboards. Thirty-plus engineering hours a week on manual start-stop and tag work nobody trusts. The waste isn’t dramatic, it’s quiet, distributed, and continuous.

86% cloud waste invisible to native advisors AWS Trusted Advisor, GCP Recommender, Azure Advisor surface the obvious 14%, the rest compounds.
73% of non-prod cycles wasted A 9-to-6 team uses 50 hours of the 168-hour week. The other 118 hours sit billable.
30+ hrs engineer-time per week, gone Manual start-stop, tag chasing, and dashboard reconciliation, on a stack nobody owns.
  • Non-prod running 24/7 Used 50 hours. Billed for 168.
  • Orphan resources Detached disks, stale snapshots, unattached IPs.
  • Over-provisioned production t3.xlarge at 8% CPU. The team that picked it left.
  • Unclaimed rate optimisation Hybrid Benefit, RIs, Savings Plans untouched.
  • Compliance drift IAM, encryption, public-access misconfigs.

Found. Fixed. Audited. — Every dollar your cloud advisor missed.

SOLUTION
section 2 · three engines

Three engines.
One workspace.

Lens reads your bill and finds the waste. Smart Scheduling captures non-prod cycles. Tide sizes production to actual demand. CDCR keeps it all fixed.

Recommendations by Lens

Finds the waste.

450+ rules across AWS, GCP, Azure. Eight categories — idle, right-sizing, schedule, orphan, compliance, discount, security, reliability. Every finding ships with the metric, the threshold, the action, and the dollar. No black-box ML.

AWS · GCP · AZURE

Smart Scheduling

Captures non-prod cycles.

Cron-based, dependency-aware, per-timezone. 30+ resource types — VMs, K8s, SQL, Databricks. Storage wakes before compute. Production-safe overrides.

30+ RESOURCE TYPES

Smart Autoscaling by Tide

Sizes for the moment, not the peak.

ASGs, scale sets, AKS pools. 30–40% compute reduction on eligible workloads. Three modes — monitor → recommend → autopilot. You decide where it gets the keys.

MONITOR → RECOMMEND → AUTOPILOT
DEPTH
section 3 · features

The depth behind
the three engines.

Nine more features you’d otherwise build internally — reports, showback, tagging, inventory, budgets, ownership, AI-native access, audited remediation, the cross-cloud map. All ship inside the same workspace, on the same audit trail.

01 · REPORTS & DASHBOARDS

Boardroom-ready cost reports.

Three Reports tabs — Organisation, Teams, Tags. Cost Flow Sankey, four columns deep. Cost anomaly detection across five dimensions. Four dashboard presets — Executive, Engineering, FinOps, All Widgets.

ORG · TEAMS · TAGS

02 · SHOWBACK

Every dollar, attributed.

Two attribution dimensions — team and tag. Shared resources split equally across owning teams. Reconciled to actual billing (Cost Explorer, Cost Management, BigQuery), not rack rate.

TEAM · TAG · RECONCILED

03 · AUTO-TAGGING

Tag every resource, without the ticket.

Predicts environment and stop-eligibility on every untagged resource. Rule-based — naming patterns, existing tags, instance config. We replaced ML with rules in production. Accept, reject, sync back to AWS / GCP / Azure.

PREDICT · ACCEPT · SYNC

04 · ALL-RESOURCES INVENTORY

Search, filter, act on every resource — three levels deep.

380+ resource types across AWS, GCP, Azure. Grouped account dropdown, cascade filters, nine type categories. Parent-child nesting (cluster → nodepool → VM). Bulk start / stop with a sticky selection banner.

380+ TYPES · 9 CATEGORIES · 3 LEVELS

05 · TEAM BUDGETS

Budgets that compute themselves.

Budget per team, per resource group, or per resource. Spend computed live from your actual cost records. Status colour-coded: green, yellow, red. Threshold-crossing alerts fire to the team’s channel.

GREEN · YELLOW · RED

06 · RESOURCE OWNERSHIP

Who created this? Already answered.

Daily identity-sync derives the IAM principal that originally created each resource — from CloudTrail, GCP Audit Logs, Azure Activity Logs. Human callers separated from service accounts. The “who owns this orphan disk?” question, finally answered.

CREATOR · LAST WRITE · HUMAN VS SERVICE

07 · MCP / AI-NATIVE

Your cloud, in your AI editor.

A Model Context Protocol server with 43 read-only tools — resources, schedules, costs, recommendations, teams, budgets, audit logs. Connect Claude Desktop, Cursor, Codex, or Claude Code with one PAT. Read-only by default; writes rejected at the protocol layer.

AI-NATIVE · 43 TOOLS · READ-ONLY

08 · AUTO-REMEDIATION

Certified rules. One click. Zero database touches.

One click applies certified recommendations. A four-step check runs every time — precondition → approval → cloud action → validate. Customer databases stay with your DBA team: RDS, Aurora, Cloud SQL, ElastiCache, Azure SQL, Postgres, MySQL — never touched.

CERTIFIED · DBS UNTOUCHED

09 · ARCHITECTURE · ATLAS + CANVAS

Map every cloud. Trace every dependency. Automatically.

Atlas — searchable inventory of 380+ resource types across AWS, GCP, Azure. Canvas — interactive dependency graph, live edges auto-derived from cloud metadata. Subnet swimlanes, security-group hubs, VPC peering, attached storage. The map maintains itself.

ATLAS · CANVAS · LIVE

section 4 · cdcr

The fix that stays fixed.

CI/CD made code continuous. CDCR makes your cloud continuous. So the fix stays fixed.

01
DETECT
Detect, continuously.

Drift on K8s clusters and schedules. Cost regressions caught by anomaly detection across five dimensions, org, cloud account, resource group, resource, team. Expired schedule overrides. Newly untagged resources. Compliance gaps that quietly reopened.

02
CLASSIFY
Classify, by impact.

450+ audit rules across AWS, GCP, and Azure. Every finding scored by severity and projected billing impact, so drift on a production resource ranks above an idle dev box on the work-list. The queue reflects the actual stakes, not just the rule count.

03
REMEDIATE
Remediate, continuously.

Auto-fix where it’s safe, tag application from accepted Tagger predictions, schedule enforcement, idle resources stopped, scale-to-zero on certified workloads, pause on certified service-tier targets. Guided remediation for the rest, with confidence and complexity scores up front. Production writes are admin-gated, scoped, and fully logged. Customer databases are explicitly excluded from mutation.

04
VERIFY
Verify, every action.

Every action lands in the audit trail, actor, timestamp, dollar delta where applicable. Quarterly review reads measurable outcomes, never forecasts.

continuous
ACTIVE
section 5 · proof

$14,820/month recovered in 4 weeks.
Production untouched.

Anonymised Fortune 1000 estate. 2,140 resources across 3 Azure subscriptions. Read-only connect, then four weeks, line-by-line, reconciled against actual billing.

section 6 · vs. native tools & finops platforms

We find. We execute. We prove.

  Azure Advisor CloudHealth Flexera Spot.io ZopNight
Azure rules15~50~90-147
Multi-cloud (AWS + GCP + Azure)-
Cron scheduler--partial-
Dependency sequencing----
Autoscale on prod---partial
Continuous remediation (CDCR)---partial
Automated execution---partial
Kubernetes + Databricks-partialpartialpartial
India residency----

* AWS Trusted Advisor and GCP Recommender exhibit the same 14%-only pattern as Azure Advisor.

section 7 · pricing

Outcome-aligned pricing.
Pay when the bill drops.

Plan Free Team Growth Enterprise
Best for Audit your cloud, read-only Up to $50K/mo cloud spend Up to $500K/mo cloud spend Custom + outcome share
Tailored Recommendations✓ all 450+ rules
Sequenced Scheduling-
Autoscaling engine--
CDCR auto-remediation (safe)--
CDCR guided remediation + audit forwarding---
MCP server (Claude / Cursor)
Multi-cloud (AWS + GCP + Azure)1 cloud
India residency / VPC deploy---
SAML SSO, RBAC, SOC 2 pack--
Pricing $0 $199/mo* $799/mo* Platform fee + % of realised outcomes
  Connect a cloud → Start trial → Start trial → Talk to platform sales →

No outcomes, no charge on the variable. Verified against your actual AWS / GCP / Azure billing.

section · stakeholder grid

Built for every seat in the room.

01

CFO / FinOps

Predictable variance. Verified against your bill.

stops the Friday "why is the bill up" meeting.
02

CTO / CPO

One platform. Three clouds. Four lifecycle stages.

stops the six-tool stack that doesn't talk.
03

VP Engineering

Ship product, not platform overhead.

stops the platform project "almost done" since Q1.
04

Platform / SRE

Cross-cloud inventory. CDCR auto-fix.

stops 3 AM pages from dashboard ↔ ticket gaps.
05

InfoSec / Audit

Read-only by default. Append-only audit.

stops "yet another vendor with broad write access."
savings calculator

How much is your cloud wasting right now?

Most teams overspend by 30–60%. Find out your number in 30 seconds.

ZOPNIGHT · ET–42 · SAVINGS
SELECT CLOUD PROVIDER
faq

Things teams ask before they sign.

Will ZopNight ever touch production?

Not until you say so. ZopNight runs read-only by default, every write operation rejected at the credential layer. To enable writes, you opt in per environment, scope the IAM policy, and tag the resources eligible. The audit trail captures every approval. Most customers run six to twelve weeks read-only before flipping the first scope.

What permissions does ZopNight need?

Read-only roles on AWS, GCP, or Azure, full IAM policy published in the docs. No service accounts created in your tenant; no agents installed; no proxy in the data path. For optional auto-remediation, a scoped write policy (also published) covers only the resource types enabled in the override settings.

What happens during an incident?

All scheduled actions pause. ZopNight stops issuing writes the moment a registered incident channel signals an open incident, Slack, Teams, GChat, webhook. Resume is one click; the audit trail records the pause and the resume.

How is this different from native AWS / GCP / Azure scheduling?

Native schedulers are single-cloud, single-resource-type, and operator-defined. ZopNight is multi-cloud, dependency-aware, and rule-derived. The cron syntax is the surface; underneath, the engine knows storage wakes before compute, knows that an EKS scale-down waits for the StatefulSet quiesce, knows the override expires Friday.

How long until the bill drops?

First findings in five minutes. First safe auto-fix windows in week one. Measurable bill movement by end of week four, the Fortune 1000 case study above ($14,820/mo recovered in 4 weeks) is the documented pattern, not the ceiling.

Is there a free tier?

Yes. The Free plan covers all 450+ recommendation rules on one cloud, read-only, with the MCP server included. No credit card. The pilot runs 30 days; after that, you stay on Free or upgrade, no auto-bill, no surprise charge.

See what 4 weeks finds
in your cloud.

See. Find. Fix. Automatic.

Connect read-only. First findings in five minutes. Charges hit only after your bill drops on the Enterprise tier — Free, Team, and Growth plans are flat-fee.

5 min connect time
7 min first remediation
42% average waste cut, 30 days
Three products. One platform.
Indie devs · MVP teams Platform engineers · Scale-ups FinOps leads · CFOs · Enterprises ◀ you are here
ZopCloud ZopDay ZopNight
We host. You push. Your cloud. Our platform layer. Continuous governance + cost optimisation.
→ zopcloud.com → zopday.dev → zopnight.com

No re-platform when you grow. No surprise bill when you scale. No drift when it’s running. Looking at the platform? → zop.dev

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001 · zero-trust· 30% average cloud cost cut· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001 · zero-trust· 30% average cloud cost cut· 4 platforms · 1 console·