Self-Hosted AI Agents

A curated list of open source AI agents you can run on your own hardware, with local models and no cloud account.

View the Project on GitHub Gingerbreadfork/self-hosted-ai-agents

Self-Hosted AI Agents

A curated list of open source AI agents you can run on your own hardware. Every entry here is self-hosted: you install it on a machine you control, it keeps its data there, and most of them work with local models through Ollama, llama.cpp or any OpenAI-compatible endpoint, so nothing has to leave the house.

The list covers personal assistants that live in your chat apps, coding agents, research and browser agents, visual workflow builders, chat interfaces with tool use, voice agents, the frameworks people build agents with, and the runtimes that serve the models. Archived projects are left out. Star counts are not listed because they go stale; each link goes to the live repo.

Contents

Personal assistants and autonomous agents

Agents that run as a long-lived process on your machine and talk to you through a terminal, Telegram, Discord, WhatsApp, Slack or a web page. They remember, schedule, browse and act.

Coding agents

Agents that read, write and run code in your repositories. All of these can point at a local or self-hosted model.

Research agents

DeerFlow, listed above under assistants, is also a long-horizon research harness.

Browser agents

Visual builders and workflow platforms

Low-code tools for building agents and automations in a browser, all installable with Docker.

Chat interfaces with agents and tools

Self-hosted chat UIs that go past plain chat: tool calling, agents, document search, MCP.

Voice agents

Agent frameworks

Libraries for writing your own agents. None of these are hosted services; your code runs where you run it.

Memory for agents

Letta, listed above under frameworks, is built around long-term memory and can serve as the memory layer on its own.

Local model runtimes

The engines that serve a model to all of the above without an API key.

Choosing one

You want Start with
An assistant in Telegram, Discord or WhatsApp that remembers you OpenClaw, Hermes Agent, ZeroClaw, nanoclaw
The same, but every agent sandboxed in a container nanoclaw, Agent Zero
No cloud APIs at all, local models only agenticSeek, Jan, AnythingLLM with Ollama
An agent that works in your code OpenHands, opencode, goose, Cline
Drag-and-drop automations with AI steps n8n, Dify, Langflow, Activepieces
A chat UI for the whole household or team Open WebUI, LibreChat
To write your own agent in Python LangGraph, CrewAI, smolagents, Pydantic AI
A voice assistant you host Pipecat, LiveKit Agents, TEN

Running agents locally

Most agents need three things: a model endpoint, a place to run, and somewhere to keep state.

Model. Install Ollama or LocalAI from the runtimes section and pull a model. A 7B to 14B model runs on 16 GB of RAM or an 8 GB GPU; 30B and up wants 24 GB of VRAM or a Mac with 32 GB or more. Any agent that accepts an OpenAI-compatible base URL will talk to it.

Runtime. Nearly everything here ships a Docker Compose file. A small home server, a NAS with Docker, or a spare mini PC is enough for the agent itself; the model is what needs the memory.

State. Agents keep memory, logs and credentials on disk. Put that directory on a volume you back up, and keep the agent on a network you trust, since many of them can run commands and browse.

Questions

What is a self-hosted AI agent? A program that uses a language model to take actions on your behalf, running on hardware you control rather than a vendor’s cloud. The model can be local or remote; the agent, its memory and its tools stay with you.

Can a self-hosted agent run without any cloud API? Yes. Pair any agent above that accepts an OpenAI-compatible endpoint with Ollama, llama.cpp or LocalAI serving an open model. agenticSeek, Jan and AnythingLLM are built for exactly that.

What hardware do I need? The agent itself is light. The model is the cost: 8 GB of VRAM or 16 GB of unified memory runs small models well, and quality climbs with memory. A home server can run the agent while a desktop with a GPU serves the model.

How is this different from a chatbot? A chatbot answers. An agent has tools: a shell, a browser, your files, your calendar, other agents. The projects in the first section are the ones that act without being asked each time.

Contributing

Additions welcome. A project belongs here if it is open source, can be installed and run on your own machine, and is an agent or something agents are built from or run on. See contributing.md.