![](https://cdn.prod.website-files.com/63ed707844acb1ccf1ccb700/66bb7fd69e9aae88e693a267_c-suite-540-alan.jpg)
Alan Shreve
Alan Shreve is no stranger to building distributed systems at scale. He organically grew ngrok from zero to 5 million users before raising a $50 million Series A. He’s dedicated to empowering developers to build a safer and more secure internet.
Introducing Pay-as-you-go pricing for ngrok
New from ngrok: Pay-as-you-go pricing. Optimize costs by paying just for active endpoints, perfect for delivering apps and APIs to production.
October 31, 2023
•
5
min read
Send your ngrok traffic as logs to Datadog
Today, we’re excited to announce ngrok’s integration with Datadog Logs. You can now send logs of your ngrok traffic to Datadog with just a few clicks. Observability is a key requirement for delivering production apps. This release expands upon our logging integrations to include Datadog Logs alongside AWS CloudWatch Logs, AWS Kinesis, and AWS Firehose.
June 12, 2023
•
10
min read
Introducing ngrok-go: Ingress to Your Go Apps as a net.Listener
Today, we're excited to announce ngrok-go, our idiomatic Go package for embedding secure ingress directly into your Go applications. If you’ve used ngrok before, you can think of ngrok-go as the ngrok agent packaged as a Go library.
March 9, 2023
•
10
min read
ngrok Raises $50M for Ingress Without Infrastructure
Today, ngrok is growing faster than ever. To meet that increasing demand, we’re thrilled to announce our first-ever fundraising round of $50 million. We’ve raised this round to scale ngrok’s business across the board and to dramatically increase our investment in delivering new products for ngrok developers.
December 13, 2022
•
5
min read
ngrok Security Disclosure, May 2022
Last week, we fixed a multi-tenancy bug in the ngrok dashboard’s caching layer that unintentionally leaked data between a small subset of ngrok accounts when they viewed the ngrok dashboard. This bug affected less than 5% of ngrok’s active users. We have contacted all accounts affected by the bug directly via email with instructions for remediation.
May 18, 2022
•
3
min read