Remove beta billing from internal endpoints (ngrok#1015)

Was asked by @samcrichard to remove this, as I grabbed this info when launching the internal endpoints. This removes the beta verbiage and replaces with some copy from Sam. Co-authored-by: Russ Savage <[email protected]>
Rhopz12 · Nov 23, 2024 · 8a72b43 · 8a72b43
1 parent 37592a4
commit 8a72b43
Showing 1 changed file with 2 additions and 5 deletions.
diff --git a/docs/network-edge/internal-endpoints.mdx b/docs/network-edge/internal-endpoints.mdx
@@ -1,10 +1,5 @@
 # Internal Endpoints
 
-::::note
-Internal Endpoints are currently a beta feature, and only enabled for a limited
-number of accounts. Please contact support if you are interested in using this feature.
-::::
-
 ## Introduction
 
 In addition to [public endpoints][Public Endpoints], ngrok also supports creating Internal Endpoints which are specific to your account.
@@ -13,6 +8,8 @@ All internal endpoints end in `.internal`, and are specific to one ngrok account
 
 Internal Endpoints cannot be accessed directly, but rather can only be accessed using the [forward-internal][forward-internal] policy action.
 
+Internal endpoints are available in ngrok's pay-as-you-go plan. An internal endpoint that transmits data in a billing period is counted as an active endpoint for billing purposes.
+
 ### Creating a Internal Endpoint
 
 A internal endpoint may be created by specifying a binding of `internal` for your endpoint. Specifically, when using the agent, a `internal` endpoint may be created like so: