The core idea
Your network sees lanes. Maya sees the vehicles.
Current problem
Sees lanes, not vehicles
Solved with Maya
Every agent identified from the wire · payload-blind
Deviation detected
declared agent → unlisted provider
The core idea
Current problem
Sees lanes, not vehicles
Solved with Maya
Every agent identified from the wire · payload-blind
Deviation detected
declared agent → unlisted provider
How Maya compares
| Capability | Maya | Firewall / NDR | Identity / IAM | Service mesh |
|---|---|---|---|---|
| Per-agent identity from the wire | ✓ | — | ◐ | — |
| Payload-blind (no TLS termination) | ✓ | ◐ | n/a | — |
| East–west (A2A) + egress governance | ✓ | — | — | ◐ |
| No code, no SDK, no sidecar | ✓ | ✓ | ◐ | — |
| Provider / peer authorization policy | ✓ | — | ◐ | — |
| Telemetry into your existing tools | ✓ | ◐ | ◐ | ✓ |
| Built for agent scale, in-line | ✓ | ◐ | — | ◐ |
◐ = partial / adjacent capability
The agentic landscape
Autonomous agents now open connections on their own: calling model and inference providers, calling other agents, and reaching services no human requested. This traffic is exploding, and it is concentrated where the stakes are highest.
40%
of enterprise apps embed AI agents by end of 2026
~47%
of banking & insurance already run agents in production
~1 in 3
enterprises have any AI-specific security controls
Sources: Gartner, IDC, S&P Global / McKinsey, 2026 industry surveys
Why can't the network stack you own answer this? See the strain, on Solutions.
The standalone agentic firewall
1
one env var per agent
2
from the wire
3
typed event fires
4
console / callback
5
in-line, reversible
Hardest-hitting use case
Declare which model & inference providers each agent may reach: the same list as your ICT third-party register. When a declared agent reaches an unlisted provider, Maya fires a typed deviation. Built for financial services under DORA and SOX.
AI, watched by AI
Deterministic checks resolve as exact arithmetic on the box; behavioral risk is reasoned over by an LLM you choose, running in your own account. Human-in-the-loop by default. Every mitigation is agent-scoped and reversible, so the blast radius is one agent, not your fleet.
The full agent-native stackThe team
Distributed systems, networking & cloud. Built DPI, QoS & IPS in Cisco IOS and L2/L3 forwarding in Juniper JUNOS; cloud infra at IBM and Oracle (OCI).
A crew out of Cisco: forwarding planes, deep-packet inspection, and carrier-grade networking in our bones.
Prior startup exit experience across the team, including security pioneers (FireEye lineage).
Cisco · Juniper · IBM · Oracle (OCI) · FireEye
We're opening a small number of design-partner slots in financial services. Run Maya observe-only against your agent traffic and see what your network can't.
Start a conversation