Just buy gpt-4 + github copilot/cursor for 2x$20
Yeah, and just let it build your entire startup for you while you sleep. 20 days in, you will have six figure revenue. /s
Is that the passive income all the influencers are talking about???
Show HN: PySaaS – Python SaaS starter kit
21–30 of 52 posts
Re: Show HN: PySaaS – Python SaaS starter kit
#22No contact info or something similar? How do we distinguish this from a "scam" site, if we do not have anyone to hold accountable? Social Media accounts do not count.
4000 followers on twitter with zero tweets. None seem to be software developers. This project is giving me more red flags than it should.
Just did a little "research" on op, it tingled an array of other red flags
Re: Show HN: PySaaS – Python SaaS starter kit
#23How is it different from: Django (Python) SaaS Pegasus https://www.saaspegasus.com/ Djaodjin. Open Source. https://djaodjin.com/ Carrot Seed https://www.cnc.io/en/seed The SaaS boilerplate by Apptension (+React) https://www.apptension.com/saas-boilerplate Vanty Starter Kit https://www.advantch.com/ Saas Hammer https://saashammer.com/ Flask (Python) SaaS Forge. Open Source. https://www.saasforge.dev/ Ignite (SaaS Boil…
PySaaS uses the Pynecone web framework rather than Django or Flask. This allows you to build the entire stack in a single language instead of having to learn and switch between multiple. You can install and import any Python library as you would with any Python file. The frontend is compiled down to a NextJS app, and FastAPI is built-in for the backend. UI components are fully-customizable, and are actually wrappers…
That kind of other-language-to-JS stuff works great for small, one-man projects that never go to production. Unfortunately, other than TypeScript, none of these solutions have really achieved critical mass, and they all fizzle out after a few years, leaving you with a horrible mess to clean up. You have layers and layers of indirection, and you don't know whether your problem is your code, or a Python library, or the Python-to-JS layer, or one of the JS libraries, and no one on the Internet can help you because your stack is completely bespoke.
I applaud you trying to make it easier for people to get started, but throwing them on top of this Tower of Babel and pretending it will never come crumbling down into a mess of inconsistent languages and libraries is a recipe for pain. TypeScript is not that hard. If you're teaching beginners how to build a web front end, just start with that, and let them use either TypeScript or Python on the back end, depending on how ambitious they are.
Re: Show HN: PySaaS – Python SaaS starter kit
#24I don't understand why you wouldn't turn the demo site into the _actual_ site? They have all the same information and features?
Re: Show HN: PySaaS – Python SaaS starter kit
#25The lifetime one-time-payment pricing seems worrying to me. It feels like it would drive high levels of activity/maintenance during a growth curve, then probably fall off rapidly. Leaving little incentive to maintain it well after some point.
Whenever I see “lifetime guarantee” or anything like that, I think yeah, for the lifetime of the company, not the customer.
Re: Show HN: PySaaS – Python SaaS starter kit
#26How is it different from: Django (Python) SaaS Pegasus https://www.saaspegasus.com/ Djaodjin. Open Source. https://djaodjin.com/ Carrot Seed https://www.cnc.io/en/seed The SaaS boilerplate by Apptension (+React) https://www.apptension.com/saas-boilerplate Vanty Starter Kit https://www.advantch.com/ Saas Hammer https://saashammer.com/ Flask (Python) SaaS Forge. Open Source. https://www.saasforge.dev/ Ignite (SaaS Boil…
PySaaS uses the Pynecone web framework rather than Django or Flask. This allows you to build the entire stack in a single language instead of having to learn and switch between multiple. You can install and import any Python library as you would with any Python file. The frontend is compiled down to a NextJS app, and FastAPI is built-in for the backend. UI components are fully-customizable, and are actually wrappers…
> The frontend is compiled down to a NextJS app
So, PySaaS > NextJS > React > Javascript
How far will this abstraction layer reach?
Re: Show HN: PySaaS – Python SaaS starter kit
#27The lifetime one-time-payment pricing seems worrying to me. It feels like it would drive high levels of activity/maintenance during a growth curve, then probably fall off rapidly. Leaving little incentive to maintain it well after some point.
Depends on the size of the niche, and how long and continuously you're reaching out to it.
Re: Show HN: PySaaS – Python SaaS starter kit
#28Where is the admin panel?
Re: Show HN: PySaaS – Python SaaS starter kit
#29The lifetime one-time-payment pricing seems worrying to me. It feels like it would drive high levels of activity/maintenance during a growth curve, then probably fall off rapidly. Leaving little incentive to maintain it well after some point.
Whenever I see “lifetime guarantee” or anything like that, I think yeah, for the lifetime of the company , not the customer .
Yeh whenever I see “life time” pricing I think the author
Is impatient and/or greedy and just wants as much money up front as possible. Where’s the incentive to keep plugging away at updates when less new customers are signing up.
Plex have this model too which worries me
Re: Show HN: PySaaS – Python SaaS starter kit
#30How is it different from: Django (Python) SaaS Pegasus https://www.saaspegasus.com/ Djaodjin. Open Source. https://djaodjin.com/ Carrot Seed https://www.cnc.io/en/seed The SaaS boilerplate by Apptension (+React) https://www.apptension.com/saas-boilerplate Vanty Starter Kit https://www.advantch.com/ Saas Hammer https://saashammer.com/ Flask (Python) SaaS Forge. Open Source. https://www.saasforge.dev/ Ignite (SaaS Boil…
The example you have mentioned only uses Python in the backend. It's based on Django or Flask. Then, in the frontend, it uses JavaScript.
Building a SaaS from scratch required a lot of time. Happy to see a 100% Python SaaS Starter kit, usually it was reserved for JavaScript because of the frontend. In the past, you are forced to use JavaScript for the frontend.
I know it because I'm the author of Nextless.js [1], a full-stack JavaScript starter kit that is totally based on JavasScript, from frontend to backend. Using only one programming language was my competitive advantage compared to the boilerplate based on Ruby, Python or PHP.
I think in the future more and more languages can be used in the frontend like Rust, etc... There are already some frameworks you can use to build frontend in Rust. It's only the beginning.
---