# zopdev — the continuous CloudOps platform

> zopdev makes cloud optimization automatic: zopnight powers down idle resources, zopday orchestrates deploys, zopcloud turns a repo into a live HTTPS URL.

Source: https://zop.dev/

---

zopdev is a continuous CloudOps platform. Rather than reporting waste on a dashboard for someone to act on later, it acts — on a schedule, across AWS, GCP, Azure and Kubernetes, starting from a read-only connection.

Operating scale:

- $30M+ in annualised cloud spend under management.
- 550K+ resources tracked since launch.
- 220M+ cloud data points processed monthly.
- **353** resource types with coverage across 6 cloud platforms.

Three products:

- [zopnight](https://zop.dev/zopnight) powers down cloud resources nobody is using and right-sizes what is left, cutting non-prod spend by up to 70%.
- [zopday](https://zop.dev/zopday) is the deployment orchestration layer: pipeline runner, dependency-aware deploys, multi-cloud release management. In beta.
- [zopcloud](https://zop.dev/zopcloud) turns a repository into a running service with a live HTTPS URL — no cloud account, no cluster, no YAML.

Pricing is per connected cloud account, not per seat — see [/pricing](https://zop.dev/pricing). What zopdev connects to, and the IAM permissions each provider needs, is documented under [/integrations](https://zop.dev/integrations).

For agents: the machine-readable index is at [/llms.txt](https://zop.dev/llms.txt), the REST surface at [/openapi.json](https://zop.dev/openapi.json), and the MCP server card at [/.well-known/mcp.json](https://zop.dev/.well-known/mcp.json). Developer documentation starts at [/developers](https://zop.dev/developers).