I've spent the last few months building OpenLen, and it all comes down to one decision I keep having to defend. When someone publishes a page on OpenLen, I strip out every script that isn't mine. All third-party JS, all embeds, gone. What ships is sealed static HTML served straight off disk. That sounds like a limitation. Here's why I did it. The people I'm building for aren't developers. They're the person who bakes cakes, the one who teaches guitar, the woman who opened a workshop three months ago. They will never clone a repo or open a console. If their page breaks on a Tuesday afternoon, they don't fix it — they abandon it. So I made it so there's nothing to break. The cost is real: every interactive thing has to be solved another way. The floating contact menu on my users' pages has zero lines of JavaScript — it's a hidden checkbox and a CSS sibling selector. Bookings, catalogs that sell over WhatsApp, member accounts, comments — they're switches you flip, baked in at publish time. No tokens, no API keys, no developer dashboards. Tools like v0 and Lovable are excellent at what they do: they give you code. I'm not competing for that user. I'm building for the one who would never get there. AGPLv3, self-hosted on a single box. Your HTML stays yours. I'd genuinely like to hear where this falls short — what would stop you from using it for your own page?

OpenLen

The landing page builder that gives you a page, not code

The landing page builder that gives you a page, not code