Folio

Folio

The open-source alternative to Notion and Confluence. Your team's wiki lives in Git. People write in the browser, together, in real time. AI agents read and write the same pages. One command to run it yourself.

Website: https://foliowiki.online · Featured in Self-Host Weekly (9 Oct 2026)

👉 Try the live demo

No install, no sign-up: open it and pick Sam on the sign-in screen. Shared login, data resets every 24 hours; don't enter personal data or API keys.

git clone https://github.com/evergreen-it-dev/folio.git

cd folio docker compose up -d

Open http://localhost:4870, create the first account, start writing.

Not ready to install? Try the live demo first.

---

Why Folio

• You own the content. Every page is a plain file in a Git repository you control. No export step, no lock-in: stop using Folio tomorrow and the files are still there, readable in any editor.
• It works the way a wiki should. Real-time editing, a page tree, search, access rights, history, sharing — and it keeps working offline.
• Agents are first-class users. Not a chatbot bolted on the side: a built-in assistant, your own agent in every space, a full MCP server, and Markdown links made for agents.
• Documents, tables, whiteboards, diagrams and files in one tree. A roadmap table next to the spec, next to the architecture board, next to the signed PDF. Obsidian canvases and bases open as pages, too, and so do the interactive artifacts your agents make.
• See how your pages connect. A graph of the space and a local graph beside every page, built from the links your team already writes, and showing only what the reader may open.
• Built for teams. Groups, single sign-on with OpenID Connect and SAML 2.0, SCIM provisioning, an audit log and page restrictions that child pages inherit.
• Publish what should be public. Turn a space into a read-only website, with search and an optional "Ask AI" for visitors, at a path of your instance, on a subdomain or on your own domain.
• One command to run. Docker, and nothing to configure for a first start.

---

See it in action

Short walkthroughs, no slides. The voice in the videos is synthetic.

• A team wiki that lives in Git — edit a page in the browser, press Sync, and it is a real Git commit; a teammate edits from the terminal and the change shows up on the page (0:37)
• An AI agent updates your wiki over MCP — one request: the agent reads the release process, writes release notes and adds a roadmap row (0:53)
• Onboarding a sales rep with Folio AI — answers from the team's own pages with sources, a weekly check as a form, and the results in a table (1:22)
• Whiteboards that live in Git — draw together, embed the board in a document, and keep every version in history (0:51)
• Docs as code without the IDE — the docs/ folder of a product repository becomes a space; a technical writer edits it by hand and with Folio AI, an agent adds a release entry over MCP, and the developer reads the commits with git pull (1:36)
• Publish a space as a public website, with Ask AI for visitors — one setting makes a space a read-only site on a path, a subdomain or your own domain; visitors search it, download pages and ask Folio AI (1:21)
• The editor and Mermaid diagrams — live Markdown, a source view of the same page, and diagrams you edit visually or as code (1:04)
• Is your wiki's AI assistant helping? Folio AI analytics — instance admins see rated conversations and unanswered questions, add the missing page, and the same question gets an answer with its source (1:21)
• Publish Claude artifacts into your team wiki — one casual line to Claude Code: the dashboard becomes an interactive page of the wiki, keeps the reader's filters after a reload, is a folder in Git, and opens for a guest by a share link (1:33)

---

Git-first, all the way down

Most wikis keep your content in a database and offer Git as an export. Folio does the opposite: the Git repository is the wiki. The database holds the index, access rights and the state of live editing — never the only copy of your words.

This is what a space looks like on disk:

acme-handbook/

├── index.md ├── welcome-to-acme.md ├── engineering.md ├── engineering/ │ ├── onboarding-checklist.md │ ├── release-process.md │ ├── incident-runbook.md │ └── how-folio-fits-together.excalidraw.svg ← a whiteboard ├── meeting-notes.md ├── meeting-notes/ │ └── product-sync-september-28.md ├── roadmap.table.md ← a data table ├── onboarding-feedback.table.md ├── onboarding-feedback/ │ └── onboarding-feedback.form.md ← a form ├── security-policy.md ├── security-policy.pdf ← files are pages too └── security-policy.docx

And this is its history — ordinary commits, with the people who made the changes as authors:

$ git log --format='%h  %an  %s'

be529a0 Maria Chen folio:update aeac3bb Maria Chen folio:update 6c2c061 Sam Rivera folio:update 026d9ec Maria Chen folio:update ... 4e9ec49 Folio init: create space

