Hi [First name],
We're rebooting our monthly product newsletter at Honeybadger. If you're reading this, it's because you signed up for our newsletter on our website, or you're a Honeybadger customer and receive our monthly product updates.
We want to try something new.
There's so much we could tell you about, but we know you're busy figuring out what your job even is in 2026—and the good stuff we're shipping is in the changelog anyway.
So instead of sending you a wall of features each month, we'll keep our emails brief and focused on the interesting bits of building and scaling Honeybadger.
Validating changes in production
ClickFunnels had bots using their checkout forms to test stolen credit cards. Blocking the bots risked blocking real customers, so they ran bot detection in report-only mode first.
Claude instrumented the feature with Honeybadger and built a custom dashboard to validate the results so that there were no surprises when they turned it on. Here's what VP of Platform Engineering Nate Vick had to say:
That's one thing that I've just totally loved doing with these tools: validating and gaining confidence, and then flipping the switch and removing the feature gates.
Read how ClickFunnels did it →
This is how we use Honeybadger every day
Earlier this week we deployed a feature to enable signed URLs in the web service we use to generate social media graphics (based on this cool Elixir OG image generator by our friends at SavvyCal).
Instead of rejecting unsigned requests right away, we're monitoring the results in Honeybadger before requiring the new signatures. Good thing we waited: about 40% of requests are still unsigned. Most of those are crawlers and pages cached before the change. We'll flip the switch once that number drops.

Notable things we shipped recently
Around our orbit
That's all for now. Are you validating changes like ClickFunnels, or using Honeybadger in a novel way? Shoot us a reply—we wanna hear your story.
—Josh, Ben, and the Honeybadger Crew