Your everyday AI assistant — proactive, private, on your own machine, with your own model.

Chat like ChatGPT. Then let it work for you: routines that run on their own, pages and prices it keeps an eye on, and a memory of what matters to you.

No server? Start your Mav in the cloud — MyMav (9 €/month, your own model key) or CloudMav (19 €/month, model included). Compare the plans.

Or run it yourself, free: curl -fsSL https://raw.githubusercontent.com/SoaOaoS/mav/main/get.sh | sudo bash

Try it in your browser: live demo (sample data, nothing to install) · Website & docs: https://getmav.dev/ · documentation

What it does

• Chat — a clean, ChatGPT-style web app (installable on your phone). Chats are titled automatically and grouped by day; type / for commands.
• Helpers — you talk to the Assistant by default. It calls in the Researcher (web, facts, comparisons), Writer (messages, emails), Planner (days, trips, to-dos) or Money (budgets, purchases) when useful — or you pick one yourself. You always see who is answering.
• Memory — Mav learns facts about you and recalls them, and relevant past chats, in new conversations. See, add and delete everything on the Memory page, or type /remember … in a chat. Stored in Postgres on your machine.
• Routines — "every morning at 7, tell me if I need an umbrella". Create them from a simple form, a ready-made template, with /routine, or just say it in a chat and confirm (English, French or Spanish). Schedules can be daily, weekly, monthly (a day, or the last day of the month), every few hours, or triggered by an incoming event (a webhook). A routine can also be conditional — "only if it's going to rain". Each routine has its own chat you can open and follow up in, and you get a push when it has something for you.
• Proactivity — Mav ranks what it finds (critical, important, useful, fyi) so more proactivity never means more noise. Set how far it can go: Quiet only interrupts for what's critical, Chatty also sends the small stuff; anything below your level is collected into one daily recap.
• Drafts & background actions — when Mav spots a mail to answer or a follow-up to send, it prepares a draft for you to review. Ask for something long and it runs in the background, then comes back with the result.
• Keep an eye on — a web page, a product price (optionally only below a target), or a news topic. Alerts only when something actually changes.
• Daily briefing — every morning (Settings → General, your time), one short message: the weather where you live, what happened since yesterday (alerts, routine reports), what needs you (drafts to approve), something from your interests. Or anytime: Brief me on the new-chat screen, /brief.
• For you — the new-chat screen shows your latest routine reports and alerts, each with Tell me more.
• Your model — Anthropic, OpenAI, Ollama (local or cloud), OpenRouter or any OpenAI-compatible API. Switch anytime from Settings → Model: no terminal.
• Connections — 60+ apps and services ready in Settings → Connections, each with a step-by-step guide: web search, Wikipedia, weather, maps and flights, Notion, Todoist, Linear, Slack, Jira, HubSpot, Zapier, GitHub, Stripe, stock and crypto prices, Home Assistant and more. Fill in a key, or just sign in for the services that support it — or add any MCP server yourself.
• Know what it costs — Settings → Usage shows this month's spend, tokens and a 30-day chart, split between chats, routines and background work. Set a monthly budget (warn at 80 % / 100 %, or stop), and pick a cheap model for background work (titles, memory, summaries).
• Always up to date — a button tells you when a new version is out and installs it for you; changes that need a restart show a Restart assistant bar until you apply them.

Screenshots

_{Chat · Mav on a phone · Routines · Memory. Shown with sample data.}

Install

With Docker (any machine with Docker Compose)

git clone https://github.com/SoaOaoS/mav.git && cd mav
cp .env.example .env          # optional: port, database password, time zone, model
docker compose up -d

Open http://<your machine>:8787. You choose a password, then a short welcome connects your model and sets up your first routines. Everything Mav keeps lives in two volumes (mav-data, pgdata) and survives restarts and updates.

• Update: docker compose pull && docker compose up -d.
• Logs: docker compose logs -f.
• Ollama on the same machine: use http://host.docker.internal:11434/v1 as its address.
• Images: published for every release at ghcr.io/soaoaos/mav (amd64 and arm64, so a Raspberry Pi 4/5 works too). Without a published image, Compose builds one locally.
• From your phone: push notifications need HTTPS. Put Mav behind your usual reverse proxy (Caddy, Traefik, Nginx Proxy Manager), or reach it through Tailscale.
• Already installed with the installer? sudo ./scripts/migrate-to-docker.sh moves everything to Docker: chats, memory, routines, model, keys and password. See Moving to Docker.

With the installer (Linux with systemd)

