Thank you for your valuable feedbacks and sharing your thought. I totally agree with your approach for a general Saas project/product and frankly speaking, I prefer as well your business model because it can bring recurring revenue instead of one-time sales.
Here in terms of Nextless.js, as the customer will have access to the source code, the revenue sharing like 3% as you suggest is extremely hard to implement. It raises a lot of technical challenge...
Perhaps in the future, this concern can be addressed somehow and your proposed business model shall be implemented. Have you had such concerns/experiences for your projects? Pricing is not an easy subject though :)
Yes, indeed, there are something similar in Rails and Django ecosystem.
All of them give access to:
- Authentication
- Payment
- Dashboard UI
- Landing page
- Form management
- ...
I just made the same for Node.js/JavaScript/TypeScript ecosystem. Nextless.js also gives access to the same features in React and TypeScript. But, I also wanted to add more into the boilerplate, things that don't offer by others:
- Infrastructure as code
- Serverless for scalability and pay-as-you-go pricing with no server to manage, no docker, no kubernetes
Indeed, you can use Redwood or any other framework to build a SaaS. But, at the end, you need to set up:
- Authentication
- User dashboard
- Landing Page
- Pricing
- Form management
- Stripe integration
- Infrastructure as code
- Type checking, linter, code formatter
- VSCode
Nextless.js provides everything out-of-the-box for you to build a SaaS business and focus on the things that makes your SaaS unique. You shouldn't lose time on boring UI, setup and configuration.
Thank you for your support and extremely happy you are also building a SaaS.
Definitively, there are several ways to build a SaaS product and I also think Cloudflare Workers, FaunaDB, Auth0, Paddle, etc. is a good stack.
One good thing to use AWS, everything is centralized. Another good thing is you can use Infrastructure as code. As a developer, you can provision everything with code (TypeScript), no need to click and remember user interface.
All frontend is in "export" mode, made in static. So, no dynamic server needed to run the frontend, 100% compatible with any static hosting like Cloudflare page.
For the backend, it uses AWS lambda with API gateway and protected by AWS Cognito for private route.
By default, you can use the themes for one domain/project. You can also upgrade to the unlimited version, which allow you to use in unlimited domains/projects.
You have access to the code source. So, you can modify as much as you want. The only limitation is you cannot create derivative products like themes, components library, page builder, etc. You aren't allowed to repackage or redistribute for someone else to use.
Sorry for this inconvenience, I'm currently taking video and I've only published two videos on YouTube for "preview" at: https://www.youtube.com/channel/UCjZpEiptoMVz4U-5G1QKBlA . I'll add the remaining in the following week.
Here in terms of Nextless.js, as the customer will have access to the source code, the revenue sharing like 3% as you suggest is extremely hard to implement. It raises a lot of technical challenge...
Perhaps in the future, this concern can be addressed somehow and your proposed business model shall be implemented. Have you had such concerns/experiences for your projects? Pricing is not an easy subject though :)