What that gives you:

• Edit anywhere. Change a page in the browser or in your IDE and push — both land in the same history. Links between pages are ordinary relative Markdown links, not a private dialect.
• Bring your own repository. Start with an empty space, clone an existing repository, or connect one later. Several spaces can share one repository, each in its own folder — so documentation can live right next to the code.
• Review like code. Merge requests, blame, diff and revert work on your wiki because it *is* a repository.
• Docs-as-code friendly. Front matter keys written by Docusaurus, MkDocs, Hugo or Jekyll are kept byte for byte; a space bound to a folder such as docs/ writes no ids into your files (a space over a whole repository does); images can be stored in the repository next to the page and linked by a relative path, so GitHub shows them; and moving a page rewrites the links that point to it and the ones inside it, in one commit. A full scenario is in Docs as code, without the IDE.
• Nothing is lost quietly. Sync state is always visible — clean, ahead, behind, conflict — and conflicts are listed for the whole space. "Take the version from Git" resets a space to the remote branch and saves what was there into a backup branch first.
• Readable formats. A whiteboard is an SVG that opens in any browser and still carries the editable scene. A data table is one Markdown file — the column types and saved views in the front matter, the rows as a table you can read:

# Roadmap

---

Docs as code, without the IDE

If your documentation lives in the docs/ folder of a product repository, Folio can show that folder as a space. Writers edit it in a browser, developers keep their IDE and read ordinary commits, and an agent works on the same pages.

• Connect the folder, not the repository. Create a space from the repository URL, choose the branch and pick docs/ as the root path. Only that folder becomes the space: Markdown files are pages; source code and other files are not pages and are never touched. Folio keeps its page ids in its own index, and the only file it adds is a hidden docs/. .folio.
• A writer edits in the browser. Reading, Live edit or Source (plain Markdown), several people on one page, or a request to Folio AI in the side panel. Folio writes each edit to the file at once and commits after about 90 seconds of quiet, or immediately on Sync, to the branch the space follows.
• A developer sees a commit with the author's name. git pull, git log and git blame show the person who edited as the author; Folio is the committer and the message is folio:update. Only the last editor in a window is recorded as author. The developer's own commits come back into the space by fetch roughly every three minutes and on every Sync.
• An agent updates pages through MCP. Claude Code, Cursor or any MCP client connects with a personal access token or through OAuth, reads and edits the same pages with the rights of the token's owner and no more, and the commit carries that person's name.
• The space can become a docs portal. Make it public and the same pages are served as a read-only website with search and, if you switch them on, downloads and "Ask AI" for visitors, see Publish a space as a website.

Where it stops: a space follows exactly one branch and Folio pushes straight to it, without pull requests (point the space at a docs branch if you want review before main; a protected branch makes the push fail and the space shows git's message). A space over the whole repository, with no root path, writes an id into every page and a small file into the repository root, unless an administrator ticks "Light footprint" (a repository with .obsidian/ is detected on its own). Opening a page writes nothing: a file changes only when someone edits it. A page's title comes from its first # heading, then from a front matter title:, then from the file name, and Folio does not add a heading to a page that has none. An id that another tool put in front matter (Docusaurus and Jest use id: intro) never moves a page between spaces. MDX files (.mdx: Nimbus, Starlight, Astro, Docusaurus) are pages like .md ones: import/export lines and JSX components such as or are folded into compact blocks in Live edit, drawn as labelled boxes in Reading, and saved back byte for byte — Folio does not run MDX, it only keeps it intact. Pasted images stay in Folio's asset store until a space administrator turns on "Store images in the repository". See also What is not there yet.

The walkthrough is in the post Docs-as-code without the IDE: edit your repository's docs in a browser and in the video.

---

Write together

Documents, data tables and whiteboards are edited by several people at once. You see who is on the page and where their cursor is; changes appear as they are typed. When the page goes quiet, Folio commits — with the person who edited as the author.

What you type is not lost between Live edit and Reading: the browser keeps a local copy until the server confirms it has your edits. If it cannot confirm them, the header says Not saved and closing the tab asks first.

Comments on text. Select a passage in a document and press Comment: the thread sits beside the page, anyone who can see the page can reply, and an editor (or the person who started it) resolves it. Comments a