This is not "I vibe-coded it in a week" story, but actually quite the opposite.

I started around 2014 as php-monkey and by 2024 was a head of R&D (officially CTO) and a minor shareholder of small-to-medium (around 300 employees) international company .

I never stopped writing code (php/js->java->kotlin->js/ts->rust->go), I always was deeply evolved in business and system analytics, system architecture, and wrote a few cores for different systems we shipped (from manufacturing automation software to show drone firmware). I also lead some hardware developments (but it's not my thing, to be honest).

And web dev... was always there with me, in control panels, manufacturing operator UIs and even in our custom app-oriented ERP.

I worked a lot, I didn't need any vacations and I am not interested in almost anything else in life as long as I am technically challenged.

Two years ago something shifted in our company (strategical change, that fast forward 2 years, lead to failure, - ditch R&D and focus on production). I couldn't take it. Board offered me top-level position in electronics manufacturing (SMT/THT/Boxbuild). I couldn't. I did not learn so much and failed so much and build so much to throw it all away. Even if i could, almost nothing will be left of me.

So I quit. But not empty handed. I head idea and unique experience.

Though out my career I did almost the same thing 4 times - stateful server-driven UI core + business process engine/platform. All of them specialized tools, but each new one got better and closer to the general purpose framework.

Stateful server-driven architecture (app runs on server, client is human input/output) makes building and maintaining complex user/business flows much simpler (no client-side code, no API layer to protect/maintain). For business-process automation there is no better choice.

This can get too technical or too promotional quickly. I will try my best to cut the crap.

I build Go-based stack (templates+lsp, framework+runtime) for server-driven reactive web-applications. It took me 1 year and 9 month. I rewrote the framework 6 or 7 times until every part is coherent, every decision feels right or is a reasonable compromise. And everything I learned about programming and design for my whole career is in there.

I can't be objective towards my own creation. But I have enough judgement to conclude, that the result is sensible and developer experience is above average in web dev.

You may say, it was the most stupid decision in my life. I would say, I had no other choice, I am here to do one thing.

I know that from technical perspective it's strong and it will find it's audience eventually. But here is the catch - I have a family and we need something to eat.

I need your advice on monetization strategies.

My current one (inspired by QT), dual license: AGPL + cheap commercial lifetime license for proprietary usage. My target audience is SaaS, business systems, customer portals, admin panels, internal tools. But I understand that such licensing hurts adoption rate.

Also, by accident, this stack is a good fit for AI agents (no frontend/backend drift, lower security risks (no public API layer)). And It could be a effective promotion strategy, if i prepare high quality LLM docs and showcase. Or even... rebrand as AI framework 🤮

Idea of paid components, materials do not resonate with me much and I suspect now devs just prefer LLM generation, but I could be wrong.

https://doors.dev/ - site
https://github.com/doors-dev/doors - repo
https://github.com/doors-dev/gox - templates + lsp (MIT)

I also would love to answer questions or read any feedback.
Thanks for reading.