Your team's memory, in Git.Fed by your AI assistants, tidied by AI every night.
Synaptane is a self-hosted wiki: Markdown first, and all your files, PDFs and scans included, all searchable. Your AI assistants search it and save what they learn over MCP; every night an AI agent files their notes into the right pages, in a Git commit.
How it works
From a conversation to the wiki, and back
What your team explains to its assistants no longer vanishes when the chat ends. Follow one note from Tuesday afternoon to Wednesday morning.
Tuesday, 4:10 PM
Saved from the conversation
Hugo tells Claude the NAS now has 16 TB and asks it to save that for the team. Claude drops a note into the IT space’s inbox, over MCP.
We put four more disks in the NAS: 16 TB usable now, still RAID 6. Save this for the team.
inbox_addacme/itNote in the inboxNAS capacity raised to 16 TBSuggested place:infra/storage.mdSaved in the inbox of
acme/it. It will be filed tonight; a page already covers this: Storage.That night, 2:00 AM
Filed overnight
The tidy-up agent reads the inbox, finds the existing Storage page and updates it instead of creating a duplicate. One commit, pushed to your Git repository.
Inbox
- NAS capacity raised to 16 TBreading…filed
- VM backupsfiled
- No deployments on Friday afternoonsfiled
3 filed, 0 left
content/infra/storage.md# Storage
-
The NAS in rack B provides 8 TB of usable space in RAID 6.+The NAS in rack B provides 16 TB of usable space in RAID 6, since four disks were added on 1 October 2026.
It receives the vzdump backups and hosts the team’s file shares. Shares are mounted from nas.acme.internal.
A replacement by distributed storage is being studied: see the [Ceph project](../projects/ceph.md).
4e1b7c2Tidy-up: 3 item(s) filedWednesday, 9:15 AM
Found the next morning
Inès asks her own assistant about the NAS. It searches Synaptane and answers from the Storage page, with a link to it.
How much usable space does the NAS have?
search"NAS"Storageacme/it/infra/storage.mdThe NAS in rack B provides 16 TB of usable space in RAID 6…The NAS has 16 TB of usable space, in RAID 6, since four disks were added on 1 October 2026.
Source: Storage
infra/storage.md
Features
A wiki your assistants read, feed and keep tidy
Markdown pages first, with all your files next to them. Everything else is built around them, and around the assistants your team already uses.
Git is the source of truth
Each space is a Git repository, on GitHub, GitLab, Gitea or any host. Its content/ folder holds Markdown pages and your original files, which you can read, grep and clone without Synaptane. Every change is a commit.
Git repositoriesBuilt for AI assistants
An MCP server with 20 tools and 3 prompts, over OAuth 2.1 or personal tokens. Tested with Claude.ai, Claude Desktop, Claude Code and ChatGPT. A connection can be read-only or limited to some spaces.
Connect an assistantInbox and nightly tidy-up
Notes from assistants, the web UI or the API wait in an inbox. Every night an AI agent files them, updates existing pages, fixes links and commits. Deletions are capped, an optional monthly budget (€20 suggested) limits spending, and a run can be undone in one click.
How the tidy-up worksScheduled routines
Agents that run on a schedule, such as a weekly consistency check or a Friday digest. They write a report page, drop items into the inbox, send an email or call a webhook.
RoutinesSearch that finds things
Full-text search with accent folding and light stemming, across pages and the text of PDFs, Office files and images, scans included (OCR). Optional search by meaning with pgvector, and related pages on every page.
SearchKnowledge you can trust
Page owners, verification dates and review cycles. A health tab lists broken links, orphan pages and pages to review. Probable secrets are refused before any commit.
Verified pagesBring your own model
Anthropic, OpenAI, Mistral, Ollama or any OpenAI-compatible endpoint, with a monthly budget per organization. Without a provider, the wiki, search, the inbox and MCP still work.
AI providersMade for teams
Organizations, spaces and roles, email invitations, single sign-on with OIDC, GitHub, GitLab or Google. A REST API with its OpenAPI schema (optional), and signed webhooks.
Single sign-on
Files
Your files, all searchable
Markdown is the heart of the wiki, but a space holds any file, versioned in Git like a page. Synaptane shows each one at its best and reads its text, so that you and your assistants find it.
Markdown pagesThe heart of the wiki
.md
Written by your team, your assistants and the nightly tidy-up. Everything else is built around them.
- In the wiki
- Rendered pages with links, backlinks, an outline, verification and related pages
- Search
- Full text
- AI assistants
- Read and write; the tidy-up writes Markdown
PDF
.pdf, scans included
- In the wiki
- Built-in viewer, in the page
- Search
- Its text, or OCR for scanned pages
- AI assistants
- Read the extracted text
Word, PowerPoint, Excel
.docx .pptx .xlsx .odt .odp .ods .doc .ppt .xls
- In the wiki
- Download link, with the extracted text below
- Search
- Extracted text
- AI assistants
- Read the extracted text
Images
PNG, JPEG, GIF, WebP, AVIF, BMP, SVG
- In the wiki
- Displayed, alone or in the pages that embed them
- Search
- Text in the image, by OCR (not SVG or AVIF)
- AI assistants
- Read the OCR text
HTML pages
.html .htm
- In the wiki
- Rendered in an isolated frame, source one click away
- Search
- Words
- AI assistants
- Read and write
Text files
CSV, JSON, YAML, code, logs…
- In the wiki
- Syntax highlighting, editable like a page
- Search
- Words
- AI assistants
- Read and write
Everything else
archives, videos…
- In the wiki
- Stored, versioned in Git, downloadable
- Search
- File name
- AI assistants
- Listed
Three ways in
- The web interfaceAdd a file to any folder, up to 25 MB.
- Your assistantsAttachments of a note dropped over MCP or the API, filed by the tidy-up.
- A git pushA file in the content/ folder is a file in the wiki.
Text becomes searchable a few seconds to a few minutes after a file arrives. On spaces where search by meaning is on, it covers all of this text, pages and documents alike. The old .doc, .ppt and .xls formats are read too, the text boxes, tables and speaker notes of a .ppt included; a file protected by a password has no text.
Get started
Running in three steps
On Linux, or WSL2 on Windows, with Docker. This starts a local instance with the demo wiki of Acme, a fictional IT team.
- Get the releaseClone the tagged release: it holds the Compose file, the nginx configuration and the server scripts.
- Write a minimal
.envA local address, a random database password and the image version. The last line lets the demo use a local Git repository: keep it for a throwaway instance. - Start and load the demoThen open
http://localhost:8000/o/acme/itand sign in with the password the command prints.
For a real server, skip the demo line, create the first account withsynaptane admin create, serve it over HTTPS and run synaptane doctor. The guide covers the two proxy modes, upgrades and encrypted off-site backups.
# 1. Get the release
git clone --branch v1.0.0-rc.1 https://github.com/synaptane/synaptane.git && cd synaptane
# 2. Write a minimal .env (the last line is for the demo only)
printf 'PUBLIC_URL=http://localhost:8000\nPOSTGRES_PASSWORD=%s\nSYNAPTANE_VERSION=1.0.0-rc.1\n' \
"$(openssl rand -hex 24)" > .env
echo 'COMPOSE_FILE=compose.yaml:examples/compose.demo.yaml' >> .env
# 3. Start, then load the demo wiki
docker compose up -d
docker compose exec app synaptane demoThe tidy-up needs an AI provider; the wiki, search, the inbox and MCP work without one.
Screenshots
Inside the application
Screenshots taken on the demo data set. Acme and its people are fictional.
(full-size image)Ctrl+K search across all your spaces, by words or by meaning.
(full-size image)PDF viewer: a contract opens in its page, and its text is indexed.
(full-size image)Office documents: a download link, and the extracted text that search uses.
(full-size image)Scans: a scanned delivery note, and its text read by OCR.
(full-size image)Inbox: notes and direct changes waiting for the nightly tidy-up.
(full-size image)History: every change is a Git commit, with its diff.
(full-size image)Wiki health: broken links, orphan pages, pages to review.
(full-size image)Connect an assistant over MCP, and see its calls arrive.
(full-size image)Routines: scheduled agents, such as a weekly consistency check.
Comparison
How Synaptane compares
Each of these tools is good at what it does. This table only covers what Synaptane is built around: your own server, files you own, assistants, and an AI that keeps the wiki tidy.
| Criterion | Synaptane | Notion AI | Confluence + Rovo | Outline | Obsidian | Wiki.js |
|---|---|---|---|---|---|---|
| Self-hosted | Yes: Yes, with Docker Compose | No: No, cloud only | No: Rovo is cloud only; Data Center reaches end of life in 2029 | Yes: Yes | Partly: Desktop and mobile app, no server | Yes: Yes |
| Your content as files you ownReadable without the tool | Yes: Markdown pages and your original files (PDF, Office, images…) in your Git repository, one commit per change | Partly: Through export (Markdown, HTML, PDF) | Partly: Through export (PDF, Word, HTML) | Partly: Through export (Markdown) | Yes: Markdown files and attachments on your disk | Yes: Markdown, with optional Git sync |
| MCP serverFor Claude, ChatGPT and others | Yes: Built in: search, read, write, inbox | Yes: Official, hosted by Notion | Yes: Rovo MCP server (cloud) | Yes: Built in since February 2026 | Partly: Community plugins | No: No official server |
| AI that files new notesOn a schedule, into the right pages | Yes: Every night, in one commit you can undo | Partly: Possible with Custom Agents (Business and Enterprise plans) | Partly: Possible with Rovo agents in Automation rules | No: Not built in | No: Not built in | No: Not built in |
| Teams and single sign-on | Yes: Organizations and roles; OIDC, GitHub, GitLab, Google | Yes: SAML SSO on Business and Enterprise plans | Yes: SSO with Atlassian Guard | Yes: Sign-in through Google, Slack, Microsoft or OIDC | Partly: Shared vaults with paid Sync; no SSO | Yes: OIDC, SAML, LDAP and more |
| Open source license | Yes: Apache-2.0 | No: Proprietary | No: Proprietary | Partly: BSL 1.1 (source available) | No: Proprietary, free to use | Yes: AGPL-3.0 |
As of October 2026, from each product's public documentation and announcements. These products change quickly: if something here is out of date, please tell us on GitHub Discussions.
Architecture
Simple to run, easy to leave
One application, one worker, PostgreSQL and your Git repositories. If you stop using Synaptane, your wiki is still a folder of Markdown pages and your original files.
- One FastAPI app serves the three interfaces: MCP for assistants, the web UI and the REST API.
- A worker runs the nightly tidy-up, the routines, Git sync, indexing (with text extraction and OCR) and webhooks.
- PostgreSQL holds accounts, permissions, settings and the semantic index (pgvector). The rest can be rebuilt from the repositories.
- The AI provider is optional: only the tidy-up, routines and search by meaning need one.
Open source
Free software, honest about its stage
Synaptane is under the Apache License 2.0. The code, the documentation and this website are on GitHub, and contributions are welcome: commits are signed off under the Developer Certificate of Origin.
Synaptane is a preview (v1.0.0-rc.1, the first public release), maintained by one person on a best-effort basis. The REST API, the MCP tools and the configuration may still change: back up before each upgrade.
- Read the codesynaptane/synaptane on GitHub
- ContributeHow to propose a change
- Ask a question, share an ideaGitHub Discussions
A hosted Synaptane? It is being considered. If you would use one, tell us on GitHub Discussions.
Give your assistants a memory your team owns.
Your pages and your documents, searchable, in a Git repository that stays yours. Start with the demo on your own machine, or read the documentation first.

