Product
Your network sees lanes. Maya sees the vehicles.
Maya rebuilds the network primitives you already trust around the agent instead of the host. A Warp appliance in your VPC. A shim on each host. One environment variable per agent. No code change, no SDK, no sidecar, and no TLS termination.
Agents
Who's running, and what they're doing
The Agentic
Networking Stack
A fair swap: every network primitive, agent-native
IP Address
AID
Agent Identity
who the agent is,
from the wire
DNS
MCP
what it’s
allowed to reach
Load Balancer
aiLB
balances by agent,
not by socket
QoS
aiQoS
priority & budget
per agent
Fabric
Substrate
one identity-aware
fabric, everywhere
Product 01
The Agentic Firewall
Network segmentation at the agent boundary
Your firewall segments networks. Maya segments agents. The boundary moves from the subnet to the agent itself, so every connection is attributed to the agent that opened it, and policy is written per agent rather than per CIDR. Ten agents on one host stop being one IP address.
Deploy
01
Launch a Warp
One appliance instance in your VPC. Your account, your keys.
02
Install Stitch
A host shim on each agent host. Steers agent traffic to the Warp.
03
Declare each agent
Set MAYA_AGENT_ID. Restart it once. That is the onboarding.
How it runs
Declare
one env var per agent
Observe
attributed on the wire
Deviate
typed event fires
Decide
console, SIEM or your engine
Enforce
per agent, reversible*
Onboarding
You do not have to know what is running
Undeclared agent traffic on a steered host is detected and enrolled onto the fabric automatically. You get a roster before you get a policy. The first question after a demo is never "how do I write a rule," it is "what do I actually have."
Enrollment is not authorization. An enrolled agent is visible and attributed, not approved. It carries no declaration until an operator writes one, and Maya governs only what has been declared. Discovery and consent stay separate on purpose.*
Agents
Who's running, and what they're doing
| Agent | Host | Declaration | Tags | Seen |
|---|---|---|---|---|
kyc-screening |
eu-west-1a | 7 of 8 declared | compliance=dora | now |
ledger-core |
us-east-1a | 8 of 8 declared | compliance=sox | now |
forecast-helper
discovered on the wire · enrolled automatically |
us-east-1a | no declaration — nothing to govern | undeclared | 4m |
fraud-scoring |
us-east-1a | 8 of 8 declared | data_class=financial | now |
Reference
The deviation catalog
You declare. Maya observes. Every gap between the two is a typed event with a durable ID, not a log line someone has to go find.
| Type | You declare | It fires when |
|---|---|---|
| PROVIDERS | Model and inference providers this agent may reach | It reaches a provider outside the list |
| REACH | The destination classes it may touch | It leaves its class. The exfiltration signal |
| PEERS | The agents it may talk to | An undeclared A2A edge appears |
| DIRECTIONALITY | Whether it initiates, receives, or both | A receive-only agent starts dialing out |
| EGRESS_BUDGET | A byte ceiling per agent | 75 percent warn, 100 percent critical. Arithmetic, no model in the loop |
| RATE | Connections and bytes per unit time | It goes loud |
| TEMPORAL | The hours it is expected to work | It runs outside its window |
| TTL_LIFECYCLE | How long it should live | It outlives its declared lifetime |
Declaration keys are environment variables on the agent process: MAYA_AGENT_PROVIDERS, MAYA_AGENT_REACH, MAYA_AGENT_PEERS, MAYA_AGENT_DIRECTIONALITY, MAYA_AGENT_RATE, MAYA_AGENT_TEMPORAL, MAYA_AGENT_TTL, MAYA_AGENT_LABELS. Budget is set operator-side, not by the agent.*
Deviations
Declared, then observed. Every gap, typed.
| Type | Agent | Detail | ID | Age |
|---|---|---|---|---|
| PROVIDERS | claims-triage us-east-1a |
declared anthropic, bedrock — reached openai | dv-8c41f0 | 3m |
| PEERS | invoice-reconciler us-east-1a |
undeclared edge to statement-gen | dv-8c3ea7 | 21m |
| EGRESS_BUDGET | disclosure-drafter us-west-2b |
78% of declared ceiling — warn | dv-8c39b2 | 1h 04m |
| TEMPORAL | treasury-sweep us-west-2b |
ran 02:14 — declared window 06:00 to 20:00 | dv-8c2d40 | 6h 12m |
DORA & SOX
Your ICT third-party register, enforced on the wire
Declare each agent's approved providers using the list you already filed. Article 28 asks for documented verification rather than a self-reported questionnaire, and a per-agent deviation record is that evidence. It also answers, without a spreadsheet exercise, which services hold privileged access and which would cause material disruption if they failed.
Agents
Who's running, and what they're doing
fraud-scoring | us-east-1a |
claims-triage | us-east-1a |
ledger-core | us-east-1a |
invoice-reconciler | us-east-1a |
claims-triage
us-east-1a · 10.42.6.18 · pid 3841
Credentials valid. Permissions intact. Nothing was bypassed.
First deviation 2026-08-01T14:22:07 · still firing
In your stack
Maya decides nothing you would rather decide yourself
SIEM and SOAR
Deviations stream out of the northbound API. Splunk, Sentinel or XSOAR decides, the action step posts the verdict back, Maya installs it in-kernel.*
Observability
Per-agent flow and deviation telemetry exports as OTLP. Agent attribution lands next to the traces your LLM tooling already collects.*
Bring your own judgment
Point the stream at Open Policy Agent, a Cedar policy, or an agent of your own. Your engine returns a decision, Maya actuates it.†
Export
Where deviations and per-agent telemetry go
Enforcement
One agent, one provider, reversible
Enforcement acts on an agent's new traffic and nothing else. Not the host, not the subnet, not the other eleven agents sharing that address. Tripping a breaker to switch off one light is what the old boundary forced on you.
Enforcement
Acts on an agent's new traffic. Reversible.
| Agent | Action | Scope | Since | |
|---|---|---|---|---|
claims-triage us-east-1a |
blocking openai | new flows to that provider only | 2m ago | Revert |
disclosure-drafter us-west-2b |
monitoring | — | — | Enforce |
Product spec
Warp
Table 1 · Capabilities
| Form factor | Warp appliance instance in your VPC or VCN. Stitch host shim on each agent host. |
|---|---|
| Datapath | eBPF in the Linux kernel, TC/TCX. Geneve overlay between host and Warp. |
| Agent declaration | MAYA_AGENT_ID in the process environment. No code change, no SDK, no sidecar. |
| TLS | Never terminated. Never decrypted. No certificate to install, no private key to hand over. |
| Deviation types | Eight. See the catalog above.* |
| Enforcement | Per agent, operator controlled, reversible. Acts on new traffic.* |
| Telemetry out | OTLP to your collector. Datadog, Grafana, Splunk.* |
| Northbound API | Deviation stream out, verdicts in. Driven directly by a SIEM, SOAR or policy engine.* |
| Console | Loom. Agent roster, A2A conversation graph, deviation stream, enforcement. |
| Control plane | Weaver, regional. |
| Clouds | AWS and GCP.* |
Table 2 · Host requirements
Maya is a Linux datapath. There is no Windows or macOS host agent.
| Architecture | x86_64. ARM64 untested. |
|---|---|
| Kernel | 4.18 or later. Ships gated at 5.16 today; 4.18 is the real floor once the Geneve bpf_printk is compiled out.* No BTF required. |
| cgroups | cgroup v2 unified hierarchy. Identity derives from the cgroup, so this, not the kernel version, is the gate that decides most platforms. |
| Present on host | tc and bpftool, reachable in the egress network namespace. |
| Packaging | .deb, .rpm, Helm chart for Kubernetes nodes, tarball for air-gapped installs. |
| Warp appliance | Ubuntu 24.04 LTS, kernel 6.1 or later. Ubuntu 24.04 ships 6.8. |
Table 2a · Platform coverage
| Platform | Base kernel | Status |
|---|---|---|
| RHEL, Rocky, Alma 9 | 5.14 | Proven. RHEL 9.8, no code port. |
| Amazon Linux 2023 | 6.1 | Proven. Clears the floor as shipped. |
| Ubuntu 24.04 LTS | 6.8 | Proven. |
| Ubuntu 22.04 LTS | 5.15 | Supported. |
| Debian 12 | 6.1 | Supported. |
| RHEL, Rocky 8 | 4.18 | Kernel clears exactly. cgroup v1 by default is the gate, so it needs a host booted on the unified hierarchy.* |
| Amazon Linux 2 | 5.10 | Kernel clears. Outside beta scope.* |
| Bottlerocket, Flatcar, Talos, COS | 5.10+ | Not supported. Kernel is fine. tc and bpftool are not reachable in the egress namespace. |
| Fargate, EKS on Fargate, Snowpark Container Services | — | Not supported. Fully managed runtimes where you do not control the node. |
On most platforms the kernel is not the deciding factor. The cgroup v2 unified hierarchy is. Any host that boots on it and carries a 4.18 or later kernel is a candidate, whatever the distribution.
Table 3 · Scalability, recommended maximums
| Hosts per Warp | 128* |
|---|---|
| Warps per fabric | 8, across VPC, VCN, region and provider boundaries* |
| Declared agents per Warp | — |
| Forwarding | 3.5 Mpps on a mid-size AWS instance, data plane under 10 percent CPU. Measured until the VPC fabric throttled, so read it as a lower bound.* |
Performance varies with the features enabled, protocol mix and packet size. Recommended maximums are sizing guidance, not hard limits. Contact us for detailed sizing.
Scope
What Maya is not
Not an identity provider. It issues no credentials, authenticates nothing, brokers no access. Fraud detection exists because authentication succeeded. Maya starts where identity ends.
Not a proxy or gateway. Nothing terminates in front of your agent. No hop to add, no endpoint to repoint.
Not an SDK or agent framework. Nothing to import, nothing to wrap, nothing to keep in step with your framework's releases.
Not a log pipeline. Attribution is derived on the wire, not reconstructed from what an application chose to report.
The Maya family
Two models
Pick by fleet size, not by feature list
Standalone Warp
For agents running on VPC and VCN hosts.
Mayajaal†
For scaled-out enterprise fleets, beyond 8 Warps per region.
- Fully distributed agentic mesh.
- Carrier-grade packet forwarding for globally distributed deployments across regions and geographies.
- Agentic-grade policy for managing millions of agents at scale.
- Single pane of management for the entire fleet.
- Highly available, resilient regional control plane. Packets keep flowing, governed, through control-plane events.
Availability
Where and how to get it
| Clouds | AWS and GCP today.* Maya is built for cloud deployments and runs inside your own VPC or VCN. |
|---|---|
| Status | Limited availability.* Design partner slots are open now. Email contact@mayagentic.com. |
| Marketplaces | Planned.† Cloud marketplace listing is the eventual distribution path. |
| Research Edition | Free for universities, colleges and labs.* Programme details, or email research@mayagentic.com. |
| Pricing | On request. Email contact@mayagentic.com with your fleet shape and we will scope it with you. |
Notes
- *
- Beta-stage detail. Availability, capacity and platform coverage reflect the current beta and are expected to expand.
- †
- Under development. Subject to change. Not a commitment of timing or functionality.
On the roadmap
ABR · Agent-Based Routing†
Policy-based routing selects a path from a prefix. ABR selects it from the agent: which region, which provider, which egress point, decided per agent from the declaration you already wrote. Data residency becomes a routing decision rather than an audit finding.
aiQoS, per-agent traffic shaping, is also on the roadmap. See the overview.
The vision
Make every agent visible. Governable. Accountable.
Design partner, or buy. Tell us the shape of your fleet: how many hosts, which cloud, and what your agents are reaching today.