Change control

Every change has an author, and a way back.

Each change creates a version with its author, its reason and a diff. Edge nodes only apply configuration the control plane has signed, in under a minute, and any earlier version can be restored in one step.

Create account How changes reach the edge

OPENWAFChange control

Every change on the record, and one step back

Each change creates a version with its author, its reason and a diff. Nodes apply the signed document in under a minute, and any earlier version can be restored in one step.

History and diff

See who changed what on each site, when and why.

One-step rollback

Restore an earlier version of a site with one command.

Propagation

Watch every node apply the new version, in under a minute.

Versioned, signed configurationEvery change is a signed version you can undo.

Each version records who made it and why, and comes with a diff.

History and diff
Every change creates a new version you can compare with earlier ones.
One-step rollback
Go back to a previous version of a site’s configuration in one step.
Mandatory change reason
Every change records why it was made.
Signed with Ed25519
Edge nodes only apply configuration documents with a valid signature.
Last-known-good
If the control plane can’t be reached, nodes keep serving the last valid configuration.
Under a minute
Changes reach all edge nodes in under a minute.

Audit log and usageKnow who changed what, and show your clients.

An audit log of every change, the version each node runs and daily usage per site.

{"actor": "user:3b9f…e21a",
 "action": "record.create",
 "target": "www.example.com",
 "data": {"channel": "mcp", "version": 15,
          "from_version": 14,
          "reason": "Point www at the new server"},
 "at": "2026-10-27T10:02:41Z"}

Audit log
Who changed what, on which site, when and why, including changes made through MCP.
Propagation
The version each edge node applies, so you know when a change is live.
Usage telemetry
Daily requests, blocked requests, bytes and DNS queries per site.

FAQ

Questions about changes

What happens if your control plane goes down?

Edge nodes keep serving with the last valid, signed configuration they received. You can’t make changes until it is back, but traffic keeps flowing and stays protected.

Can I undo a change?

Yes. Any earlier version of a site’s configuration can be restored in one step, as a new version, from the dashboard, the API, the command line or MCP (revert_zone).