As we move into 2026, Abimongo is progressing toward the release of its Dynamic Multi-Tenant feature.
This phase focuses on increasing flexibility and runtime compatibility, allowing developers to integrate Abimongo seamlessly into the environments they already use.
Supported and upcoming runtimes
Next.js
Fastify
Hapi
Koa
Support for serverless platforms, edge runtimes, and GraphQL servers is planned for later this year.
Abimongo is an open-source project, and community contributions are always welcome.
Follow our updates, read the blog, and ⭐ star the GitHub repository to stay informed.
Emmanuel Nodolomwanyi (Creator & Lead Maintainer, Abimongo Ecosystem)
Since Abimongo’s launch, the community response has been incredible. Developers across multiple ecosystems have already begun exploring how its intelligent multi-tenancy, schema abstraction, and real-time hooks simplify complex MongoDB applications.
While v1 successfully laid the foundation for a modern, scalable MongoDB ORM/ODM, the upcoming v2 release will take versatility and interoperability much further — through a new universal adapter architecture designed to integrate seamlessly with diverse runtime environments.
Why Adapters Matter
Today, Abimongo’s multi-tenant API is optimized primarily for Express applications. Although Express remains widely adopted, the modern backend landscape now includes a rich mix of frameworks and execution models:
Microservices (Fastify)
Full enterprise application frameworks (NestJS)
API-centric GraphQL servers
Edge runtimes and serverless platforms
Middleware-driven architectures like Koa and hapi
Developers expect database tools that adapt to their stack— not the other way around.
That is the core direction of Abimongo v2.
Introducing the Adapter Ecosystem (V2 Preview)
Abimongo v2 will introduce a clean, standardized integration layer powered by a shared @abimongo/adapter-types core.
Each adapter maps the underlying framework request shape to Abimongo’s universal tenant context contract, ensuring predictable DX across environments.
Planned official adapters include:
Adapter Package
Target Framework / Runtime
@abimongo/adapter-express
Express 4/5 REST APIs
@abimongo/adapter-fastify
Fastify microservices & servers
@abimongo/adapter-nestjs
NestJS (HTTP + GraphQL)
@abimongo/adapter-graphql
Apollo Server, Yoga, Mercurius, etc.
@abimongo/adapter-koa
Koa 2 middleware-based servers
@abimongo/adapter-hapi
hapi enterprise APIs + gateways
Community adapters will also be supported through a documented adapter contract API.
A Framework-Agnostic Core
At the center of this ecosystem is the new @abimongo/adapter-types package, which provides:
Unified error message format and fault tolerance rules
Optional framework detection & auto-configuration via CLI
Release Timeline
The first public preview (Express, Fastify, NestJS, GraphQL) is scheduled for Q1 2026.
Subsequent releases will introduce Koa, hapi, and edge runtime adapters, followed by community-driven innovation.
If you want early access, feature discussions, or to contribute adapters, now is the best time to get involved.
Final Note
Abimongo v2 represents a major milestone toward a universal, framework-agnostic MongoDB ORM/ODM, designed for real-world multi-tenant workloads and modern distributed applications.
The mission remains unchanged:
Empower developers to manage data complexity — intelligently, securely, and without friction.
Stay tuned for detailed release notes and upcoming preview builds right here on the blog.