Question about Litestar’s Long-Term Vision and Enterprise-Level Feature Support

[null-ed]

Hello Litestar team 👋

First of all, thank you for building Litestar — it is a very well-designed, high-performance Python web framework, and I really appreciate the work you are doing for the Python ecosystem.

I would like to ask about Litestar’s long-term roadmap and vision, especially regarding enterprise-level, out-of-the-box capabilities.

In other ecosystems, there are mature frameworks that provide a relatively complete enterprise experience:

• Java: Spring Boot / Spring Cloud
• .NET: ABP
• Node.js: NestJS

In comparison, the Python ecosystem currently lacks a framework that is both feature-complete for enterprise applications and high-performance / async-first.
While Django is powerful, it has some limitations for modern enterprise use cases, such as:

• Limited async-first support
• No built-in multi-tenancy model
• No Unit of Work pattern
• Missing standardized solutions for many cross-cutting concerns

Given Litestar’s strong architectural foundation, I’m curious whether the project intends to support (either officially or via first-class extensions) some of the following capabilities in the future:

• User, Role & Permission Management (RBAC)
• Multi-Tenancy & Tenant Management
• Unit of Work pattern
• Feature Management System
• Application / Tenant Setting Management
• Audit Logging
• Background Jobs
• Background Workers
• Localization / Multi-Language Management
• Distributed Event Bus
• Distributed Locking
• BLOB Storage Abstraction
• Virtual File System
• Unified Exception Handling
• Email & SMS Abstractions with Templating Support
• Soft Delete support

I fully understand that Litestar may intentionally focus on being a core framework rather than an “all-in-one platform”.
My main questions are:

• Does Litestar aim to become an enterprise-ready foundation similar to NestJS or Spring Boot?
• Are there plans for official modules, recommended patterns, or an ecosystem to cover these cross-cutting concerns?
• Or is the long-term direction to stay minimal and let the community handle these areas independently?

Any insight into the project’s vision or roadmap would be greatly appreciated.

[JacobCoffee]

User, Role & Permission Management (RBAC) - litestar-users is a nice 3rd party option

[provinzkraut]

Does Litestar aim to become an enterprise-ready foundation similar to NestJS or Spring Boot?
Are there plans for official modules, recommended patterns, or an ecosystem to cover these cross-cutting concerns?
Or is the long-term direction to stay minimal and let the community handle these areas independently?

I don't like the term "enterprise-ready". Litestar, and definitely Django, are being used by enterprises already, quite successfully.

As for the second part of that question: No. Litestar is not trying to evolve into NestJS or Spring Boot. Litestar is going to stick roughly with the same scope it has at the moment. It's not as minimal as Flask or FastAPI, but also not as featureful as Django or Spring.