Rollback by id

Object and zone config. Commit. Rollback by id.

A next-generation firewall / UTM you run on hardware you own. One canonical document. A human commits. Rollback is an id, not a salvage job.

Every committed state is an immutable snapshot, addressed by the hash of its canonical JSON, with a parent pointer and an author. Re-applying an earlier one is the whole of rollback. A commit may arm a confirm window that auto-reverts if you get locked out. The AI layer proposes; a human commits. We do not advertise auto-block.

Object and zone config as one document, not a pile of per-daemon files.
Validate, preview the rendered daemon diff, commit atomically.
Rollback by id. Content-addressed revisions. Re-apply an earlier snapshot.

Teams leaving Sophos UTM: Sophos UTM replacement. Same pf family, commercial orchestration: vs OPNsense / pfSense. Short answers on the FAQ. What is actually built: Platform.