Skip to content

Add pricing details for region pinning (multiple pages)#2059

Merged
nijikokun merged 7 commits intomainfrom
update-pricing-for-region-pinning
Mar 20, 2026
Merged

Add pricing details for region pinning (multiple pages)#2059
nijikokun merged 7 commits intomainfrom
update-pricing-for-region-pinning

Conversation

@BPKelley
Copy link
Copy Markdown
Contributor

Added limits and pricing information for region pinning feature.

It's related to our rollout of this blog post tomorrow: https://github.com/ngrok-private/frontend/pull/2227

Also changing the actual pricing page: https://github.com/ngrok-private/frontend/pull/2248

Added limits and pricing information for region pinning feature.

It's related to our rollout of this blog post tomorrow: ngrok-private/frontend#2227
Clarified warning about billing for region pinning feature and updated usage monitoring information.
Comment on lines +217 to +219
It will cost **$0.02 per active endpoint hour**, for each endpoint on a domain with region pinning enabled (as described above).
* This is in addition to the existing rate for endpoints.
* But you'll only be charged for region pinning when an endpoint is _actively_ sending or receiving traffic. If you have endpoints with pinning enabled, but they don't send/receive traffic, there are no associated costs from this feature.
Copy link
Copy Markdown
Collaborator

@nijikokun nijikokun Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
It will cost **$0.02 per active endpoint hour**, for each endpoint on a domain with region pinning enabled (as described above).
* This is in addition to the existing rate for endpoints.
* But you'll only be charged for region pinning when an endpoint is _actively_ sending or receiving traffic. If you have endpoints with pinning enabled, but they don't send/receive traffic, there are no associated costs from this feature.
Region pinning will cost **$0.02 per active endpoint hour**, per endpoint on a pinned domain, in addition to the standard endpoint rate. You're only charged while an endpoint is actively handling traffic. Endpoints with pinning enabled that aren't serving traffic don't incur charges from this feature.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think of this, or something similar? Does it address your clarity concerns here?

It's what I added to the blog post after feedback from both Sams:


Region pinning is available on the Pay-as-you-Go plan. It will be charged at $0.02 per active endpoint hour, on top of the existing rate for endpoints. An endpoint is considered active if it receives any traffic in a given hour. Learn more on the pricing page.

If your pinned endpoints don't receive any traffic, you won't be charged for region pinning — no need to disable endpoints to save money. Your costs scale with your usage.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think niji's suggested change was for brevity, as the pricing explanation is a little technical and the less noise there the better. I like your new proposed change, so I will approve if you add it

per niji's suggestions

Co-authored-by: Niji <niji@ngrok.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Collaborator

@S3Prototype S3Prototype left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@nijikokun nijikokun merged commit e1c9cff into main Mar 20, 2026
7 checks passed
@nijikokun nijikokun deleted the update-pricing-for-region-pinning branch March 20, 2026 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants