Why HTMLaunch exists.

I almost threw my laptop out of the window.

For a long time I have been building things I care about. Passion projects like daserstewort.com, a literary journey through the German language, and From Greenhorn to Goldman, a story-driven course on corporate finance. The kind of ideas you pour yourself into at night, long after everyone else has gone to bed, because they matter to you.

Then came the part nobody warns you about: getting them online. Six browser tabs. One wanted repositories. Another wanted nameservers, CNAME records, DNS propagation, API keys, and a webhook secret I was told to never, ever lose. A third wanted three tools installed from the terminal before I could even sign up. I paid for five subscriptions in a single afternoon. Each one promised to be "the simple one". None of them were.

When something finally loaded, half of it was broken. The platform that did publish my work took the site down two weeks later because I had not upgraded to their next tier. Months of work, gone behind a paywall I had not agreed to.

So I built HTMLaunch. No repositories. No nameservers. No subscriptions that quietly strangle your site two weeks in. You drop your file, you get a real website, and it stays up. Every technical horror I dragged myself through, you will never see. That is a promise.

Tobias, founder