bantay

Under development

Know exactly what your agent just did.

Bantay runs inline between your coding agents and your infrastructure. It logs every file, command, and outbound connection across every developer and CI runner — and stops the ones your policy hasn't allowed.

curl -fsSL bantay.ai/install | sh soon
single static binary · no runtime · <1ms added latency · written in Rust
Product preview · access is coming soon.
overview
coding agents
developer machines
coding agents
CI runners
autonomous agents
scheduled jobs
Bantay
inline · sub-1ms
filesystem
shell
MCP servers
AI agents
sub-agents · model APIs
secrets
↵ deny.secrets
network egress
registry.npmjs.org:443 allowed api.stripe.com:443 ask telemetry.unknown.dev:443 denied
▸ bantay.live watching
[14:08:23] allowed · payments-api · net registry.npmjs.org:443 allowlisted
[14:08:20] ask · payments-api · bash rm -rf node_modules matched ask.destructive
[14:08:14] allowed · web-frontend · bash cargo check
[14:07:51] blocked · data-pipeline · read .env.local rule: deny.secrets
[14:07:44] allowed · payments-api · write src/middleware/auth.ts +34 −12
[14:07:38] allowed · web-frontend · mcp filesystem.list ./workspace
[14:07:29] ask · ci-runners · bash git push origin main remote write
[14:07:12] blocked · scheduled-jobs · read ~/.ssh/id_ed25519 rule: deny.secrets
[14:07:03] allowed · data-pipeline · bash git diff HEAD~1
newest first · tail -f 1,284 events this session
works with any agent that runs a shell · terminal agents · IDE assistants · CI agents · autonomous workers · custom harnesses
katok

It asks before it's too late.

When the agent reaches for something outside your policy, Bantay holds the action and waits for you. No rollback, no postmortem.

⚠ bantay · katok agent · payments-api · ci-runner-04
An agent wants to run:
aws s3 sync ./dist s3://acme-staging --delete
matched rule deny.destructive reason --delete against a remote bucket
allow once [y]· deny [n]· always allow [a] ›
policy

Rules you can read.

One file in your repo. Version it, review it, share it with your team.

▸ bantay.toml
[deny]
paths = [".env*", "**/*.pem", "~/.ssh/**"]
commands = ["rm -rf", "git push --force"]
[ask]
ports = [22, 3306, 5432]
domains = ["*"]
modules
Tanod the local watch daemon
Bakas traces of everything the agent touched
Tahol alerts the moment something crosses a line
Katok approval requests before an action lands
Tala replayable session records
accountability

No action without an owner.

Every file read, command run, and connection opened is attributed to a person, a repo, a branch, and a named agent. Not "an agent did something on a laptop" — a specific action, by a specific agent, running on behalf of a specific engineer, at a specific commit. Reconstructable months later.

100% of agent actions attributed to a person
<1ms added latency per intercepted call
0 runtime dependencies in the agent binary
dashboard

The same record, months later.

Every session your agents have run, across projects and machines, with the rules that actually fired. Read-only by design — approval stays in the terminal.

4 projects · 30 days
2,180 events· 61 held· 14 blocked· 3 detections
held and blocked, 30 days
what your agents reach for
src/** 1,204
package.json 188
registry.npmjs.org 141
infra/terraform/** 94
.env* 14
rules that fired
deny.secrets 14
ask.destructive 31
ask.ports 16
deny.force_push 0never fired
reading rules from ~/acme/payments/bantay.toml · edited by you, in your editor
plans

Plans are taking shape.

We're refining our plans and pricing. Full details will be available before launch.

quickstart

Quickstart

brew install bantay-ai/tap/bantay soon
bantay init generate a policy bantay watch attach to a running agent session
installation preview · Bantay isn't available to install yet
access

Access is coming soon.

We're still building Bantay. Access will open when it's ready.