Thanks! I really like your new website and rebrand.
Some wishes:
1) First I was confused when I didn't find issues etc, but then I found your rebrand. Please remove your https://github.com/level09/readykit repo, and rename original https://github.com/level09/enferno repo to https://github.com/level09/readykit, so that you keep all issues, PRs, and releases. It also will redirect old enferno url to correct new readykit url.
2) Please make automatic immediate forward from URL https://enferno.io to https://readykit.dev .
3) It would be nice if your website had button for dark mode, so you could switch between light mode and dark mode. Your new website is light, and your previos website is dark.
Thanks!
Thanks for the kind words and thoughtful suggestions!
On the repos, they're intentionally separate projects. Enferno stays as a minimal Flask framework with fewer dependencies, ideal for anyone who wants a clean starting point. ReadyKit builds on top of Enferno with SaaS-specific features like workspaces, Stripe billing, and team collaboration. I plan to maintain both:
* Enferno: lean framework for general Flask projects * ReadyKit: batteries-included SaaS template
This gives users the freedom to choose the level of complexity they need.
On the redirect, good point. I'll set that up so enferno.io links don't cause confusion.
On dark mode, fair feedback. I can add a dark mode toggle and will work on that.
Thanks again for checking it out!
Good stack, nice choices.
What always turns me off this sort of thing, and there are loads of these kits, is the tech choices. It's always either very frontend heavy with no answer for deeper backend engineering, or it's all based on MongoDB, or it's a complex mess of Javascript dependencies.
This looks like an excellent set. One could criticise every component, Celery kinda sucks, but would I build a business on it? Yeah sure, many have and they're fine. Flask has its issues, but it will absolutely work. Python is having a renaissance with Astral.
I imagine this would be a highly productive stack to work with. Might even tempt me away from Django for my day-one stack... maybe...
Thanks, that means a lot coming from someone who has clearly evaluated many of these stacks.
A few notes:
Celery is completely optional, it's there if you need background jobs, but the core app runs fine without it. Same with Redis, it falls back to filesystem sessions in development. The idea is to add complexity only when you actually need it.
And that is the beauty of open source. If you don't like Celery, swap it for RQ, Dramatiq or whatever fits your workflow. It's your code.
The stack is opinionated, but the opinion is simple, pick boring, battle tested tools and stay lean. No webpack, no heavy build chains, no node_modules black hole. Vue and Vuetify load from CDN in development and that is perfectly fine. It ships products just as well.
Django is fantastic, and if you're productive there, there is no reason to switch. But if you ever want something lighter where you wire up only what you need, give it a try.
On my list for 2026 is a suite of tools for my coworkers who work in the same tech I do (we’re consultants). I get thrown a small bone from the silverbacks come bonus season for these kinds of thing.
Your project fits perfectly with what I need, I’ve built the functionality (using python even) now I need all the other stuff to get it up and running on the web. Thanks for doing this!
Awesome, glad it fits! Will be posting more tutorials and use cases soon. Let me know how it goes
(first of all, excellent contribution, starred, will serve as useful starter/reference code, etc)
may i ask incentives? are you doing this out of the kindness of your heart?
Thanks for starring!
Honestly, open source changed my life. I've built my own products on this stack. https://mixedcrm.com for example runs on Enferno, along with many several other projects of different sizes. It's been my go to foundation for years.
After taking so much from the ecosystem, giving back just felt right. And value has a way of coming back, whether through contributions, feedback, connections or simply knowing the code is being battle tested by more than just me :)
I wasn't able to see some example images or a demo video. That would be great to have before setting things up.
Fair feedback. Demo, video, and use case tutorials are in the works! stay tuned
Python with celery is not my stack of choice but:
This is awesome and I would use it in a heartbeat.
Appreciate it! Sometimes the right tool wins over the familiar one :)
Say more on this, your chosen stack?
How far did you have to stray from your “actual stack” for package-ability, for instance?
Neat project - especially as pure FOSS.
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)
You are completely right in the direction you are headed. I have 2 Saas as well and let me tell you that it's the best thing to offer services and get paid.
Appreciate it! and congrats on your two! SaaS is indeed a fun ride :)
Neo brutalist UI look and feel! It's cool to see it in a modern product!
Thanks! Felt like a nice break from the usual generic SaaS aesthetic
Maybe also rename https://github.com/level09/enferno-cli to https://github.com/level09/readykit-cli ?
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.
I think CI/CD to those platforms would be more useful than “one click deploy”. Submit your changes - 2 minutes later it’s deployed.
Good call. That's next on the list!
What is your experience running python+flask on production with low latency requirements? Coming from Django, it was always a struggle.
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.
Nice concept, why flask though? Just for iteration speed? Because Python in almost 2026 is probably one of the worst choices for a web server, right after Javascript...
So quick iterations and rebuild once the SaaS has to scale I guess?
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.
Scale problems are good problems to have.
Not OP but I think it's a bit harsh on flask tbh.
If you want to validate a product or run with a few K users (which I think this is helping), I really think that flask is a proven WS framework that just works.
There are many node/js alternatives, nice to have one for the Python devs
Agreed!
One differentiator among others: try finding a stack with full self-hosted auth. Most push you toward third parties! I wanted to own my users.
https://medium.com/@level09/the-stack-that-owns-you-7ff06b26...
For 99% of the SaaS teams, low latency becomes an issue later unless the product itself needs to be catering with that feature. Focus with kits like this is to get everything running on day 0.
Its not about low latency but memory consumption too. If you have unlimited money to throw at Fly.io or AWS its no issue sure, but other than that you might wanna be mindful with the resources you waste due to using the wrong tool for the problem.
If your app goes viral for some reason and has to scale within hours its not easy to rebuild for performance in that timeframe. Then if u use stuff like AWS and your app has a shit payment model that allows free tier users to just waste resources, good luck paying off that invoice.
There's no reason to throw money at those providers when there are many options a dozen times cheaper.
Also it's not fun to play catch-up due to performance issues, because popularity will trigger competition from other corporations and they are unlikely to pick dynamic languages with reputation issues regarding things like latency.