Your AI tools finally share one memory.

Get started · What it does · Docs · How it works · Coming from v2?

palaia is a hub you run yourself: on a server in your office, in your own cloud account, or on a machine at home. Every AI tool you use connects to it once: Claude, ChatGPT, Codex, Gemini, and any other tool that speaks MCP, the open standard AI tools use to reach outside data and tools. From then on they share one memory and one set of tools, and they can hand work to each other. Your data stays in plain files on hardware you control.

Think Home Assistant, for your AI tools.

[!NOTE] palaia v3 is a release candidate (3.0.0-rc6). Everything below works and is tested. Try it, keep backups, and tell us what breaks. palaia v2 is retired and gets critical fixes only.

What it does for you

• Your AI tools remember, together. Tell one assistant about a decision and the others know it too. Your memory is a folder of plain Markdown notes you can open in any editor (Obsidian opens it as-is), search, and back up like any other files.
• Set up a tool once, use it everywhere. Install an add-on in palaia and every connected AI can use it. No more pasting the same configuration into five apps.
• Your agents can work as a team. An AI session on your laptop can hand a task to one on your server, with the context attached, and find out who is already working on what.
• Runs where you decide. A server in your office, a machine in your cloud account, a NAS, or a Raspberry Pi. No account with us, no subscription, no data leaving your infrastructure unless you say so.
• Safe by default. Your dashboard stays on your private network. ChatGPT and Claude reach only palaia's AI connection, over HTTPS, and sign in with your account. Back everything up with one click.

Get started in 60 seconds

You need Docker. That is the whole prerequisite list.

docker run -d --name palaia-hub \
  -p 8420:8420 \
  -v palaia_home:/data \
  --restart unless-stopped \
  --security-opt no-new-privileges:true --cap-drop ALL \
  --read-only --tmpfs /tmp --tmpfs /run \
  ghcr.io/byte5ai/palaia-hub:beta

Then open http://<your-machine>:8420 in a browser (on many home networks http://palaia.local works too). palaia's setup opens by itself and takes it from there: your first memory, your account, cloud access if you want it, your first AI app. No config files, no second command.

Once 3.0.0 is final, use :stable instead of :beta. Updating later is one click in the dashboard.

Other ways to install

You have…	Do this
A Synology NAS	Paste one file into Container Manager, no terminal: step-by-step guide
A Raspberry Pi	The command above works on 64-bit Raspberry Pi OS with Docker. A ready-to-flash card image is in progress
A rented server (Hetzner, DigitalOcean, AWS, …)	Paste cloud-init.yaml into your provider's user-data field. It installs everything and keeps the hub off the open internet
Umbrel, CasaOS, Runtipi, TrueNAS SCALE	Packages are ready; until they are in the official catalogs, use the command above
Docker Compose or Portainer	docker-compose.yml

Release candidate: the files and packages in this table pin ghcr.io/byte5ai/palaia-hub:stable, which does not exist until 3.0.0 is final. Until then, change :stable to :beta in whatever you use.

Stuck? See Your first shared memory for a walkthrough with screenshots, or troubleshooting.

Works with

Claude Code · Claude Desktop · claude.ai · ChatGPT · Codex · Gemini CLI · Grok · LM Studio · any other MCP-compatible tool

Each one has a short connect guide. Claude Desktop gets a one-click bundle: download, click, connected.

Everything is managed from a dashboard in your browser:

Learn more

• Documentation: getting started, connecting each tool, backup and restore, troubleshooting.
• How it works: the full feature list, the architecture, the test evidence behind the claims, and when palaia is not the right fit.
• Security and the threat model.
• What is left before 3.0.0 and what shipped.
• For contributors: CONTRIBUTING.md and v3/README.md for the dev setup.

Already using palaia v2?

palaia v2 is the Python package at the root of this repository. It is retired: it gets no new features, v3 replaces it, and only a critical fix (security, data loss, a broken release) can still land. It stays installable, and its documentation is unchanged. When you are ready, one command imports your v2 knowledge into v3, and the migration guide covers what changes and how to roll back.

Community & support

• Questions, bugs, ideas: open an issue.
• Security vulnerabilities: please do not open a public issue. Use GitHub's private vulnerability reporting instead. Details in v3/SECURITY.md.

License

MIT · © 2026 byte5 GmbH