Starting a new backend always felt like losing 3 days to Docker, auth, SSL, DNS before touching the actual idea.
So I built DooCloud: write a schema, get a live production API in under 5 minutes.
It generates the REST API, deploys it, and handles JWT auth, SSL, custom domains, rate limiting, and Git. No server to manage. It's not magic, you own code in the repo it creates. And it's binary.
I launched on April 14. Cold launch did not work. That part is on me, not the product. I spent months building and barely thought about distribution.
I’m sharing it because I want honest feedback from other solo founders: is this actually useful, or am I only solving my own problem?
Playground: https://doocloud.dev/#playground
Note: Sorry, I posted this twice by mistake, keeping this version
The 'I spent months building and barely thought about distribution' line lands hard, I'm in the same place. On DooCloud itself: the 'you own the code in the repo it creates' framing is the differentiator from typical PaaS, but it's buried below the 'no DevOps' pitch. If a CTO scrolls and sees no DevOps then leaves, they miss the bit that actually matters to them. On distribution, I'm working through Play Store closed testing for a finance app right now and the bit that's worked best so far is direct, conversational outreach to people in similar build-stage rather than broad Show X posts. Happy to swap honest feedback or mutual amplification at launch if useful.
Hi, I appreciate the feedback. I'd like to understand what I'm missing here.
And for CTO, yeah, I realise then DooCloud is not for a deep technical person, I realise the best positioning is DooCloud for a startup founder or solo founder who needs a quick solution, including most boilerplate features. Because I realise and got feedback, the tech person says why I should not try cusror claude or other. I realise then DocCloud is not mainly for tech people because it trigger thier ability, what is your thougt?