Skip to content
Private beta

Run agents with confidence

Prevent agents from going rogue without touching agent code.

Works withClaude CodeOpenClawCodexand most agents you already run.

The firewall for AI agents

Use Senri to control what your agents can and can't do.

dash.senri.io
Console
T
Block npm packages with known CVEsBLOCK
host=registry.npmjs.orgANDpackage.cves>0BLOCK
Block just-published npm packagesBLOCK
host=registry.npmjs.orgANDpackage.age<7 daysBLOCK
Alert on API key in request bodyALERT
method=POSTANDbody~sk-[A-Za-z0-9]{20,}ALERT
Block access to internal networkBLOCK
host=*.internalBLOCK
Allow GitHub API readsALLOW
method=GETANDhost=api.github.comALLOW

One agent or a hundred, every request flows through the same console.

Monitor, control, and scale your agents

Monitor

See what your agents are doing

Traffic streams into the dashboard in real time, and everything stays on the record. Watch an agent live, or replay exactly what it did last Tuesday.

  • Watches HTTP, HTTPS, DNS, and WebSocket traffic in real time
  • Keeps the full history for incident response and forensics
  • You choose what gets logged, where it’s stored, and for how long
All agents
Policy on
VerdictBehavior
ALLOW
claude-code · read a pull request on GitHub
GET api.github.com/repos/acme/app/pulls/42
BLOCK
support-bot · export customer records
POST api.crm.example.com/v2/contacts/export · 4.1k rows
ALLOW
ci-agent · install a trusted npm package
GET registry.npmjs.org/express
BLOCK
ci-agent · install a package published 2 days ago
GET registry.npmjs.org/quick-json-utils
ALERT
claude-code · send an outbound email
POST api.sendgrid.com/v3/mail/send
BLOCK
ci-agent · resolve a known paste site
DNS pastebin.com → NXDOMAIN

Control

Decide what they’re allowed to do

Define policies that allow, alert, or block, and Senri enforces them on every request.

  • Looks at what a request does, not just where it goes
  • Blocks it before it ever leaves the machine

Protects against

supply-chain attackscredential exfiltrationdestructive API callsand more

Senri Managed Policies

Coming soon

A safe default for your whole fleet that keeps known-bad packages, hosts, and actions out — continuously updated by Senri.

example · Supply-chain attack prevention

claude-code · npm install
Senri policy

✓ allowed

Install a trusted package

GET registry.npmjs.org/express

✗ blocked · too new to trust

Install a package published 2 days ago

GET registry.npmjs.org/quick-json-utils

Scale

Give every agent its own rules

A coding agent isn’t a support bot, and their rules shouldn’t match. Scope a policy to each agent’s job, and manage them all from one place.

  • Assigns each agent a policy scoped to its purpose
  • Rolls out changes to the whole fleet from one dashboard
claude-code

policy: engineering

github · npm· prod db

support-bot

policy: support

crm reads· bulk export

ci-agent

policy: build

registries· unknown hosts

one dashboard, a policy per purpose

Use cases

How teams use Senri

Pick the setup that matches how you run agents.

Solo developers

local agents with your keys

senri run -- claude \
--dangerously-skip-permissions
  • Blocks dangerous actions, even with --dangerously-skip-permissions
  • Wraps the agent you already use in one command
  • Catches outbound calls before they disappear into tool or shell logs

Startups

production agents moving fast

docker run senrilabs/firewall:claude \
claude
  • Action-level rules your whole team can review in a pull request
  • No SDK or app rewrite, even for agents you didn’t write
  • Ship policy next to your app in a drop-in container

Security teams

shadow agents across the org

senri setup --auth-key $AUTH_KEY
senri inject
  • Push one policy across the fleet by tag
  • Verify the exact policy version running on each machine
  • Own the full audit trail, and control exactly what gets captured

Security

Built to be trusted with your traffic

Choose where your data lives, how long it stays, and who sees it.

Run it in our cloud, or entirely in yours

Use the hosted dashboard, or self-host the whole stack so that traffic, logs, and keys stay inside your infrastructure and never reach us.

Keep the keys on your machines

The keys that decrypt HTTPS never leave your environment, and you can bring your own.

Log exactly what you choose

Capture is off by default and configured per rule: redact sensitive headers, paths, and bodies, or keep full payloads as evidence. You pick the destination and the retention.

Certifications in progress

SOC 2 Type IIIn progressISO/IEC 27001Planned

Early access

Put a firewall
in front of your agents

We're onboarding a small group of early users. Get early access and we'll help you get set up.