Earlier quoted context omitted.
I agree, i'm working on my own SaaS boilerplate in laravel debating oss vs paid, might be a cheaper Nova/Spark combo alternative. $99 per project is pricy, esp when a lot of projects are just testing ideas and things. SaaS needs to have teams, projects, payments, auth, invites, and possibly be configurable for different 'types' of scenarios... projects could be optional for instance if they don't group actions by pro…
Thanks for sharing your thoughts and experience! Honestly, I don't know if teams and projects should be a part of SaaS. If so, in which context? I wonder, how are you going to charge? Is your product is app or it's SaaS itself? And I think $9.99/month is very low price. Any link to share? ;-) Good luck!
Show HN: SaaS application boilerplate
71–78 of 78 posts
Re: Show HN: SaaS application boilerplate
#72Earlier quoted context omitted.
Thanks for sharing your thoughts and experience! Honestly, I don't know if teams and projects should be a part of SaaS. If so, in which context? I wonder, how are you going to charge? Is your product is app or it's SaaS itself? And I think $9.99/month is very low price. Any link to share? ;-) Good luck!
Look at some apps like Clockify, Slack, Trello, Jira, Asana, all have teams, -- I really like the way clockify does workspaces, and then you clients, and projects per client. All organized nicely. This sort of model of teams/projects would probably be quite common in SaaS...think anything tagetting SMB's that need to give access to parts of the app for their employees or contractors, or use it to organize, etc...
Re: Show HN: SaaS application boilerplate
#73I am working on the same idea, on a different stack. Hope to finish it soon. Good luck with your project!
Re: Show HN: SaaS application boilerplate
#74Earlier quoted context omitted.
Although there are literally dozens of tools out there that aim to facilitate SaaS, if you look at the definition of SaaS and what makes SaaS, SaaS. Things like “on demand” activation, licensing models, and resource management are the key definition points, not so much the nuts and bolts libraries needed behind the scenes. I wrote a funcional specification for a SaaS provider platform about a month ago (see https://a…
WOW! You put a lot of work into it, and I'm going to research it. Just wondering, what made you create this phenomenal work?
Thanks for the kind words. To answer your question, I can say I had a many reasons to create this document. First and foremost I’d like to create an open source project around these specifications and see if I could generate interest and invite contributors to jump on board. Second, is to provide a working document for the community scrutinize and critique as it’s still very much work in progress, and before committing to building the solution I wanted to ensure what is built is done so in a way that gains acceptance and use.
Also, I see that Cloud and more particularly SaaS has a lot of bias surrounding it’s use both from a commercial and personal perspective. This largely has to do with how SaaS providers store and use peoples’ data. My aim with PAL is to create a flexible solution that takes all perspectives into consideration based on the type of offering and what is acceptable by the customer or user of the SaaS offering.
I could go on further to say that since SaaS has become such a large segment of the Cloud market I also feel it’s important to keep as much of it as open and free as possible as to allow smaller players the chance to offer SaaS solutions. Since the market is largely dominated by Big Tech this is becoming increasingly more difficult and that has a lot to do with the lack of resources available to smaller companies. It may not seem apparent to most people especially those in countries where internet services are easily available but currently where I’m located, a country where the economy suffers greatly, the low cost of establishing SaaS solutions for businesses vs offering custom built in-house solutions is a far more feasible option.
Anyway, I hope the you find the contents of the document useful and helps you in some way with your project :)
Regards James
Re: Show HN: SaaS application boilerplate
#75Earlier quoted context omitted.
WOW! You put a lot of work into it, and I'm going to research it. Just wondering, what made you create this phenomenal work?
Hi KRains Thanks for the kind words. To answer your question, I can say I had a many reasons to create this document. First and foremost I’d like to create an open source project around these specifications and see if I could generate interest and invite contributors to jump on board. Second, is to provide a working document for the community scrutinize and critique as it’s still very much work in progress, and befor…
Re: Show HN: SaaS application boilerplate
#76I am a fan of opinionated full-stack frameworks, in particular for building B2B web applications which contain lots of CRUDL views. For an open-source solution that largely revolves around the React frontend, consider react-admin [1] + its adapter for Hasura [2]. [1]: https://github.com/marmelab/react-admin [2]: https://github.com/hasura/ra-data-hasura , https://github.com/hasura/graphql-engine/ In Ruby/Rails-land, t…
Anything full stack with Python/PostgreSQL/Angular?
Full disclosure: I'm the creator. Happy to answer any questions you have about it!
Re: Show HN: SaaS application boilerplate
#77Re: Show HN: SaaS application boilerplate
#78Nice, but I think you need also an ORM. I used Flask with ORM from Django after I tested SQLAlchemy, and now I think that was a good choice.