Blazeway
A/B testing that explains why your experiments work
Start new thread
Daniel Janisch

Blazeway - A/B testing that explains why your experiments work

by•
Blazeway is a lightweight, cookieless A/B testing platform for founders and small teams. Run experiments with a structured hypothesis, track live results, and document one-sentence insights — so your 10th test builds on your first.

Add a comment

Replies

Best
Daniel Janisch
Maker
📌
Hey Product Hunt! 👋 Blazeway is a cookieless A/B testing tool for founders and small product teams and it's built around one idea: documenting why your experiments work, not just that they work. I kept watching founders (myself included) run experiments, ship the winner, and then lose the reasoning entirely. Six months later, you're making the same guesses from scratch. The insight that "benefit-driven headlines outperform feature lists for cold traffic" just disappears. So Blazeway adds a decision journal layer to A/B testing. Every experiment starts with a structured hypothesis (observation → mechanism → prediction) and ends with a one-sentence insight that goes into a searchable history. Your 10th experiment builds on your first. It's also fully cookieless: GDPR-compliant by architecture, no consent banner needed. And setup is a 2KB script tag. No data team required. We're currently in beta, and the Pro plan is free with no credit card needed. Would love to hear what you think, especially from founders who've felt the pain of shipping experiments with no paper trail. What do you use today to track why product decisions were made?
Daniel Janisch
Maker

I was integrating Blazeway's snippet into my own landing page to run an A/B test.

At some point I got stuck on how to wire up the snippet correctly. The documentation didn't show how variant assignment actually works in practice. No concrete example. No code.

I'm the maker. I got stuck on my own product.

I fixed it. Added an explicit explanation of how variant assignment works and a working code example. Shipped the same day.

The point isn't the fix. It's that this only became obvious when I used the product myself, under real conditions, with a real test running.

That's why I build in public. Not to show progress. To keep myself accountable to what's actually true.