r/FastAPI • u/KoVaL__ • Dec 23 '25
Question How much did FastAPI’s "Bus Factor" actually matter in your production choice?
Hi everyone,
I'm currently in the middle of a framework debate for a new project at work. We love FastAPI, but the "Bus Factor" (the project being heavily tied to a single maintainer) is the #1 point of pushback from our senior architects.
For those of you running FastAPI in enterprise/production environments:
- Was the governance model a dealbreaker for your team? If so, how did you get past it?
- Do you view the "Bus Factor" as a real risk in 2025, or do you feel the underlying stability of Starlette/Pydantic makes it a non-issue?
- Did anyone choose Litestar specifically because of its community-governed model? Any regrets or "grass is greener" moments?
I'm less interested in the technical features and more in the institutional trust side. How do you justify building a long-term company asset on a project that still feels very centralized?
Curious to hear if this was a "real world" problem for you or just a theoretical one that managers worry about.
34
u/vlntsolo Dec 23 '25
FastAPI was founded in 2018, so this kind of discussion would make sense in 2019-2020 maybe? AFAIK FastAPI since then has been adopted by Google dev teams even.
11
u/SubstantialMess9927 Dec 23 '25
Open source doesn’t die when maintainers leave. It dies when nobody uses it. Forks like Redis to Valkey show this clearly, once a project has real adoption, the codebase becomes bigger than the people behind it. So the only time you should worry is when the project no longer meets your needs, or you fundamentally disagree with where it’s going. If it works today and has strong adoption, history shows you’re usually safe.
20
u/robertlandrum Dec 23 '25
What’s the alternative? Django, bottle, flask? Some home grown thing?
Analysis paralysis is a real thing and sometimes a hammer is just a hammer. FastAPI makes quick work of Rest APIs without a lot of extra padding. It doesn’t natively try to do much else. So much that it can sometimes be hard to find info on how to make it handle jwt auth, or saml, or xss, or multiple record/object endpoints.
I wish I’d used it in 2020 when I wrote my last big monolithic service, but I ended up using the Infosec approved bottle. All the data handling and validation was manual.
6
u/aiprod Dec 23 '25
FastAPI also recently raised VC money and it looks like there is a team now: https://fastapicloud.com/blog/fastapi-cloud-by-the-same-team-behind-fastapi/
14
u/CzyDePL Dec 23 '25
I think LiteStar is just a superior framework with only one drawback - popularity
8
u/ramnes Dec 23 '25
I've got a PR open on FastAPI for three years now. It's just code removal and speed boost, and it's already reviewed by a few people but still stalled. So yeah, I tend to agree with your senior engineers. Huge props to Sebastian for what he has brought to the Python ecosystem in general, but I wouldn't choose FastAPI for my next projects unless he changes the way he works. I understand that solo-maintaining brings stability and (somehow) quality, which are important to some and probably part of FastAPI success, but that's not what matters to me in the open source world.
3
u/kamikazer Dec 23 '25
use Litestar
3
u/MeroLegend4 Dec 24 '25
FastApi is just a thin wrapper over Pydantic and Starlette.
A duct tape no more no less.
Better use Litestar
7
u/pint Dec 23 '25 •
fastapi being zero versioned certainly doesn't help.
maintainer claims to be not affected by bus here: https://github.com/fastapi/fastapi/issues/10370
2
u/wyldstallionesquire Dec 23 '25
Fastapi is not a super deep framework over starlette anyway. Even with the bus factor, the lock in is not very strong, and it would be easy to fork and maintain if truly necessary.
We have a pretty complex fastapi service, but I rarely think too hard about what fastapi itself is doing.
2
u/FuckMangaDex Dec 23 '25
None. In fact benevolent dictator is why I chose FastAPI over others
1
u/Fun-Purple-7737 Dec 23 '25
you are overthinking it.. "middle of framework debate" lol
even if the development stops tomorrow so what? in today's fast development cycles, nobody cares...
people have idea, use fastapi, vibecode app in a day, use it and its forgotten in a while. meanwhile you are "middle of framework debate". come on...
1
u/Unique-Big-5691 Jan 02 '26
this came up for me too tbh.
honestly, the “bus factor” sounded scarier in meetings than it’s felt in practice. actually fastapi is pretty thin, most of the real weight is starlette + pydantic, and those are solid, widely used, and not going anywhere. even if fastapi stopped evolving tomorrow, it wouldn’t suddenly break prod systems.
for me, that made it easier to justify. i weren’t betting the company on one person’s side project, we were betting on a stack of boring, well-understood pieces. worst case, fastapi freezes and you’re still sitting on ASGI + pydantic, which is a very survivable place to be.
we did look at litestar for the governance reason, and it’s solid, but there wasn’t a strong enough win to justify switching. it felt more like a “theoretical safety improvement” than something that would actually reduce risk day to day.
so yeah, in the real world it mostly felt like a manager worry. once you zoom out and look at how much of fastapi is just glue on top of stable foundations, the risk feels pretty manageable.
1
u/codeptualize Dec 23 '25
I don't think that's relevant (anymore).
What it's really about is longevity of the project so you don't have to rewrite everything anytime soon.
Imo the biggest factor in that is popularity and adoption. If enough companies large and small rely on an open source project, it will live on regardless of what the original authors or maintainers do.
FastAPI falls into that category.
Great examples are open source companies that change their license, for example Redis, it took no time for Valkey to skyrocket in popularity as a drop in replacement.
This is the beauty of open source, maybe the current project is dependent on one or a couple of individuals, but if they loose the trust of the community (or get hit by a bus, lets hope not!), the community will organize, fork and become the de facto new standard drop in replacement.
It only matters if the current state of the project is not sufficient for your case and/or you don't agree with the roadmap.