Make your network readable by agents
Agentic network operations built on eBPF:
fleet-wide, real-time, and incredibly cost-efficient
curl -fsSL https://yeet.cx | shLinux only | Manual install | Read the docs
┌─ yeetd ──────────────────────────────────────────┐ │ │░ ┌─────────────┐ │ ┌────────────────┐ ┌─ Linux kernel ───┐ │░ │ │░ ask │ │ │ │ │ │░ │ you / agent │░───────>│ │ V8 isolate │ ────> │ eBPF │ │░ │ │░ │ │ │ │ │ │░ └─────────────┘░ │ └────────────────┘ └──────────────────┘ │░ ░░░░░░░░░░░░░░░ │ │░ └──────────────────────────────────────────────────┘░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
New capabilities for your coding agents
With yeet, your live network traffic becomes the agent’s context for operating.
Claude Code v2.1.287 Opus 5 · Claude Max ~/code/api
- the name behind every TLS connection, read from the handshake, with no DNS to intercept
- raw packets on any interface, tunnels included, with the protocol tree and hex in the terminal
- HTTP, gRPC, SQL and Redis decoded off the wire, inside TLS too wherever the process uses OpenSSL
- every connection, in or out, tied to the process that made it and flagged when it leaves your network
- request rate, errors and latency per container, from inside its network namespace, no sidecar and no code change
“yeet has been one of the biggest keys to our development success at Kairos. When you’re building trading infrastructure, you need tools you can trust to keep up, and yeet has done that from day one.
The technology powering it is seriously impressive, and it’s versatile enough that we keep finding new ways to use it across our stack. It’s become a core part of how we build, and I’d recommend it to any team working on serious infrastructure.”
“yeet is an essential platform for us at Pickle in optimizing and monitoring network performance, an essential bottleneck that exists onboard every robot, between every robot, and across our growing footprint of distributed cloud and edge compute.
We prefer to build in-house, so we brought in yeet to let our engineers write their own systems for network performance issues that our existing telemetry could not explain. We find root causes in minutes.
Setup was fast, and yeet lets us replace millions of dollars of engineering and production expenses with tools our engineers build. Today, yeet is part of our daily workflow, continuously profiling the performance of our fleet.”
Use yeet for…
Fleet operations
Improve cluster health via ambient limit checks across clusters, setting up ephemeral triggers where things look suspicious.
Incident triage
Network incidents are the most challenging. Instead of digging through a thousand dashboards, generate specific views on the fly.
Sovereign troubleshooting
Pre-install yeet in on-prem deployments so customers can self-diagnose network issues and relay answers back.
Use yeet when you don’t know where the problem is
Network problems live below the layer your tools were built to watch. yeet lets the agent go read that layer directly.
┌─ your app ─────────────────────────────────────────┐ │ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │░ │ │ dashboards │ │ logs │ │ traces │ │░ │ └─────────────┘ └─────────────┘ └─────────────┘ │░ └────────────────────────────────────────────────────┘░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ - - - - - - - - your tools stop here - - - - - - - - ┌─ Linux kernel ─────────────────────────────────────┐ │ │░ │ ┌─────────────────────┐ ┌─────────────────────┐ │░ ┌────────────┐ yeet │ │ connections │ │ DNS │ │░ │ your agent │░────────>│ │ who, where, when │ │ every lookup │ │░ └────────────┘░ │ └─────────────────────┘ └─────────────────────┘ │░ ░░░░░░░░░░░░░░ │ │░ │ ┌─────────────────────┐ ┌─────────────────────┐ │░ │ │ retries │ │ packets │ │░ │ │ never logged │ │ any interface │ │░ │ └─────────────────────┘ └─────────────────────┘ │░ │ │░ └────────────────────────────────────────────────────┘░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
You don’t pay per event
Your kernel doesn’t bill you per event, and neither do we.
Free until you have a fleet. Three hosts, no charge.
curl -fsSL https://yeet.cx | shIt’s just Linux
yeet is a daemon on a Linux host. It runs the same on AWS, GCP and Azure, on Kubernetes nodes, in Docker or on bare metal.
Nothing about your networking changes: no sidecar, no proxy in the path, no CNI to swap. Your security or ours? Yours. yeet runs inside your account and your VPC, inherits the controls already there, and the data it reads stays on the host. Any agent that can run a command works with it.
AWS
GCP
Azure
Kubernetes
Docker
Prometheus
Grafana
Slack
GPT
Claude
Jev
Gemini
┌──────────────────────────────────────────────┐ │ Google Chrome │░ │ V8 against the DOM │░ │ ╭─ browser process ────────────────────────╮ │░ │ │ DOM · fetch · WebGL · WebRTC │ │░ │ ╰──────────────────────────────────────────╯ │░ │ ^ │░ │ ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄ supervises ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄ │░ │ v │░ │ ╭─ child process ──────────────────────────╮ │░ │ │ ┌─────────────────┐ ┌─────────────────┐ │ │░ │ │ │ * v8 isolate │ │ * v8 isolate │ │ │░ │ │ │ gmail.com │ │ github.com │ │ │░ │ │ └─────────────────┘ └─────────────────┘ │ │░ │ │ ┌─────────────────┐ ┌─────────────────┐ │ │░ │ │ │ * v8 isolate │ │ * v8 isolate │ │ │░ │ │ │ stripe.com │ │ youtube.com │ │ │░ │ │ └─────────────────┘ └─────────────────┘ │ │░ │ ╰──────────────────────────────────────────╯ │░ └──────────────────────────────────────────────┘░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
┌──────────────────────────────────────────────┐ │ yeet │░ │ V8 against your kernel │░ │ ╭─ yeetd daemon ───────────────────────────╮ │░ │ │ eBPF · connections · DNS · packets │ │░ │ ╰──────────────────────────────────────────╯ │░ │ ^ │░ │ ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄ supervises ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄ │░ │ v │░ │ ╭─ child process ──────────────────────────╮ │░ │ │ ┌─────────────────┐ ┌─────────────────┐ │ │░ │ │ │ * v8 isolate │ │ * v8 isolate │ │ │░ │ │ │ httpwatch.tsx │ │ tcpwalk.tsx │ │ │░ │ │ └─────────────────┘ └─────────────────┘ │ │░ │ │ ┌─────────────────┐ ┌─────────────────┐ │ │░ │ │ │ * v8 isolate │ │ * v8 isolate │ │ │░ │ │ │ wssnoop.tsx │ │ pktscope.tsx │ │ │░ │ │ └─────────────────┘ └─────────────────┘ │ │░ │ ╰──────────────────────────────────────────╯ │░ └──────────────────────────────────────────────┘░ ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Security
The computation happens below the agent.
Your agent declares what it wants and gets the result. The intermediate computation (the raw kernel stream, the bytes a tool reads) stays inside the isolate and never crosses into the agent. Each tool is sandboxed the same way your Google Chrome sandboxes the web: a V8 isolate with no path to the network.
Build custom infrastructure
With access to runtime system data and yeet’s build primitives, your agents become capable of building a new category of infrastructure tools. From protocol debuggers to test infrastructure, every new tool in your stack is now custom-built to your needs.
Agentic network operations in under 60 seconds
curl -fsSL https://yeet.cx | shLinux only | Manual install | Read the docs