Developers
Open formats, and room for your own checks
Verazyn's rule format is open, and where the built-in checks cannot express what you need, you can write your own and run it in a sealed space with no access to your files, the network or the clock. The surfaces Verazyn exposes to the tools you already use are listed below with the status of each — which tools and which versions are supported is always named, never assumed.
A simple path to your first successful connection
1. Choose a listed connection
Start with the connection type you need and read its current status. A planned connector is never presented as available.
2. Prepare only what it asks for
Use an account you control and provide only the credential or permission named by that connection. You do not need coding knowledge unless the page explicitly says so.
3. Test with a small example
Run one safe sample, confirm the expected result, and read any error before connecting important work or inviting a team.
Your credentials and data stay within the stated path
Each connection must explain where its credential is stored, which service receives your data, and whether the feature is available, in development, or planned. Never paste a password or secret into ordinary page content.
See it on your own work
Bring your own model key and run your first check. Free to start.
What this covers
Every capability on this page, each with its current status.
Writing rules and keeping their history
In progressWrite, change and keep a history of rules, held either as files on your own machine or in a shared library with permissions.
Learn more→Custom predicates (JavaScript / CEL / Starlark)
AvailableA sealed space to write your own always-the-same check when none of the built-in types can express it.
Learn more→WASM deterministic-check plugin tier
PlannedBring 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.
Learn more→Scoped, user-granted plugin capabilities
PlannedAn extension is given nothing by default; each permission is granted explicitly, and separately for an organization, a workspace or a project.
MCP verification & retrieval surface
AvailableLets AI coding assistants call Verazyn's checks while they work, over the open Model Context Protocol (MCP) standard — including a ready-made skill file that makes an assistant consult the project's rules on its own instead of only when asked.
Learn more→External connectors — bring-your-own integration
PlannedVerazyn connecting outward to a tool a developer already runs, over that same open standard, so integrating needs no fork of anything.
Learn more→CI, PR-bot & native tool integrations
PlannedRuns the checks automatically when code is proposed or merged, at the boundary where work actually gets accepted — the main place rules are enforced.
Learn more→Local agent-CLI passthrough provider
Reuse an AI tool you already run on your own machine as the model behind Verazyn, so trying it costs nothing extra.
Learn more→Client surfaces — editor extension & native app (web · desktop · mobile)
In progressOne shared core behind every first-party Verazyn app, with a thin, explicit layer for each place it runs.
Learn more→Interactive CLI / terminal UI
On the roadmapThe 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.
Learn more→