
# Your data. Your AI.
**AutoBot is a self-hosted AI platform you own — not a service you rent.**
Feed it your docs, your codebase, your business knowledge.
Plug in any LLM you trust — local or hosted.
Your data stays on your machines. Your AI stays yours.
[Get Started](#quick-start) · [Documentation](docs/) · [Community](https://github.com/mrveiss/AutoBot-AI/discussions) · [Sponsor](https://github.com/sponsors/mrveiss)
[](https://github.com/mrveiss/AutoBot-AI/actions/workflows/docker-smoke-test.yml)
[](https://codecov.io/gh/mrveiss/AutoBot-AI)
[](https://github.com/sponsors/mrveiss)
[](LICENSE)
---
> **AutoBot is infrastructure you own, not a subscription.**
> A small, solid core. A management layer that runs the hard infrastructure for you.
> Modules you install on top. Deploy it once, feed it your knowledge, connect whatever
> LLM you trust, and run it forever — on your terms.
| What you get | What stays yours |
|---|---|
| Chat interface | Your prompts |
| RAG knowledge base | Your documents |
| Service lifecycle management (SLM) | Your infrastructure |
| Modules (Company OS, Codebase Analytics, Transcriber) | Your data |
## Why, How, What
- **Why.** Private AI you trust with your business knowledge shouldn't require handing that
knowledge — or control of the intelligence itself — to someone else's server.
- **How.** A small, stable Core (RAG + knowledge-graph memory, a provider-agnostic LLM gateway
with fallback, governance) plus a management layer that absorbs deploy/operate/scale, plus
Modules that inherit all of it instead of rebuilding it.
- **What.** A self-hosted AI platform — chat, a private knowledge base, a fleet-management
dashboard, and installable modules. Apache-2.0. No subscription.
## The Platform Model
AutoBot is three layers, bottom to top:
1. **Platform Core** — small, solid, and yours. Chat and streaming, a RAG knowledge
base backed by a knowledge graph (your *institutional memory*), an LLM gateway with
provider fallback, local inference, hooks, and governance (auth, RBAC, review gates,
budgets). It changes slowly so everything above can depend on it.
2. **Management Layer — Service Lifecycle Manager (SLM).** Private AI has a lot of
moving infrastructure: vector DB, cache, database, inference, and background workers,
often across several machines. The **Service Lifecycle Manager (SLM)** owns the full
lifecycle — **deploy → operate → scale** — so you can run it in production without
becoming a full-time operator. *(SLM means Service Lifecycle Manager, never "small
language model.")*
3. **Modules** — installable capabilities built on the core's bones. A module inherits
institutional memory, local inference at zero marginal cost, hooks, and governance,
so it stays small relative to what it delivers. Modules include **Company OS** (an
autonomous *agent-company*), **Codebase Analytics**, and the **Transcriber**.
→ Full picture: [The AutoBot Platform Model](docs/architecture/PLATFORM_MODEL.md)
## Quick Start
**Which path?** On a dedicated Ubuntu host, use the one-line installer (Option A). On
anything else, use Docker (Option B). Hardware and OS requirements are in one table:
[INSTALL.md#requirements](INSTALL.md#requirements).
**Option A — One-line installer (dedicated Ubuntu host).** Deploys the **Service Lifecycle
Manager (SLM) control plane** — Postgres, the SLM backend and nginx. The SLM then
provisions the platform onto your fleet nodes; it is not the platform itself:
```bash
curl -fsSL https://raw.githubusercontent.com/mrveiss/AutoBot-AI/main/install.sh | sudo bash
```
When it finishes, the installer prints your **SLM URL** (`https://