Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't think the idea sticks with me. The final products of these services are never reliable.

Right now, except for some hyperscalers, any similar service has integrated their deployments to some hyperscaler which means any day 2 operations will happen in someone else's computer (supabase, azure/aws, etc). On top of that, you have third party services that you need to integrate and manage their pricing plus auth. That alone is another challenge. Let's not even start with stateful data and migrations which is almost non existent.

The main problem is these tools don't tackle day 2 operations so it will be handled to some developer to make it happen which means exporting your code to some VCS service which I think it's only github. Right there, it's a threat for lovable and others. On top of that, there's not a real feedback loop between manual integration (external dev making it prod ready) and keeping the MVP workflow. Also, there's no real way these services can say "you are free to touch these components without breaking incompatibility with our system, anything else here be dragons".

In other words, You need to own the ecosystem to make more money. Funnel the capabilities to your own ecosystem.



> manual integration (external dev making it prod ready) and keeping the MVP workflow.

Right, the codebase generated by these can get huge, but maintenance can also be aided by AI tools like GitIngest[1], GitPodcast[1] etc. all helping you understand any new codebase easily or someone can query their doubts.

So, I wouldn't strike these kinds of tools yet. AFAIK, v0 already lets you connect github.

1. https://gitingest.com

2. https://gitpodcast.com




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: