# About Vigil
Vigil is built by Costa Xanthos, started 2026. Founder-led; no team-size embellishments.
## Why Vigil
AI agents are about to be the dominant traffic shape on the internet. Today's control plane — rate limiters keyed by IP, identity providers built around one-human-one-token, observability tools that only describe what happened — was built for a world where requests originate from people clicking buttons.
Agents fan out. One goal becomes thousands of sub-requests. They share keys, repeat themselves, and casually take down their own databases. The infrastructure interprets this as an attack and either crashes or rate-limits everything indiscriminately.
Vigil is the agent-aware data plane. It sits between the agents and the systems they touch and shapes traffic the way agent traffic actually behaves. Per-agent identity. Smart rate limiting that understands which agent is which. Fan-out coalescing for the redundant queries. Blast- radius policies enforced at the proxy, not in the agent's prompt. Signed audit trail for everything that flows through.
The bet is structural: foundation labs can't build this — they live in the LLM call path, not in the application call path. Vigil sits in your VPC, in front of your Postgres, in the part of the stack the labs can't see.
## What we believe
- Agents are not human users, and infrastructure built for humans will fail under their traffic shape.
- The control plane belongs in the data path, not in the agent’s prompt where it can be jailbroken out of.
- Per-agent identity is the load-bearing primitive. Everything else is downstream of it.
- Boring middleware compounds. Audit trails are stickier than dashboards.
- If something goes wrong at 3am, you should be able to replay exactly what an agent did. No exceptions.
## Get involved
Source: https://github.com/constantinexanthos/vigil
Proxy: https://github.com/constantinexanthos/vigil/tree/main/proxy