--- title: Teleport 5.0 adds Application Access for Developers description: Teleport 5.0 introduces Application Access, letting developers expose internal web apps and dashboards (Jenkins, Grafana, Kubernetes UIs, custom tools) behind... canonical: https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Teleport 5.0 adds Application Access for Developers | daily.dev og:description: Teleport 5.0 introduces Application Access, letting developers expose internal web apps and dashboards (Jenkins, Grafana, Kubernetes UIs, custom tools) behind... og:url: https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc og:image: https://api.daily.dev/og/posts/WIfYEQEFC.png og:image:alt: Teleport 5.0 adds Application Access for Developers og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Teleport 5.0 adds Application Access for Developers **[Teleport](https://daily.dev/sources/teleport)** · 8 min read · 0 upvotes · 0 comments ## Summary Teleport 5.0 introduces Application Access, letting developers expose internal web apps and dashboards (Jenkins, Grafana, Kubernetes UIs, custom tools) behind NAT to authenticated users via a proxy, without VPNs or manual TLS/SAML setup. It works via a proxy service and an app-access sidecar that creates an encrypted outbound tunnel, issuing each app its own DNS-backed HTTPS URL. Authentication supports local users with MFA, GitHub/Google, and SAML-based corporate SSO, with identity passed to apps via HTTP headers. The release also improves Kubernetes access, unifying SSH, application, and Kubernetes access under a single login, and rebrands Teleport from a 'proxy/server' to an 'Access Platform.' ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Application Access in Teleport 5.0? Application Access is a Teleport 5.0 feature that lets users securely reach internal web applications, such as Jenkins, Grafana, or Kubernetes dashboards, through the Teleport proxy without a VPN. Each app is exposed as its own HTTPS URL, and a sidecar process running with the app role creates an encrypted outbound tunnel from the private network to the proxy, avoiding manual TLS, DNS, and SAML setup per app. _daily.dev surfaces releases like this for teams weighing VPN alternatives for internal app access._ ### How does Teleport authenticate users accessing internal apps through Application Access? Teleport supports three authentication methods: a local user database with MFA for quick setup, public identity providers like GitHub and Google using team or group trust, and corporate SSO via SAML providers such as Active Directory, Okta, Auth0, or OneLogin. User identity is passed to backend applications through HTTP headers, and SSO-integrated proxies typically only prompt for login once per day. _engineers evaluating SSO integrations for internal tools can track access-platform updates on daily.dev._ ### What are the two main roles a Teleport binary can run as for application access? The single teleport binary can run as a proxy service, started with teleport start --roles=proxy, which is the public-facing access point, or as an application access service, started with teleport start --roles=app, which acts as a sidecar creating a permanent encrypted tunnel from a private network to the proxy. This lets apps behind NAT, even on devices with changing IPs, remain reachable. _daily.dev helps developers stay current on access-platform architectures like this one._ --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#authentication](https://daily.dev/tags/authentication) [View this post on daily.dev](https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Teleport 5.0 adds Application Access for Developers","url":"https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc"},"datePublished":"2026-08-23T12:23:04.586Z","dateModified":"2026-08-23T12:53:09.611Z","description":"Teleport 5.0 introduces Application Access, letting developers expose internal web apps and dashboards (Jenkins, Grafana, Kubernetes UIs, custom tools) behind...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,authentication","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Teleport 5.0 adds Application Access for Developers"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/teleport-5-0-adds-application-access-for-developers-wifyeqefc#faq","mainEntity":[{"@type":"Question","name":"What is Application Access in Teleport 5.0?","acceptedAnswer":{"@type":"Answer","text":"Application Access is a Teleport 5.0 feature that lets users securely reach internal web applications, such as Jenkins, Grafana, or Kubernetes dashboards, through the Teleport proxy without a VPN. Each app is exposed as its own HTTPS URL, and a sidecar process running with the app role creates an encrypted outbound tunnel from the private network to the proxy, avoiding manual TLS, DNS, and SAML setup per app. daily.dev surfaces releases like this for teams weighing VPN alternatives for internal app access."}},{"@type":"Question","name":"How does Teleport authenticate users accessing internal apps through Application Access?","acceptedAnswer":{"@type":"Answer","text":"Teleport supports three authentication methods: a local user database with MFA for quick setup, public identity providers like GitHub and Google using team or group trust, and corporate SSO via SAML providers such as Active Directory, Okta, Auth0, or OneLogin. User identity is passed to backend applications through HTTP headers, and SSO-integrated proxies typically only prompt for login once per day. engineers evaluating SSO integrations for internal tools can track access-platform updates on daily.dev."}},{"@type":"Question","name":"What are the two main roles a Teleport binary can run as for application access?","acceptedAnswer":{"@type":"Answer","text":"The single teleport binary can run as a proxy service, started with teleport start --roles=proxy, which is the public-facing access point, or as an application access service, started with teleport start --roles=app, which acts as a sidecar creating a permanent encrypted tunnel from a private network to the proxy. This lets apps behind NAT, even on devices with changing IPs, remain reachable. daily.dev helps developers stay current on access-platform architectures like this one."}}]} ```