Modules
Everything in modAI is a module. There is no separate core — the chat UI, authentication, AI provider connections, and all other features are each their own module, wired together through configuration.
Adding a new module works exactly the same way as the built-in ones.
modAI splits into two halves: the frontend runs in the user's browser and handles everything visible, while the backend runs on the server and manages data, AI connections, and business logic. The two communicate over HTTP and server-sent events (SSE) for streaming.
Both halves are fully modular — read on to see which modules make up each side.
Backend Modules
Backend modules run on the server — they provide API endpoints, manage data, and connect to external services.
The diagram above shows the default modAI backend — the full set of modules that ship out of the box and how they depend on each other. This combination is what makes modAI work as a whole. Leaving out a module removes exactly the functionality it provides. There is no hidden core: every feature is a module.
Frontend Modules
Frontend modules run in the browser — they render UI, manage navigation, and talk to the backend.
The diagram above shows the default modAI frontend — the full set of modules that ship out of the box and how they depend on each other. This combination is what makes modAI work as a whole. Leaving out a module removes exactly the functionality it provides. There is no hidden core: every feature is a module.
Installing Additional Modules
A module's documentation must clearly state whether it is a backend module, a frontend module, or both.