RUTILE

Run it yourself. Block it yourself.

Give the coding agent a prompt, then change policies in the GABA console.Verdicts happen on the endpoint within 100ms. Every decision lands in the audit log.

Guided tour0 / 4
  1. 1Run the prompt
  2. 2See the block and the alert
  3. 3Turn the policy off
  4. 4Run the same prompt again

Four steps, start to finish

See a block, change a policy, and watch the same prompt get allowed. The tour never clicks for you. It points at a window and tells you what to do.

GABA Governance
https://gaba.solutions

Overview

Online PCs
1
Active Agents
3
Pending Approval
8
Captured Events
37,451
Threats on Date
0
Unclassified Assets
12
Action Queue
Agent Status
Total 11 agents
approved 3
pending 8
Agent · test
✳New agent task
Pick a prompt below and watch GABA govern it in real time.
Verdicts follow the policies set in the GABA console.
Preset prompts
agent: claude.exe · Dev-PC-02 · pendingAuto mode
WHAT YOU JUST SAW

Three things happened at once

Endpoint

Detected by kernel signal, decided locally

The agent's file read is caught as an OS kernel signal. The policy bundle stored on the endpoint decides allow or block within 100ms, and the decision holds even when the policy server is down. On a block, gaba-tray notifies the user.

Console

Policy on behavior, not vendors

Policies attach to behaviors like 'read a sensitive file'. The same action gets the same rule, whatever the AI tool. One toggle pushes it to the endpoint, and an approval workflow handles exceptions.

Audit log

Every decision is sealed

Blocks and allows alike land in an insert-only log. Who, when, what, which policy matched, and the approver are recorded, meeting the audit-trail requirements of ISMS-P and financial supervisory regulation.

Don't block AI. Make it controllable.

See how GABA Governance works in a 30-minute demo.