Solid earns strong praise for delivering real, production-ready apps rather than throwaway prototypes. Reviewers highlight fast setup, an intuitive flow, and dependable full‑stack outputs with React/Node that feel “ownable” and extendable. Many compare it favorably to Lovable, V0, and Replit, citing superior results and a smoother path to deployment. Concerns center on credits running out during error fixes and wanting clearer guidance on plans, export readability, and long‑term maintainability. Overall, users report shipping working apps quickly, with several moving projects over after hitting limits elsewhere.
Really exciting launch! What caught my eye is how you’re focusing on ownership and extendability. Most AI builders feel exciting for 5 minutes, but then box you in with limits or lock-in.
I’ve been exploring how founders can avoid those “half-measures” in other parts of building too, and I think your approach nails that balance between speed and seriousness. Do you think people will adopt Solid as their first build tool, or as a way to escape the limitations of something they have already tried?
Solid
@andreitudor14 Thanks Andrei! 🙌 Exactly — most tools feel magical for 5 minutes then trap you. With Solid, we see both: teams starting their build with us and teams importing projects (yes, we even built an Import from Lovable feature 😅). The goal: speed + real ownership. 🚀
@eddelan Rooting for Solid's growth!
Solid
Ever since I started programming 19 years ago, I’ve been obsessed with one question: how do we quickly build better software? When ChatGPT came out, I knew something had changed. But almost three years later, with all the vibe coding tools on the market, it’s clear we are not there yet.
Most app builders today are great for frontend design but fail to make it to production. People use them to build prototypes then get stuck. Why? Real-world software faces new challenges all the time — new compliance and on-premise requirements, third-party APIs, integration with existing infrastructures, so the walled-garden app builder approach breaks down quickly when trying to go beyond a prototype.
That's why we built Solid. Solid isn't another walled garden where your creations are held hostage. It builds production-grade software that you can scale, maintain, migrate and extend. Every application comes with its own PostgreSQL database, runs in its own Docker container on dedicated VM, and belongs entirely to you. Build browser automation agents, SaaS platforms, or internal tools—the choice is yours.
Jinna.ai
My first impression by reading the first sentence: "Unlike Lovable and other prototyping tools, ...".
Lovable actually builds the back end just fine, even a database, able to run migrations etc, via third-parties like, for instance, Supabase. I was hands-on vibe coding such a thing lately.
So I'm thinking what's the unique value proposition of your tool.
Solid
@nikitaeverywhere hi Nikita! Do you think lovable was built with Lovable? No. They have a real backend. Here is chatgpt explaining the differences: https://chatgpt.com/share/68beb9d8-4510-800e-b017-0efd6acdd376
Solid
@nikitaeverywhere
Summary
🔍 So what’s better for a serious project?
🟢 Real Codebase (Node.js, React, PostgreSQL) — by far.
It gives you:
• Production-grade architecture
• Full flexibility
• Real security
• Long-term maintainability
• Dev team confidence
Lovable with Supabase is useful for:
• Quick MVPs
• Personal projects
• Internal dashboards
But if you’re building a real startup, plan to raise funding, or expect serious users—invest in a real stack.
Really cool @zerotox do you guys have a LinkedIn?
@mcval_osborne Thanks Mcval. You mean the LinkedIn company page?
Really like how Solid sets itself apart with production ready code. One thing I’m curious about, do you see this being used mostly for MVPs that can later scale, or as a true production tool teams can rely on from day one?
Solid
@nelsonnn000 Great question! 🙌 The answer is both:
Many use Solid to get an MVP live fast — and then keep scaling on the same codebase (no rewrite needed).
Others jump straight into production with Solid because the stack (Node.js, Postgres, React, Dockerized) is what their teams would use anyway.
The whole point is: speed without throwaway code. 🚀
Big congrats @zerotox @tkeith @eddelan , this looks like a real step up from the "demo-only" tools out there. Love that you’re tackling the vendor lock-in problem head-on.
How do you see Solid fitting into a team’s workflow long-term? For example, once a startup scales beyond MVP, can they keep iterating on the same Solid-generated codebase without friction?
Solid
@zerotox @tkeith @lina_huchok Thanks Lina! 🙌 That’s exactly the point — with Solid you don’t throw away your MVP. You can keep iterating on the same codebase because it’s a real stack (Node.js, Postgres, React, Dockerized). Teams can extend it, add features, refactor, and scale it just like any code they’d write themselves.
In short: Solid gets you to production faster, without locking you into a dead-end codebase. 🚀
Pretty impressive—at least from a UI point of view. Solid also managed to draw inspiration from the UI components I fed to it which is a big upside for me. I just wish there were more free credits, as I ran out of mine when trying to create the second project.
Solid
@maxim_bortnikov Appreciate that! 🙌 Glad the UI + custom components worked well for you. And totally hear you on credits, you have 30 free credits per day =)