Skip to main content
developers · build

Build on ZopNight.
Automate everything.

API-first. MCP-native. Terraform-ready. ZopNight is built for teams who'd rather automate than click.

Four ways to build on ZopNight.

Whether you're scripting a one-off audit or embedding cloud cost intelligence into your platform, there's a supported path.

REST API

Full programmatic access to your cloud findings, remediations, accounts, and showback data. JSON over HTTPS. Bearer token auth. Paginated, versioned, and stable.

Available API docs →

MCP Server

ZopNight publishes an MCP Server that gives Claude, Cursor, and any MCP-compatible AI client live access to your cloud findings and remediation controls.

Available MCP docs →

Terraform Provider

Declare ZopNight schedules, tagging policies, and notification rules as code. Works alongside your existing AWS, Azure, and GCP Terraform configurations.

Available Terraform docs →

Webhooks

Push-based event delivery for findings, remediations, and schedule executions. Subscribe to specific event types. HMAC-signed payloads. Retry with exponential backoff.

Coming soon Join waitlist →

ZopNight speaks LLM.

ZopNight publishes an MCP Server that lets Claude, GPT-4o, and any MCP-compatible AI client query your cloud state, surface waste, and run remediations, all from a chat window. No dashboards required.

# Ask your AI client to query ZopNight findings
Tool call: zopnight://findings
  ?account=aws-prod
  &min_impact=500
  &status=open

# Returns: 14 findings · total impact $38,400/mo
# Top finding: 47 idle EC2 instances · $12,800/mo

REST API. Clean, versioned, stable.

Every ZopNight capability is available over HTTP. Authenticate with a Bearer token. Rate limits are generous, 1,000 req/min on paid plans.

Base URL
https://api.zop.dev/v1
  • GET /findings List all findings, filterable
  • POST /remediations Apply a remediation action
  • GET /accounts List connected cloud accounts
  • GET /showback Department cost showback data
  • GET /recommendations Rightsizing recommendations
  • POST /schedules Create a resource schedule
Get your API key →
Quick example
# List top findings in aws-prod
curl -X GET \
  'https://api.zop.dev/v1/findings' \
  -H 'Authorization: Bearer $ZOPNIGHT_TOKEN' \
  -G \
  -d 'account=aws-prod' \
  -d 'min_impact=500' \
  -d 'status=open' \
  -d 'limit=10'

# 200 OK
{
  "findings": [...],
  "total_impact": 38400,
  "count": 14
}

Infrastructure-as-Code
for your savings.

Declare ZopNight schedules, tagging rules, and alert policies alongside your existing Terraform. Peer-reviewed. Diff-able. Rolled back when things go wrong.

The ZopNight Terraform Provider is published to the Terraform Registry. Works with Terraform 1.3+ and OpenTofu.

main.tf
terraform {
  required_providers {
    zopnight = {
      source = "zopdev/zopnight"
      version = "~> 1.0"
    }
  }
}

resource "zopnight_schedule" "dev_off" {
  name = "dev-environments-off"
  description = "Stop dev EC2s after hours"
  account = "aws-dev"
  action = "stop"
  cron = "0 20 * * 1-5"
  timezone = "America/Los_Angeles"
  target_tags = {
    Environment = "dev"
    AutoStop = "true"
  }
}

We build in public.

Source of truth for what we're shipping, what we've shipped, and what you told us to ship next.

Start building in 5 minutes.

Get an API key, connect your first account, and run your first query. No infrastructure required.

Stop watching the waste.
Start cutting it.

See. Find. Fix. Automatic.

Connect your first cloud account in under 5 minutes. See your first remediation in under 7. No credit card required.

REST + SDK Python, Go, TypeScript
webhooks for every action
MCP live in Claude & Codex
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·