Skip to main content

Audit and version history

When a regulator, a security team or an incident review asks "what did users see, and who changed it?", the answer should already be on record. In Myop it is.

Nothing is overwritten​

Every save of a component creates a new version. Earlier versions stay as they were, so the full history of any component is always available, and going back is a matter of releasing an earlier version.

Who did what​

  • Who changed it. Each version records the person who made it.
  • Who released it. Each release records who released it and when, separately from who wrote the content.
  • Which integration changed it. Changes made through the management API are recorded with the identity of the API key that made them.

Compare any two versions​

From the CLI, list a component's history and diff any two points in it:

myop log                                   # the component's history, newest first
myop log --author tal@acme.com             # only one person's changes
myop log --env production                  # only what was released to production
myop diff @production latest               # what the next release would change
myop diff at:2026-08-01T12:00:00Z @production   # production now vs. what was there on a date

The same history is available to AI assistants through the Myop MCP tools, so an agent can answer "what changed in this component last week?" from the record.

Learn more​

Versions & Diffs: version references, the CLI and the MCP tools.

Open as MarkdownOpen in ChatGPTOpen in Claude