At the very least one must connect to people who would find it valuable (either inbound or outbound), and the value has to be communicated to the prospective buyers. People make their decisions based on how they perceive the product, not based on your view. And the value big enough to overcome friction involved in purchasing, including soft factors like people trusting you with their money. There might be habits and other pieces of inertia that has to be overcome also, and why would they pick your thing over the alternatives. And of course you must be able to charge enough to cover the costs of providing said value.
This is my actual stack, been using Enferno for years, ReadyKit is just the SaaS layer on top. No straying, more like cleaning up what I already run in production.
Stack choices: Flask for its elegant simplicity without hidden conventions, Vue with Vuetify over CDN to skip build-tool pain (massive productivity and time win btw), PostgreSQL because boring is reliable, Redis (optional) for sessions and caching, and Celery when background jobs are needed (optional too)
Python is having a moment right now, between the AI ecosystem, Astral tooling and a huge talent pool. I think calling it the worst choice is a stretch :)
The real question is not raw speed. It's how fast you ship, how many users you need before performance matters and whether you actually own your stack. Most modern solutions push you toward third party auth. This gives you full self hosted auth out of the box.
For sure it depends on the requirement/use cases, but I think most performance issues have nothing to do with the framework. It's usually N+1 queries, missing indexes or no caching etc... Fix those first.
People chase FastAPI for speed, but if your bottleneck is the database or any network bound work, using async vs sync framework barely matters. Premature optimization is real.
Flask handles production traffic perfectly fine. And by the time it doesn't, you will know exactly where the real bottleneck is.
Ha, good catch. That is an old deployment script that could use some love.
I'll work on a modern quick deploy option for ReadyKit. I have an Ansible playbook that handles single server deployments, the monolith old school approach I still prefer. It just needs a bit of cleanup before it's shareable.
Open to feature requests too. If one click deploys to Fly.io, Railway or similar would help, I can add that. Let me know what would be useful.
- Build something boring that makes money. Excitement is optional; users are not.
- Use AI less like a chatbot and more like infrastructure, background processes that think while I sleep.
- Go back to fundamentals that compound, graphics, systems, taste.
- Experiment selectively; curiosity without commitment.
- Invest in people, not “networking.” Fewer pings, more real conversations.
- Protect focus like equity.
reply