I've spent more time than I'd like to admit wrestling with overcomplicated tech stacks. Build tools, bundlers, frameworks that need their own frameworks. So when something genuinely simple works, it's worth stopping to appreciate it.
The iframe. Yes, that iframe. Been around since the late 90s. Still does exactly what it says on the tin.
We've been building interactive tools internally, and the question kept coming up: how do we get these in front of brewers, partners, and internal teams without asking everyone to log into yet another system? The answer turned out to be about one line of HTML.
BetaTec Product Calculator
Helps those who work through BetaTec product selection and dosing. No account, no download, no friction. It just runs.
Haas Hop Products Calculator
Broader scope, full Haas product range. Both calculators are running on this page right now, completely independent of each other and of the blog itself. Neither knows the other exists, and neither needs to.
Why I'm Writing About Iframes in 2026
Because somewhere along the way, the industry decided they were embarrassing. A relic from the Geocities era, filed alongside marquee tags and visitor counters. Fair enough. They were badly misused for years. Pop-up ads, dodgy affiliate sites, layouts that broke on everything.
But the technology itself is just a window into another document. That's all it's ever been. The embedded content doesn't care what the host page is built with. The host page doesn't care what's inside the iframe. React, Vue, plain HTML, a spreadsheet. If a browser can render it, an iframe can embed it.
No npm install. No build step. No dependency conflicts. You point at a URL and the tool appears.
What This Actually Unlocks
Every tool we build becomes embeddable with a single line of code. A distributor drops a dosing calculator onto their own site without touching their codebase. A sales rep bookmarks a live tool and pulls it up mid-conversation. A brewer in Yokohama runs a product comparison from a partner page without creating an account or switching tabs.
The bit that matters most internally: when we update a tool at the source, every embed updates automatically. This blog post, a partner's website, an internal wiki. All current, all the time. No redeployment, no version sync, no "can you send me the latest file."
In an industry that still runs a remarkable amount of its commercial operations through email attachments and static PDFs, that's not a small thing.
The best systems are composable. Independent pieces that work together without being tightly coupled. The iframe is exactly that. Each tool is self-contained. You don't import it, configure it, or worry about what version it's on. You embed it and move on.
That's not a limitation. That's how it should work.
