Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

This started as an employee contest at our all-hands and turned into one of the best things we've ever made. Meet the Teleportopia house band and yes, you might recognize some likenesses to real Teleporters. Don't make AI a silo. Give it an identity.

Pi is a minimal coding agent that lets you choose the features Claude Code and Codex bake in for you. Nothing is forced, nothing is hidden, and you decide what your harness does. However, Pi runs with no safety rails by design, so the environment has to be the boundary. In this video, we'll take a look at Pi, what it is, its features, how to get your own customized setup running, and why it works so well with isolated agentic environments like Beams.

In this video, we'll look at a few key updates from Teleport's latest release v18.8.

AI agents are rapidly moving into production, but most organizations are still deploying them on top of legacy identity systems built around passwords, secrets, and fragmented access models. In this video, we introduce the Teleport Agentic Identity Framework, a standards-driven approach for deploying AI agents securely across infrastructure using cryptographic identity, governed access, and continuous visibility.

Securing AI agents in Teleport, focused on unified identity, eliminating standing privileges, and enforcing real policy controls instead of relying on the whims of an agent.

Regulators don’t just want login logs anymore. They want immutable proof of every action and full session recordings. Steven Martin on how Teleport delivers that — and how AI-powered session summaries are changing what audit actually looks like.

There’s a moment in every Teleport demo where the customer lights up. They see session replay, Kubernetes playback, the scope of what’s possible — and something clicks. Gus Luxton on why that reaction never gets old.

AI agents are tireless, highly capable, eager to please, but difficult to manage. George Chamales (CriticalSec) and Josh Rector (Ace of Cloud) unpack the identity and access challenges posed by agentic AI. How do you verify it was the right agent, doing the right action, approved by the right person? How do we bound, constrain, govern agentic behavior? Ultimately, the same frameworks built for human identity and access should be applied to agents.

FedRAMP 20x → continuous monitoring. Moving from point-in-time audits to real-time visibility.

With just a Slack message, AI agents can triage and resolve Kubernetes failures. But what's stopping that agent from wiping your cluster?