Trusted Runtimes for Infrastructure Agents

Connect agents to your infra in seconds.
Built-in identity. Zero secrets.

Beams runs each agent in an isolated Firecracker VM with built-in identity.
Connected to your infrastructure and inference services — no secrets, no IAM wrestling.


          

Connects agents to inference endpoints without secrets. Start coding now, bring your own inference later.


          

Check out the repo, spin up Claude, and test against staging or production without exposing secrets.


          

Run agentic jobs against real infrastructure in an isolated VM. Zero risk of credential leakage.

Break the AI adoption barriers.

Security and IAM are the main adoption blockers for running agents in production. Launching agents today means stitching together IAM, infra, and secrets by hand.

Run agents with identity security

Today, agents impersonate users and services with unchecked permissions and access to API keys and secrets.

Gain visibility into agent activity

Today's tooling are not equipped to audit agent activity and access to infrastructure without the extra hassle.

Cut operational drag

Teams end up needing to build their own container or VM workflows to run agents securely across their infrastructure.

Start with our inference endpoints or add your own

Beams start with limited access to OpenAI and Anthropic subscriptions and let you integrate your own inference endpoints.

Keep infra locked by default

Full control over access to internet services and internal services via API or CLI. Nothing is open unless you explicitly allow it.

Control agents with guardrails

Cap beam count and shared inference usage. All beams expire with the user session, roughly 24 hours. No runaway agents.

Behind the beams

Ephemeral, isolated runtimes built for agentic workloads. Fast to start, locked down by default, and wired with identity connected to your infrastructure and audit trails.

  • Firecracker isolation with short-lived storage
  • Delegated identity for every beam
  • Virtual networking connected to infrastructure services without secrets
Isolated Connected Ephemeral
200ms
VM Startup
0
Secrets Required
100%
Audit Coverage
Client
tsh beams add
BEAMS CLOUD
Orchestrator
Cert Authority
Audit Log
Proxy
MICRO-VM
Egress Proxy
Identity Cert
Agent Code
Internal APIs
OpenAI / Anthropic
External APIs

A deeper dive into the architecture

When you run tsh beams add, Teleport provisions an isolated VM, injects an identity certificate, and opens a VNet tunnel — all before your agent executes its first line.

Developer
tsh beams exec 'python agent.py'
creates beam · delegates identity
Teleport Cloud
Orchestrator
Provisions a Firecracker VM on EKS. Starts in 200ms.
Auth Service
Issues a short-lived identity certificate to each beam. No static keys.
Application Proxy
Routes all beam traffic. Enforces access policy per beam. No secrets needed to access trusted services.
Audit Trails
Every access event recorded immutably. Session replay available with enterprise trial.
starts VM · injects cert · opens VNet tunnel
Beam — Firecracker micro-VM
Your Agent Code
python agent.py
Any language or runtime. Full root access inside the VM.
Identity Certificate
Short-lived, auto-injected on start. Scoped to the services this beam is allowed to reach.
Ephemeral Storage
Isolated filesystem. Completely wiped when the session ends, leaving no residue.
No direct internet access; all traffic routed through VNet
Connected via VNet
Inference Endpoints
OpenAI / Anthropic automatically provisioned — no API key stored in beam
Internal Services
Your apps and APIs, authenticated automatically with the beam's Teleport identity
External APIs
Policy-controlled egress only — only allowlisted domains reachable

Scenarios

From internal agents to ephemeral jobs, Beams keeps the environment secure and auditable.

Scenario 1

Coding agents

Drop a simple agent into a beam, let Teleport handle access to internal services and OpenAI and Anthropic inference endpoints with audit and access control.

# Launch ephemeral Firecracker VM, deploy agent
$ tsh beams add ray1
$ tsh scp agents.py ray1:/mnt
$ tsh beams exec ray1 -- python /mnt/agents.py
Scenario 2

Sandboxed apps

Check out the repo, spin up Claude skills, and test against staging or production without exposing secrets.

# Create a named beam running in background
$ tsh beams add ray1
# Clone repo inside the isolated VM
$ tsh beams exec ray1 -- git clone github.com/org/repo
# Spin up Claude, write some code
$ tsh beams run ray1 claude init
Scenario 3

Agentic jobs

Run ephemeral agentic jobs against real infrastructure in an isolated VM. Full access to services, zero risk of credential leakage.

# Spin up a sandboxed agent environment
$ tsh beams add agent-runner
$ tsh beams exec agent-runner -- git clone github.com/org/repo
$ tsh beams exec agent-runner -- make agent-task
Job completed. Beam "agent-runner" will be garbage collected.

Beta launching April 30

Join the early cohort and shape how secure agent runtimes should work.

Teams from Nasdaq, Elastic, and GitLab are already testing