With Telepresence, you’re developing on a Kubernetes or OpenShift cluster, which can be configured
to be identical to production. Eliminate bugs due to differences between development and production
environments.

Telepresence adds virtually zero overhead to your development environment. It only requires the
memory and CPU necessary to run your actual service. Don’t let your laptop melt from running
minikube!

Use your favorite code editor, debugger, profiler, or other tools. Anything that runs on your
laptop works with Telepresence.

"Telepresence is such a useful tool. I use the swap deployment so I can iterate faster
when I'm working back and forth between my local cluster and cloud clusters."

"Going through CI to test 2 lines of changed code seems excessive. Telepresence got it
down to `go run main.go` with an added benefit of getting access to real ConfigMap /
Secrets."

Vladimir Pouzanov

"Telepresence can be used to drastically improve the development workflow for Spark
applications. It’s the best tool we have found for running integration tests against against systems inside our cluster from our local machines / CICD environments."

Nate Buesgens, Vizual.AI

Get started in 3 minutes

How it works:

Telepresence substitutes a two-way network proxy for your normal pod running in the Kubernetes cluster. This pod proxies data from your Kubernetes environment (e.g., TCP connections, environment variables, volumes) to the local process. The local process has its networking transparently overridden so that DNS calls and TCP connections are routed through the proxy to the remote Kubernetes cluster.

Stay Updated

Telepresence is under active development. Subscribe to get updates and announcements: