Open formats, and room for your own checks

Write, change and keep a history of rules, held either as files on your own machine or in a shared library with permissions.

A sealed space to write your own always-the-same check when none of the built-in types can express it.

Bring checks written in the programming language you prefer, run in a sealed space with no access to your files, the network or the clock, capped on memory and stopped if they run too long.

An extension is given nothing by default; each permission is granted explicitly, and separately for an organization, a workspace or a project.

Lets AI coding assistants call Verazyn's checks while they work, over the open Model Context Protocol (MCP) standard.

Verazyn connecting outward to a tool a developer already runs, over that same open standard, so integrating needs no fork of anything.

Runs the checks automatically when code is proposed or merged, at the boundary where work actually gets accepted — the main place rules are enforced.

Reuse an AI tool you already run on your own machine as the model behind Verazyn, so trying it costs nothing extra.

One shared core behind every first-party Verazyn app, with a thin, explicit layer for each place it runs.

The interactive command-line experience — a session that stays open, a live command menu and full-colour output. ON HOLD since 2026-08-18 by project-owner decision.