ZopDay can now copy a database from one GCP Cloud SQL instance to another, with compatibility and permission checks up front and live progress while it runs. A new App Catalog and Starter Templates turn a four-step chart install into a single flow.
New ZopDay: GCP Cloud SQL database migration. Copy a database from one instance to another without leaving ZopDay: pick a source and a compatible target, watch progress live, and the new database appears when it finishes. The source is never touched and credentials are never stored
Improved ZopDay: App Catalog and Starter Templates. Browse installable charts (Postgres, Redis, JupyterHub, and more) and configure them through a form built from each chart's own schema. Starter Templates go a step further and create the cluster, namespace, and environment for you before installing, so a ready-made app takes one flow instead of four manual steps
ZopNight's MCP server now supports write operations: agents connected over MCP can start and stop resources, manage schedules, and drive ZopDay deployments across a surface that grows from 50 to 117 tools, with governance in front of every change. A new Schedule Success Rate widget shows how reliably your schedules are actually firing.
New ZopNight: MCP write operations. Agents connected over MCP can now act, not just look: start and stop resources, manage schedules, and drive ZopDay deployments across a tool surface that grows from 50 to 117. Every write is governed by a per-org permission tier, a global kill switch, and per-tool authorization. Rolling out opt-in per org; reads are unchanged
New ZopNight: a Schedule Success Rate widget on the dashboard reconciles every scheduled run against what was supposed to fire, so a schedule that quietly stopped working shows up instead of hiding
Improved ZopNight: Amazon ECR repositories are now discovered with their AWS resource tags, so tag-based filtering, cost attribution, and rule routing apply to ECR the same way they already do for EC2 and RDS
Improved ZopNight: hover any audit-log or History timestamp to see the precise date and time in your org's timezone, instead of only a relative label like "5 hr ago"
Alerts now cover far more of your cloud activity and arrive in Microsoft Teams as clean, color-coded Adaptive Cards with a one-click link back into ZopNight. You can also export your recommendations to a shareable, two-sheet Excel report straight from the Recommendations page.
New ZopNight: alerts now cover far more of your cloud activity (scheduling, automation, budgets and billing, cost anomalies, remediation, and report exports) and arrive in Microsoft Teams as clean, color-coded Adaptive Cards with a one-click link back into ZopNight; pick which alerts you want in Alerts settings
New ZopNight: export your recommendations to a shareable, two-sheet Excel report (an executive summary plus the full detail) from the Recommendations page. It respects your active filters and de-duplicates savings per resource
ZopNight now offers an AI Gateway: a single, governed front door to your LLM providers, with scoped virtual keys per team or app, budgets to cap AI spend, and cost reports broken down by key, provider, and model. Imported Helm services in ZopDay now show the live public URL they route to.
New ZopNight: AI Gateway. A single, governed entry point for your teams' access to LLM providers: issue scoped virtual keys per team or app, each limited to the providers and models you allow; cap AI spend with budgets so a runaway workload can't blow past its limit; see usage and spend broken down across keys, providers, and models; and govern who can view, create, edit, or delete virtual keys and models through your existing roles, scoped to specific providers when needed
Improved ZopDay: the "How to access" card for an imported (Helm) service now shows the live public URL the cluster's Ingress routes to it; when nothing routes to it, the in-cluster endpoint shows as before
ZopNight now flags Azure VMs that are switched off but still billing for their attached disks, with an estimated cleanup saving. Imported ZopDev Helm services get their own Settings and Overview, and Kubernetes live view now respects per-namespace access.
New ZopNight: flag Azure VMs that are switched off but still billing for their attached disks and public IP, with an estimated cleanup saving
New ZopDay: services imported from a ZopDev Helm chart now have their own Settings and Overview, and stand out on the canvas and in project navigation
Improved ZopNight: Kubernetes live view now respects per-namespace access, so users see only the namespaces they've been granted
ZopNight now connects to Snowflake alongside your cloud providers: guided setup with Key-Pair (RSA) or Programmatic Access Token auth, full inventory discovery, and start/stop scheduling for warehouses to cut idle compute. Recommendations also read more accurately, so idle resources that can only be deleted no longer suggest 'Stop.'
New ZopNight: Snowflake support. Connect a Snowflake account alongside AWS, GCP, and Azure with a guided Key-Pair (RSA) or Programmatic Access Token setup, discover warehouses, databases, tables, stages, pipes, users, and resource monitors, and schedule warehouses on and off to cut idle compute
Improved ZopNight: recommendations now show the real action for every finding. Idle resources that can only be deleted (load balancers, NAT gateways, VPNs, and managed databases and caches) no longer say 'Stop'; each recommendation's safety guidance matches its actual action: delete, resize, or reconfigure
ZopNight now files Jira tickets straight from your cost recommendations — by hand or by policy — with two-way status sync. And Smart Tags replaces the old heuristic auto-tagger with virtual tags derived only from the tagging policies you define, used for cost attribution and never written back to your cloud.
New ZopNight: file Jira tickets straight from cost recommendations — connect Jira in Settings ▸ Integrations (classic or scoped tokens), file by hand or set a policy (e.g. a ticket for every idle resource over $50/mo). Each ticket carries the resource, savings, and suggested fix with a link back, status stays in two-way sync, and re-running never files a duplicate
New ZopNight: Smart Tags — virtual tags derived only from tagging policies you define (a new Tagging domain on the Policy page), used for cost attribution and never written back to your cloud, with a Smart Tags page to review and accept or revoke derived tags in bulk or per resource (replaces the old heuristic auto-tagger)
ZopNight now discovers and manages your Azure AI estate — Azure OpenAI, AI Foundry, Azure AI Search, and Azure Machine Learning — with real cost, metrics, scheduling, and recommendations. Databricks support extends to GCP, joining AWS and Azure, and recommendations can now be filtered by multiple categories at once.
New ZopNight: Azure AI & Machine Learning support — discovers and manages Azure OpenAI, AI Foundry, Azure AI Search, and Azure Machine Learning with real cost and Azure Monitor metrics, start/stop scheduling for Azure ML compute, and new recommendations for idle or over-provisioned AI Search, under-utilized OpenAI throughput, and idle ML compute
New ZopNight: Databricks support extended to GCP — discovery, cost, recommendations, scheduling, and start/stop now work on GCP Databricks workspaces (joining AWS and Azure), with guided account-console setup and a provider chip on every Databricks card
Improved ZopNight: filter recommendations by multiple categories at once (e.g. Rightsizing and Idle together), matching the severity and type filters, with a removable chip per selected category
ZopNight now lets you set a budget for an entire cloud account — not just individual resources or resource groups — with month-to-date spend shown per account. Budgets get a dedicated page under Settings → Budgets, with All / Applied / Not set filters to sort by budget status.
New ZopNight: set a budget for an entire cloud account — not just individual resources or resource groups — with each account showing its month-to-date spend
New ZopNight: budgets get a dedicated page under Settings → Budgets, with All / Applied / Not set filters to sort accounts by budget status
ZopNight extends Databricks support to AWS — connect your AWS Databricks workspace as a separate connection and ZopNight manages it end-to-end, from discovery and cost to savings recommendations and start/stop scheduling. ZopDay also lets admins create and edit Secret and Namespace manifests directly from the Kubernetes resource views.
New ZopNight: AWS Databricks support — connect your AWS Databricks workspace as a separate connection. ZopNight discovers clusters, instance pools, SQL warehouses, jobs, and model-serving endpoints with per-resource cost, recommends savings on idle instance pools and oversized clusters (priced against real pricing), and can start and stop clusters, instance pools, and SQL warehouses
New ZopDay: admins can now create and edit Secret and Namespace manifests directly from the Kubernetes resource views, with safety guards on the apply path to prevent accidental edits
ZopNight now covers AWS Bedrock and GCP Vertex AI end-to-end — discovering and managing the full estate of agents, models, knowledge bases, feature stores, endpoints, and jobs, with per-resource cost and metrics. Schedule recommendations can be applied in one click, and recommendation coverage and accuracy both widen across AWS and GCP.
New ZopNight: full AWS Bedrock support — discovers and manages agents, knowledge bases, guardrails, foundation/custom/imported models, provisioned throughput, flows, and customization, batch-inference, and evaluation jobs, with per-resource cost and metrics
New ZopNight: full GCP Vertex AI support — endpoints, models, indexes, feature stores, datasets, Workbench notebooks, reasoning engines, and training, tuning, batch-prediction, and pipeline jobs, with per-resource cost and metrics
New ZopNight: broader recommendation coverage — license-cost advisories (AWS + GCP), SageMaker GPU-idle endpoints, a revived NAT → VPC-endpoint advisory, and more orphan-cleanup rules (idle dashboards, unused alarms, idle GCP load balancers, abandoned S3 multipart uploads)
Improved ZopNight: apply a Schedule recommendation in one click — no need to recreate the schedule by hand
Improved ZopNight: more accurate recommendations — wider metric coverage (memory, GPU, and database-capacity signals across AWS and GCP) and a steadier 30-day scoring window reduce noisy or premature recommendations
ZopNight extends savings recommendations across your Azure Databricks compute — clusters, instance pools, SQL warehouses, jobs, and model-serving endpoints — covering rightsizing, spot discounts, governance, idle, and orphan cleanup. Idle recommendations also get safer and more accurate, and ZopDay can now show the logs of a container's previous, terminated instance.
New ZopNight: savings recommendations now cover Azure Databricks — clusters, instance pools, SQL warehouses, jobs, and model-serving endpoints — across rightsizing, spot discounts, governance, idle, and orphan cleanup
Improved ZopNight: idle recommendations are safer and more accurate — they default to scheduling instead of a one-shot stop, never suggest terminating active resources, and savings no longer double-count across recommendation types
Improved ZopDay: the cluster log viewer can now show the logs of a container's previous, terminated instance — useful for debugging a crash or restart
Get release notes in your inbox.
We ship every two weeks. Subscribe to receive a short summary of what's new, no marketing, just the changelog in email form.
Multi-cloud automation·Production-ready in 30 min·SOC 2 · ISO 27001·20–60% off the bill, first month·4 platforms · 1 console·Multi-cloud automation·Production-ready in 30 min·SOC 2 · ISO 27001·20–60% off the bill, first month·4 platforms · 1 console·