We're not the only ones saying this
Tyler Denk runs Beehiiv. He's making the same ownership argument I keep making about link-in-bio, just from inside a $100M competitor to Substack. That's not coincidence; it's a category emerging.
Tyler Denk runs Beehiiv. Beehiiv is a newsletter platform. They're a direct competitor to Substack, not a self-hosting tool, not a fringe indie outfit. They have funding, a real engineering team, real users. He gave a recent interview where he said something interesting: Beehiiv and Substack are on a "very divergent" strategic path, and the divergence is about ownership. Beehiiv, in his framing, is "infrastructure, not destination." Publishers should "fully own their audience and data." The platform's job is to be an enabling layer, not a brand competing for attention with the publishers using it.
That's roughly the same argument I keep making in this space, just from inside a different category. I write about link-in-bio because that's the corner of the problem I'm building software for, but the underlying claim is identical. The relationship between creator and platform is asymmetric. The platform's incentives diverge from the creator's over time. Software that respects the creator's ownership is structurally different from software that doesn't.
An indie maker making this argument is one thing. The CEO of a major newsletter platform making it is another. Beehiiv lives or dies by the choices its users make. They could have run the standard playbook: lock in via proprietary features, increase switching costs, make audience export technically possible but practically painful. That's what most platforms eventually become. Denk is pretty openly saying they don't want to be that, and they're betting publishers will reward the difference.
I want to be honest about the implementation gap. Beehiiv is still a service. You pay them, they host your newsletter, your audience data lives on their servers. Their pitch is "leave whenever you want with everything intact" — and from what I can see, they back it up. But the lease is still a lease, even if the lease terms are unusually generous. Beacon is on the other end of the spectrum: self-hosted, no them at all, the software runs on your machine and your hosting. We're allies in philosophy, different in implementation. Both options are better than the lock-in default. Neither is the only right answer.
What's actually happening, I think, is that ownership-first software is finally becoming a real category instead of a vibe. 37signals has been making the argument for two decades: once-purchase products, business models that don't require holding customers hostage. The self-hosted movement has been doing the work for longer. What's new is platforms in mainstream creator categories framing themselves this way openly. Beehiiv's bet is that newsletter operators are tired enough of platform extraction to choose differently if given a real option.
For creators, the practical effect is that "rent forever" vs "be a sysadmin" is no longer the only choice. There's a spectrum now. Beehiiv-style platforms that respect ownership but still host you. Self-hosted tools you fully run yourself. Hybrid options in between. You can pick the point on the spectrum that fits your skill level, your budget, and your tolerance for setup. None of them is an indie-zealot lifestyle commitment. All of them are better than what most creators are still using.
Beacon doesn't require you to be an indie zealot. It's one option on a spectrum that finally has options — the maximum-ownership, lowest-recurring-cost end. If that fits you, the demo is here. If a Beehiiv-style middle ground fits better, that's a great choice too. Glad I'm not making the case alone.