--- title: Introducing Cloud Endpoints | daily.dev description: Ngrok launched Cloud Endpoints, persistent always-on endpoints managed via dashboard and API that keep routing and responding to traffic even when upstream... canonical: https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Introducing Cloud Endpoints | daily.dev og:description: Ngrok launched Cloud Endpoints, persistent always-on endpoints managed via dashboard and API that keep routing and responding to traffic even when upstream... og:url: https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto og:image: https://api.daily.dev/og/posts/wWo7rkDto.png og:image:alt: Introducing Cloud Endpoints 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. # Introducing Cloud Endpoints **[ngrok Blog](https://daily.dev/sources/ngrok)** · 7 min read · 0 upvotes · 0 comments ## Summary Ngrok launched Cloud Endpoints, persistent always-on endpoints managed via dashboard and API that keep routing and responding to traffic even when upstream services are offline. They use ngrok's Traffic Policy system, the same configuration language as Agent Endpoints (tunnels), enabling custom error pages, failover, centralized authentication/routing, and API automation via the Endpoints API resource and Kubernetes Operator. Cloud Endpoints deprecate and replace the older Edges feature, offering a simplified object model, more flexible routing by headers/subdomains/paths, and fewer API calls to set up. A migration guide is available for moving off Edges, though no end-of-life date has been announced for Edges yet. Cloud Endpoints are available on free and pay-as-you-go plans, and ngrok.com itself now runs on a cloud endpoint. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are ngrok Cloud Endpoints and how do they differ from agent endpoints (tunnels)? Cloud endpoints are persistent, always-on ngrok endpoints managed centrally via the dashboard and API, unlike agent endpoints (tunnels) which go offline when the local agent process disconnects. They use the same Traffic Policy configuration as agent endpoints, so you can copy/paste configs between the two, and they can route traffic or serve a custom response even if the upstream service is offline. _daily.dev surfaces gateway and networking updates for teams designing resilient API front doors._ ### Are ngrok Edges deprecated and what should I use instead? Ngrok Edges are deprecated in favor of Cloud Endpoints, which are simpler and more flexible, replacing the older object model of Tunnel Groups, Backends, Modules, and Edge Routes with a single endpoint plus Traffic Policy. Creating a cloud endpoint takes just one API call versus multiple calls for edges. No end-of-life date has been set for Edges yet, and a migration guide is available to move existing setups to cloud endpoints. _Track ngrok's edges-to-cloud-endpoints migration path on daily.dev before planning your own cutover._ ### How can I show a custom error page when my ngrok upstream service is offline? Create a cloud endpoint with a Traffic Policy that forwards to your agent endpoint using the forward-internal action, then add a custom-response action that triggers when forward-internal fails, and convert your public agent endpoint to an internal one (e.g. ngrok http 8080 --url https://your-agent-endpoint.internal). This serves static HTML error content without hosting a separate error page service. _daily.dev helps developers building resilient failover and error-handling patterns for API traffic stay current._ --- Tags: [#devops](https://daily.dev/tags/devops), [#devtools](https://daily.dev/tags/devtools), [#networking](https://daily.dev/tags/networking), [#api-gateway](https://daily.dev/tags/api-gateway) [View this post on daily.dev](https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto) ```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":"Introducing Cloud Endpoints","url":"https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto"},"datePublished":"2026-08-23T07:21:02.498Z","dateModified":"2026-08-23T07:26:39.925Z","description":"Ngrok launched Cloud Endpoints, persistent always-on endpoints managed via dashboard and API that keep routing and responding to traffic even when upstream...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5090a13f493974d8e5640a2b9f035da6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5090a13f493974d8e5640a2b9f035da6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ngrok Blog","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":"ngrok Blog","logo":"https://media.daily.dev/image/upload/s--718XXxvE--/f_auto,q_auto/v1787469610/logos/ngrok?_a=BAMAMicg0","url":"https://daily.dev/sources/ngrok"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devops,devtools,networking,api-gateway","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ngrok Blog","item":"https://daily.dev/sources/ngrok"},{"@type":"ListItem","position":3,"name":"Introducing Cloud Endpoints"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-cloud-endpoints-wwo7rkdto#faq","mainEntity":[{"@type":"Question","name":"What are ngrok Cloud Endpoints and how do they differ from agent endpoints (tunnels)?","acceptedAnswer":{"@type":"Answer","text":"Cloud endpoints are persistent, always-on ngrok endpoints managed centrally via the dashboard and API, unlike agent endpoints (tunnels) which go offline when the local agent process disconnects. They use the same Traffic Policy configuration as agent endpoints, so you can copy/paste configs between the two, and they can route traffic or serve a custom response even if the upstream service is offline. daily.dev surfaces gateway and networking updates for teams designing resilient API front doors."}},{"@type":"Question","name":"Are ngrok Edges deprecated and what should I use instead?","acceptedAnswer":{"@type":"Answer","text":"Ngrok Edges are deprecated in favor of Cloud Endpoints, which are simpler and more flexible, replacing the older object model of Tunnel Groups, Backends, Modules, and Edge Routes with a single endpoint plus Traffic Policy. Creating a cloud endpoint takes just one API call versus multiple calls for edges. No end-of-life date has been set for Edges yet, and a migration guide is available to move existing setups to cloud endpoints. Track ngrok's edges-to-cloud-endpoints migration path on daily.dev before planning your own cutover."}},{"@type":"Question","name":"How can I show a custom error page when my ngrok upstream service is offline?","acceptedAnswer":{"@type":"Answer","text":"Create a cloud endpoint with a Traffic Policy that forwards to your agent endpoint using the forward-internal action, then add a custom-response action that triggers when forward-internal fails, and convert your public agent endpoint to an internal one (e.g. ngrok http 8080 --url https://your-agent-endpoint.internal). This serves static HTML error content without hosting a separate error page service. daily.dev helps developers building resilient failover and error-handling patterns for API traffic stay current."}}]} ```