Product

Your network sees lanes. Maya sees the vehicles.

Maya rebuilds the network primitives you already trust — identity, authorization, balancing, priority — around the agent instead of the host. All of it payload-blind: Maya never terminates TLS and never decrypts your traffic.

The Maya 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

Maya Substrate

A programmable, agent-identity-aware fabric

Identity-aware fabric

Assigns and carries agent identity in the datapath — east–west (A2A) and north–south (egress), across regions, providers, and geos.

Telemetry, not lock-in

Emits open telemetry (OTLP) into the tools you already run. Maya adds a layer; it doesn't replace your stack.

Policy you control

Deviations are typed, auditable events you route and act on. Enforcement is operator-controlled, per agent — and deliberately observe-first.

Declared once, governed continuously

One view of every agent across clusters, clouds, and regions — Warps in every region, one Loom for the fleet.

Maya, the standalone agentic firewall

Solving problems you can't see yet

1

Declare

one env var per agent
2

Observe

from the wire
3

Deviate

typed event fires
4

Decide

console / callback
5

Enforce

in-line, reversible

Hardest-hitting use case

Per-agent authorized providers — from the wire

Declare which model and 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.

Proven now

Wire-level agent identity, assigned from a single env var — no code, no SDK, no sidecar
Live deviation firing + reversible enforcement on the box
Cross-host agent-to-agent flow, wire-proven
Open telemetry (OTLP) streaming into existing tools
Payload-blind datapath — no TLS termination, no decryption
In-VPC deployment on your data and your keys

Provider & peer deviations, live on the wire
Density & performance ramp toward agent scale
Kubernetes DaemonSet packaging
Bring-your-own-judge (BYOJ) policy, GA
Single-pane console across regions & providers
Setpoint: behavioral posture reasoning over fleet telemetry, human-in-the-loop by default

Items shown as next are under development, subject to change, and not commitments of timing or functionality.

Start an observe-only pilot