SaaS Platform (No Vendor Lock-In) – Can I Use React + Express Instead of Wasp?
Hi all,
I’m planning to build a SaaS platform with open-source tools and want to avoid vendor lock-in. I looked into OpenSaaS.sh for this, but it seems like it requires Wasp to manage the project structure.
While Wasp looks helpful, I’d rather directly use React for the frontend and Express.js for the backend, so I have full control and can easily continue using my code even if Wasp isn’t actively maintained or supported in the future.
Has anyone successfully set up a similar stack with OpenSaaS or another tool without relying on Wasp? Or would it be better to just build my stack from scratch to avoid future dependencies?
Thanks in advance for any insights or advice!
2 Replies
Hi @yash_0100. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Your question about using React and Express instead of Wasp for building a SaaS platform is understandable, especially considering your concerns about vendor lock-in. Let me address your concerns based on the information available:
1. Regarding vendor lock-in with Wasp:
Wasp is designed to be flexible and allow developers to "exit" if needed. When you run
wasp build, you get a React + Vite client and a NodeJS server Discord support thread (https://discord.com/channels/686873244791210014/1220889422367817839). This means you can take the generated code and continue development without Wasp if you choose to do so in the future.
2. Using React and Express directly:
While Wasp currently works with React, Node.js, and Prisma Discord support thread (https://discord.com/channels/686873244791210014/1206921679608090646), it's designed to be a layer on top of these technologies. The Wasp team's long-term vision is to make Wasp agnostic of the underlying technology, potentially allowing developers to choose between different frameworks and languages Github Issue (https://github.com/wasp-lang/wasp/issues/143).
3. Building from scratch vs. using Wasp:
Building from scratch gives you full control but may require more initial setup time. Wasp aims to simplify the development process while still allowing flexibility. The team is actively working on expanding Wasp's capabilities and making it more adaptable to different stacks Github Issue (https://github.com/wasp-lang/wasp/issues/143).
4. OpenSaaS without Wasp:
The OpenSaaS template is built using Wasp, so using it without Wasp would require significant modifications. There's no direct information in the provided sources about using OpenSaaS without Wasp.
5. Future-proofing your project:
The Wasp team is dedicated and has been working on the project for about 3 years, backed by Y Combinator Discord support thread (https://discord.com/channels/686873244791210014/1220889422367817839). However, if you're still concerned about long-term maintainability, you can always start with Wasp and transition to pure React and Express later if needed.
In conclusion, while it's possible to build your SaaS platform directly with React and Express, Wasp offers a middle ground that provides initial structure and efficiency without completely locking you in. The choice ultimately depends on your specific needs, development speed requirements, and comfort level with the technologies involved.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @yash_0100, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?OpenSaas is leveraging Wasp, without it you would have to implement more stuff yourself!
Btw Wasp is VC funded, and open source, so while nothing is guaranteed, it is certain to stay around for at least couple a years more, and hopefully for much longer.
If you want to go just React and Express.js, I would recommend looking for some other saas template instead of opensaas.