Deterministic
agentic gates
Hold the merge until every check passes.
From prompt to merge
Prompt
Describe the work.
Agent works
The agent writes the code.
Checks run
Action gates run wherever they apply.
Merge when green
No green checks, no merge.
How it works
Installs in your agent
Run npx create-asondy install. It sets up locally inside your coding agent.
Checks every action
Each agent action is checked before it runs, at agent speed.
Blocks bad actions
A bad action is stopped with the reason, so the agent fixes it itself.
Nothing leaves your machine for a check. It runs inline and blocks, so it is not passive logging.
Gates for your workflow
-
Commands & git
Stop destructive commands and pushes to main.
-
Secrets
Keep keys and credentials out of prompts and tool calls.
-
Untrusted input
Flag injected or untrusted content before it acts.
-
Edits
Keep edits in scope and the action gates switched on.
-
Session
Keep the run on track and linked to your dashboard.
-
Code quality
Keep code, tests and prose clean and correct.
-
Security
Check code for unsafe patterns and leaked secrets.
-
UI & UX
Hold interface code to accessibility floors and your DESIGN.md.
Your prompts, files and secrets stay with you. We receive a fingerprint, never the content.
Questions
Does my code leave my machine?
Not for a check in your coding agent: those gates run on your machine. With the cloud connected, asondy.com receives counts, names, ids and hashes. Content sharing and Data gate stay off until the org owner turns them on, Verify and Harness send content only when you run them, and what we receive lists every field.
Does it add token costs?
A credential-gate block adds about 25 tokens for the reason the agent reads. An action the credential gate allows adds 0, since the gate is deterministic and calls no model. If a 200,000-token session meets 10 blocks (an assumption, not a measurement), that is 0.125% of the session on Claude Pro, Max 5x and Max 20x alike.
Does it slow my agents?
Each gate runs in a fresh process per action. In our benchmark on a 16-core linux arm64 machine with Node v22.23.3, the credential gate answered an allowed action in 89 ms at p50 and 96 ms at p95.
Is CI not enough?
CI sees your code after a push. Asondy stops actions that never reach a push, like reading .env, rm -rf or a secret pasted into a prompt, before they run, so it works alongside CI.
Can I add my own rules?
Yes: add a .md file to .asondy/rules/ whose front matter, between two --- lines, sets event, matcher, pattern, message and an action of block or warn, and it runs before each matching tool call.
---
event: PreToolUse
matcher: Bash
pattern: terraform destroy
action: block
message: Ask before destroying infrastructure.
---Prices are on the pricing page, and the supported coding agents are in agent setup.
Get started with Asondy
npx create-asondy install