On Debian, Ubuntu, Arch (Omarchy, Manjaro…) or Fedora — a home server, a mini PC, a VPS:

curl -fsSL https://raw.githubusercontent.com/SoaOaoS/mav/main/get.sh | sudo bash

or

git clone https://github.com/SoaOaoS/mav.git && cd mav && sudo ./install.sh

The setup asks only what it must:

1. Your model provider (arrow keys), your API key — checked live — and the model, picked from the provider's own list. Or set it up later in the dashboard.
2. Optionally, a contact email for push notifications.

Everything else gets sensible defaults (an Advanced settings? prompt lets you change the user, ports and quiet hours). Then it installs and starts everything; details go to /var/log/mav-install.log. Open the address it prints, and say hello.

Manage it

mav status        # what's running, the address, the model
mav doctor        # check everything, with a hint for each problem
mav update        # install the latest release, keep your settings
                  #   --check · --local (no download) · --channel main · --force
mav version       # installed and latest version
mav restart [engine|worker|web]
mav logs [engine|worker|web|install] [-n 50]
mav backup        # memory, routines and settings → /var/backups/mav/
mav password      # set or reset the password of the web app
mav reconfigure   # change the model, or re-run the setup
mav uninstall     # remove the services (your data is kept)

Updates can also be installed from the web app (sidebar → Update to vX.Y.Z).

Unattended install: sudo ./install.sh --yes with MAV_PROVIDER (anthropic, openai, ollama, ollama-cloud-api, openrouter), MAV_PROVIDER_APIKEY, MAV_OPENCODE_MODEL, and optionally MAV_PROVIDER_BASEURL, MAV_VAPID_EMAIL. --dry-run shows what would happen.

How it works

   Browser / phone (PWA)
          │
          ▼
   ┌──────────────────┐      ┌──────────────────────┐
   │  mav-dashboard   │ ───► │  mav-server          │
   │  web app + API   │      │  opencode agent      │
   └──────────────────┘      │  engine (:4096)      │
          │                  └──────────────────────┘
          │                            ▲
          ▼                            │
   ┌──────────────────┐      ┌──────────────────────┐
   │  Postgres        │ ◄─── │  mav-worker          │
   │  memory, alerts  │      │  routines, watching, │
   └──────────────────┘      │  push notifications  │
                             └──────────────────────┘

Service	Role
mav-dashboard	the web app and its API
mav-server	the agent engine (opencode)
mav-worker	runs routines and "keep an eye on", sends notifications

The web app is protected by a password you choose on your first visit. Everything runs on your machine. The only thing that leaves it is what you send to the model provider you chose — or nothing at all with a local Ollama.

Security

Static analysis (CodeQL) and a supply-chain posture check (OpenSSF Scorecard) run on every push to main; secret scanning and push protection are enabled. To report a vulnerability privately, see SECURITY.md.

Versions

Every push to main is tagged with a semantic version and published as a GitHub release (.github/workflows/release.yml). The bump comes from the commit messages, written as Conventional Commits:

Commit	Release
feat!: … or a BREAKING CHANGE: footer	major — v1.4.2 → v2.0.0
feat: …	minor — v1.4.2 → v1.5.0
anything else (fix:, docs:, chore:, merges…)	patch — v1.4.2 → v1.4.3

get.sh, mav update and the update button install the latest release, from the mav-vX.Y.Z.tar.gz archive attached to it. GitHub counts how many times these archives are downloaded (installs and updates, anonymously), and the downloads badge above shows the total. Nothing is sent from your machine: this is GitHub's own download count. CI (.github/workflows/ci.yml) runs shellcheck, syntax checks and the tests in tests/ on every pull request.

Repository

mav/
├── get.sh              # "curl | bash" bootstrap
├── install.sh          # the setup wizard
├── docker-compose.yml  # the Docker install (Dockerfile, docker/entrypoint.sh)
├── agents/             # the everyday helpers (Assistant, Researcher, …)
├── bot/                # mav-worker: routines, watching, memory, notifications
├── dashboard/          # the web app (front-end + server/)
├── scripts/mav         # the mav command
├── scripts/            # database schema, version helper
├── tests/              # unit and script tests (run by CI)
├── systemd/            # service templates
└── docs/               # website, docs, roadmap (ROADMAP.md), brand (BRAND.md), screenshots

Hacking on the web app without a model: run python3 dashboard/tools/fake_engine.py and point the dashboard at it with OPENCODE_URL=http://127.0.0.1:4096 (see dashboard/README.md).

License

MIT — see LICENSE.