Quickstart

Fosnie runs entirely inside your own infrastructure – no data, prompts, or documents leave your perimeter unless you explicitly enable an external connector. Bring your own model (a local LLM via vLLM, Ollama or llama.cpp, or an external API key) and get retrieval-augmented chat, agents, document work, research and voice on top.

Requirements

Docker + Docker Compose v2 (≥ 2.24). ~8 GB RAM with an external model API; ~16 GB for the fully-local stack (--local). Only one port is published (8080).

Option A – one-line install

Downloads a pinned release, generates secrets, and starts the stack.

curl -fsSL https://get.fosnie.dev | sh
# fully local – no API keys, all inference on this host:
curl -fsSL https://get.fosnie.dev | sh -s -- --local

Prefer to read before you run: download install.sh, review it, then sh install.sh.

Option B – manual (Docker Compose)

mkdir fosnie && cd fosnie
curl -fsSL -O https://github.com/Fosnie/fosnie/releases/latest/download/docker-compose.yml
curl -fsSL https://github.com/Fosnie/fosnie/releases/latest/download/example.env -o .env
# edit .env: set POSTGRES_PASSWORD, MESSAGE_ENCRYPTION_KEY (openssl rand -base64 32), ML_SHARED_SECRET
docker compose up -d

First run

Open http://localhost:8080 and create the first account – it becomes the admin. In the default (external-inference) mode an onboarding checklist walks you through adding a model provider under Settings → Providers. With --local, the Ollama + reranker stack is wired up automatically, so chat works immediately.

• Fully-local models: --local adds Ollama (LLM + embeddings) and a llama.cpp reranker; first run pulls the models (a few GB).
• Managed Postgres (Supabase, Neon, RDS, Cloud SQL, Azure): set PAI__DATABASE_URL in .env and drop the bundled postgres service.
• Bare-metal, air-gap bundle, backups, upgrades, reverse-proxy TLS: see the Deployment guides.