Works with your stack.
All of it.
Clouds, data platforms, Kubernetes, repos, and the channels your team already reads. Start read-only. Minutes, not months.
Your whole stack, into one layer.
Connect once, then power all three products.
Multi-cloud from day one.
AWS, GCP, and Azure, normalized into one unified view.
A keyless cross-account IAM role, static keys, or temporary credentials. Discovers 121 resource types across every region. Cost from the Cost Explorer API, or your CUR 2.0 export for resource-grain history.
Explore the AWS directory →Service Principal or Workload Identity Federation. Connect one subscription, or the tenant and every subscription follows automatically. 110 resource types. Cost from Azure Cost Management, amortized, so reservations land on the resources that use them.
Explore the Azure directory →One-Click Connect: sign in with Google and zopdev provisions its own service account at the permission level you choose. Or bring a service-account key. 78 resource types. Billing from your BigQuery export, net of credits, the way the invoice bills it.
Explore the GCP directory →Your data platforms, on the same audit trail.
The spend native advisors never see: clusters that never terminate, warehouses that never suspend.
A standalone connection on AWS and GCP (OAuth service principal), and straight through your existing subscription on Azure. Workspaces, clusters, pools, SQL warehouses, jobs, and serving endpoints, discovered, costed, scheduled, and covered by 15 audit rules per cloud.
Explore the Databricks directory →
Connect with a key pair or a personal access token. Warehouses, databases, tables, stages, and pipes, with usage-based cost reconciled against your own ACCOUNT_USAGE views, 20 optimization signals, and warehouse suspend and resume on the same scheduler as everything else.
Explore the Snowflake directory →Every resource, rule, and permission. Documented.
6 platforms, each documented resource by resource with the audit rules that watch it, the schedules that stop it, and the permissions the connection needs.
| Category | AWS | Microsoft Azure | GCP | Kubernetes | Snowflake | Databricks | Total |
|---|---|---|---|---|---|---|---|
| AI & Machine Learning | 25 | 32 | 25 | 1 | 83 | ||
| Networking & CDN | 20 | 21 | 15 | 3 | 59 | ||
| Databases | 15 | 15 | 11 | 41 | |||
| Containers & Kubernetes | 8 | 3 | 3 | 13 | 27 | ||
| Security & Identity | 9 | 3 | 4 | 7 | 1 | 24 | |
| Storage | 6 | 6 | 5 | 3 | 3 | 23 | |
| Analytics & Data Platform | 8 | 8 | 5 | 1 | 1 | 23 | |
| Governance & Operations | 12 | 5 | 3 | 1 | 1 | 22 | |
| Compute | 7 | 5 | 3 | 2 | 3 | 20 | |
| Serverless & App Platform | 4 | 8 | 7 | 1 | 20 | ||
| Messaging & Streaming | 7 | 4 | 11 | ||||
| Documented | 121 | 110 | 78 | 29 | 9 | 6 | 353 |
Documented platforms 6
AWS Cloud Cost Optimization — Connect Your AWS Account to ZopNight
Azure Cloud Cost Optimization — Connect Microsoft Azure to ZopNight
GCP Cloud Cost Optimization — Connect Google Cloud to ZopNight
Kubernetes Cost Optimization Inside the Cluster — Namespaces, Workloads and Waste
Snowflake Cost Optimization — Automatic Warehouse Suspension and Credit Analytics
Databricks Cost Optimization — Clusters, Pools and SQL Warehouses on Autopilot
Every tool in your workflow.
18 connections, grouped by category, all through one connection.
Run it on EKS, GKE, or AKS, ship to it from GitHub, and get Let's Encrypt certificates issued and renewed for you — you keep the DNS zone, zopdev verifies the record.
State changes, schedule failures, budget thresholds, anomaly alerts, and remediation approvals, in the channels your team already reads.
One-click tickets carrying the resource, the savings, and the fix. Two-way status and assignee sync, deduplicated.
One-way cloud IAM import into zopdev teams and roles, from AWS, GCP or Azure. Review before apply; admin rights are never auto-granted.
Govern LLM spend like cloud spend, and let your AI assistant act through a governed MCP server.
Cost in from every provider's native export, business metrics in from your pipeline, reports out as CSV in your display currency.
zopdev as an MCP Server.
326 tools inside any MCP-capable AI client, such as Cursor, Claude and VS Code, over OAuth 2.1 or a personal access token. The 183 read tools cover resources, schedules, costs, recommendations, teams, budgets, and audit logs. The 143 write tools are opt-in per org, split into three risk tiers, need an org-bound token, and are enforced at the gateway before they touch anything. Every write lands in the same audit log as human actions.
Learn about the MCP Server →Run it in your own cluster
27 production Helm charts — one command each, versioned and maintained.
Applications 10
Data sources 17
Don’t see your tool?
New integrations ship every sprint, avg 3 weeks to deliver.