System Requirements
Methodius AI is fully customizable in every regard.
Given this customizable nature, your exact requirements to run Methodius AI depend on many factors. You can use the tables below to get a rough idea of what it will take to run Methodius AI.
Methodius AI can be a wrapper around many external services that all accomplish some task - making Methodius AI so lightweight it can run on the smallest machines - even Raspberry Pis!
Recommended configuration for Methodius AI
This is the minimum value for running Methodius AI. This will be enough for you to store some documents, send chats, and use Methodius AI features.
| Property | Recommended Value |
|---|---|
| RAM | 2GB |
| CPU | 2-core CPU (any) |
| Storage | 5GB |
LLM selection impact
This is how you get chat responses. Popular hosted solutions like OpenAI (opens in a new tab) tend to provide state-of-the-art responses with almost zero overhead. However, you will need an API key for any cloud-based LLM provider.
Tip: Host a local LLM on another machine that has a GPU if the device running Methodius AI does not have a GPU. Methodius AI can connect to any LLM running anywhere via API.
Embedder selection impact
This is the model which you use to "embed" or vectorize text. Likewise, external services connected to Methodius AI have zero overhead impact.
Tip: Host a local embedder on another machine that has a GPU if the device running Methodius AI does not have a GPU. Methodius AI can connect to to a provider via API.
Vector database selection impact
All supported vector databases either have no impact as they are externally hosted or can scale to hundreds of millions of vectors at the minimum recommended settings.
the default LanceDB vector database can handle anything you can throw at it