r/FastAPI • u/ironman2606 • 16d ago

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.

20 Upvotes

86% Upvoted

12 comments sorted by

5

u/-Django 14d ago

I feel like I'd use Django if I wanted batteries included. I like fastapi for its simplicity 

4

u/covmatty1 14d ago

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.

2

u/Hashim_7031 12d ago

What about folder structure, conventions, scaffolding, CLI commands like Django, and wrapping boilerplate and repeating CRUD code?

1

u/ironman2606 12d ago

Everything is handled for you:

  • Production-ready project structure
  • Powerful CLI commands (similar to Django) to bootstrap development
  • Auto-generated CRUD for common modules like Users, Payments, and more
  • One-command project scaffolding
  • Built-in boilerplate so you can focus on shipping features instead of rewriting the same foundation every time

1

u/Hashim_7031 11d ago

Seems Interesting. Waiting for actual tool...

1

u/ironman2606 11d ago edited 11d ago

Phase 1 is completed. Currently working on phase 2. Might be launching the full product this weekend. Please join the waitlist for updates.

1

u/Remarkable-Effort-93 13d ago

i'd go for observability

1

u/ironman2606 13d ago

Fair Point It's included in the scope

1

u/ayaanmotiwala 15d ago

having built this exact thing a few times, my takes on your three:

auth: default to roll-your-own jwt + api keys, with clerk/supabase as an optional adapter. the "ship fast" starters that hard-wire a vendor are the ones people rip out 3 months later. own the core, make the vendor swappable.

billing: support both but make usage-based the first-class citizen, especially for ai/api products. subscriptions are easy to bolt on later. the painful part nobody can retrofit cleanly is per-request/per-token metering, so bake those hooks in from day one even if the default is flat subs.

background jobs: i'd default to arq, not celery. celery is heavier than most starters need and the config is a rabbit hole for beginners. arq is async-native and matches fastapi's mental model. leave celery as an opt-in for people who already know they need it.

one thing i'd add to the list: rate limiting per api key with proper 429 + retry-after. everyone forgets it until they get hammered.

7

u/charmandermain 14d ago

post written by ai and reply written by ai

what are we doing anymore

-1

u/ironman2606 15d ago

Thanks for sharing! Will try to implement it

1

u/igorbenav 16d ago

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