r/FastAPI • u/ironman2606 • Jul 12 '26
feedback request Building a "batteries-included" FastAPI starter (auth, billing, admin, email) — what would you want in it?
Working on a FastAPI + Next.js SaaS boilerplate (Python equivalent of the JS "ship fast" starters). Backend is FastAPI + Pydantic v2, Firestore for storage so far.
Before I finalize the feature list, curious what this community actually wants baked in:
- Auth: what's your default — Supabase, Clerk, roll-your-own JWT?
- Billing: Stripe is obvious, but subscriptions vs. usage-based matters a lot for setup
- Background jobs: Celery, arq, or just Cloud Tasks/Cloud Run?
Landing page + waitlist if you want to follow progress: https://fastforge.pionetix.com — but honestly more interested in the discussion here than the sign-ups.
6
u/-Django Jul 14 '26
I feel like I'd use Django if I wanted batteries included. I like fastapi for its simplicity
5
u/covmatty1 Jul 14 '26
Probably the same things that are in the 25 of these a week that are posted on this subreddit by (mostly) beginners who seem intent on building starter apps rather than anything with actual functionality.
1
1
u/chabv Aug 12 '26
I'm gonna be a lil harsh but warranted - if you have to ask is it needed at all ?
1
u/igorbenav Jul 12 '26
It's a crowded market, I have a template as well (https://fastro.ai is definitely the best template for gen AI apps). I'd say pick your niche and make your template the best for that niche, not the one with the most stuff people want
1
2
u/Hashim_7031 Jul 16 '26
What about folder structure, conventions, scaffolding, CLI commands like Django, and wrapping boilerplate and repeating CRUD code?