Every change,
logged.
Every change anyone makes in ZopNight is logged with the full request and response: a schedule edited, an override set, a finding remediated. Filter it, search it, export it, and read it in plain words.
Free to start. No card. The playground just needs your work email.
The trail, kept whole.
What was asked, and what actually happened.
Captured at the door
Every create, update and delete is recorded at the gateway, together with the response it got back.
Kept whole
The request body and the response body are both stored, so you see what was asked and what happened. MCP reads keep the request only.
Read in plain words
Cron expressions become sentences, overrides get friendly labels, and failed operations are marked as failed.
Found fast
Filter by action, resource, status or person, search across it, open any entry for the full detail, or export the view to CSV.
The trail auditors ask for.
Including the changes an AI agent made.
- What is logged
- Every create, update and delete made through ZopNight, by a person, a token, or an AI agent. Activity inside your cloud consoles is not part of it.
- AI agents
- MCP tool calls are logged too, reads included, and marked as coming from MCP. A burst of reads at the same moment collapses into one row.
- Evidence
- Export the filtered view to CSV when an auditor asks, for your own SOC 2 or ISO 27001 review.
- Access
- Reading the log is its own permission, so you decide who can see it.
Know what happened without asking around.
Every change made in ZopNight lands on the record. Admins can export it whenever an auditor asks.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.