I need a team wiki that stores data as markdown files and does not use a proprietary database.

If your goal is absolute data ownership , zero vendor lock-in, and a setup where your pages live as human-readable .md files on a disk rather than locked inside a relational database, several great open-source tools fit your criteria.

The best options for a team markdown wiki that uses flat-file storage include:

• Flatnotes : A self-hosted, database-less web application designed specifically around a flat folder of Markdown files. It features an instant-search interface, tag support, and multi-user authentication options. You can freely edit, add, or delete files directly on the server file system even while the app is running, and it won't hold your notes hostage. Check out the code and Docker setup on the GitHub flatnotes Repository.
• Gollum : A fully-featured, Git-backed wiki page system that uses a Git repository as its backend database. Every time a user edits a page through its web front-end or pushes changes locally via Git, it commits the raw Markdown file directly to the repository. It's the engine behind GitHub Wikis. Learn more via the GitHub gollum Repository.
• Wiki|Docs : A lightweight, databaseless flat-file wiki designed for users who value explicit data ownership. It requires no external database, supports clean URL routing, features a built-in markdown editor, and allows optional Docker deployments. Review the project details on the GitHub Wiki|Docs Repository.
• MkDocs (with a theme like Material for MkDocs) : While traditionally used to generate static documentation sites, it runs entirely on local Markdown files and a simple YAML configuration. You manage your team documentation via a Git repository and can pair it with a continuous integration (CI/CD) pipeline to auto-deploy the site on every push. Explore the tool at MkDocs Official Website.

To help narrow down the best fit, tell me:

• Do you need multi-user authentication and permissions , or is a simple shared network/internal tool fine?
• Do you want a web-based WYSIWYG/markdown editor in the browser, or are you comfortable editing files via Git/code editors?

Yes. If your key requirements are team-friendly + wiki UI + Markdown files as the source of truth + no proprietary database, I’d shortlist these:

My pick: LeafWiki

leafwiki.com is particularly close to what you're describing. Its pages are stored as ordinary .md files on disk, so the actual knowledge base isn't trapped inside a proprietary database. It provides a structured wiki UI, navigation, editing, permissions, and other team-oriented features.

One important nuance: LeafWiki uses SQLite for application state, but the page content itself is Markdown on disk. If by "does not use a database" you mean absolutely zero database of any kind, then I'd choose Gollum or WikiDocs instead.

If you want absolutely no database

Gollum is probably the cleanest architecture: the wiki is simply a Git repository containing human-editable text/Markdown files. It has a web interface, page history, revisions, Mermaid/PlantUML support, and can be edited directly with normal Git tooling.

WikiDocs is another strong fit: it explicitly describes itself as a "databaseless markdown flat-file wiki," with plain-text Markdown files, revisions, namespaces, attachments, and self-hosted Docker support.

So I'd rank them:

1. LeafWiki — best modern team experience if SQLite for metadata is acceptable.
2. Gollum — best if Git itself should be the entire persistence layer.
3. WikiDocs — best if you want a straightforward flat-file wiki with essentially zero database dependency.
4. wikmd — good lightweight option; it is explicitly file-based and supports Git/version control.
5. Wiki.js — excellent team UI, but I'd choose it only if you're comfortable with a more substantial application stack.

If you tell me whether you need SSO, permissions, simultaneous editing, Git sync, search, and Docker, I can narrow this down to the best 1–2 choices for your team.

leafwiki.com is particularly close to what you're describing. Its pages are stored as ordinary .md files on disk, so the actual knowledge base isn't trapped inside a proprietary database. It provides a structured wiki UI, navigation, editing, permissions, and other team-oriented features.

One important nuance: LeafWiki uses SQLite for application state, but the page content itself is Markdown on disk. If by "does not use a database" you mean absolutely zero database of any kind, then I'd choose Gollum or WikiDocs instead.

If you want absolutely no database

Gollum is probably the cleanest architecture: the wiki is simply a Git repository containing human-editable text/Markdown files. It has a web interface, page history, revisions, Mermaid/PlantUML support, and can be edited directly with normal Git tooling.

WikiDocs is another strong fit: it explicitly describes itself as a "databaseless markdown flat-file wiki," with plain-text Markdown files, revisions, namespaces, attachments, and self-hosted Docker support.

So I'd rank them:

If your priority is a collaborative team wiki where everything lives as portable, human-readable .md files on disk—with zero reliance on MySQL, Postgres, or proprietary block formats—you have some great lightweight and modern open-source options.

Here are the best team-ready tools that run strictly on flat markdown files:

1. • The Vibe: A clean, privacy-focused, databaseless flat-file wiki.
   • How it works: It reads and writes straight to Markdown files with YAML frontmatter. It doesn’t use a database, supports namespaces for categorization, includes media/image pasting, dark mode, and can be easily spun up via Docker or run locally.
   • Best for: Teams that want a traditional wiki UI in the browser without managing a database backend.
2. • The Vibe: A modern, feature-rich, databaseless wiki built in Go.
   • How it works: Stores all content and attachments directly as plain Markdown files and assets in a local directory structure. It includes a hierarchical page tree, user management, full-text search, and comments while keeping backups as simple as copying a folder.
   • Best for: Teams looking for a fast, single-binary application that keeps files fully transparent on the file system.
3. Gollum (Git-backed Wiki)
   • The Vibe: The official wiki engine behind GitHub.
   • How it works: Gollum is a ruby-based web frontend that treats a Git repository as its database. Every edit you make via the web UI or via git push directly commits a raw Markdown file into the underlying repo.
   • Best for: Technical teams who already live in Git workflows and want a web interface wrapper over a raw Git/Markdown repository.
4. Obsidian + Git / VS Code + Foam (The Decentralized Approach)
   • The Vibe: No server application at all, just shared local files.
   • How it works: If your team is small and technical enough, you can store a shared folder of Markdown files in a private Git repository (or synced via secure self-hosted storage) and have team members use Obsidian or VS Code with the Foam extension.
   • Best for: Maximum ownership, zero server maintenance, and elite offline markdown editing.

If you want to narrow this down, let me know:

• Do you need a web interface for non-technical team members , or is a Git/file-sync workflow okay?
• Do you prefer a Docker container to host on a private server?

If you want a team wiki where Markdown files are the source of truth and there is no proprietary database, look for a “file-based” or “Git-backed” wiki. Good options:

My shortlist

Best for a software/engineering team: Gollum

Gollum is probably the most proven pattern: pages live as files in a Git repository, so you get branches, pull requests, history, and normal Git backups.

Typical setup:

team-wiki/
├── Engineering/
│   ├── architecture.md
│   └── deployment.md
├── Operations/
│   └── runbooks.md
└── People/
    └── onboarding.md

Benefits:

• Git history and review workflow
• No vendor lock-in
• Edit with VS Code, Vim, etc.
• Easy export: clone the repo

Best simple self-hosted option: wikmd

wikmd is explicitly file-based: it stores content as Markdown files rather than in a database and adds wiki features like search, graphs, and Git support.

Good if you want:

• A browser editor
• Markdown files you can copy/backup directly
• Minimal infrastructure

Best “modern team wiki” feel: KiwiFS

KiwiFS is designed around Markdown files as the canonical data source, with search/indexing layered on top.

Good if you want:

• A web UI
• Search
• Wiki links/backlinks
• Automation or AI tooling around your docs

Things I would avoid for your requirement

Tools like Notion, Confluence Cloud, and many wiki SaaS products store your content in application databases. They may export Markdown, but Markdown is not the primary storage format, which makes migrations harder.

For a team of developers, ops, or technical writers, I would usually choose:

1. Git repository + Gollum for maximum durability and review workflows.
2. wikmd for a simpler “drop in a server and go” wiki.
3. KiwiFS if you want a newer Markdown-native knowledge system.

A good architecture is often:

Git repository
      |
   Markdown files
      |
 Wiki web UI
      |
 Search index (rebuildable)

The key property is that if the wiki software disappears, your knowledge is still just a folder of .md files.

If your team wants a knowledge base where content remains completely portable as plain .md files on a disk—free from the lock-in of a proprietary or external SQL database—several open-source, flat-file wiki engines fit the bill.

Top options designed specifically around a flat-file/Markdown storage model range from Git-integrated servers to minimal web apps:

• Otter Wiki
  • How it works: A lightweight, self-hosted wiki that stores all pages as Markdown files directly inside a Git repository.
  • Storage: Pure flat-file backed by Git history. Every edit is a real commit.
  • Team fit: Excellent for teams wanting simple access control, a clean modern look , and complete ownership of a standard Git repo that can be cloned locally.
• • How it works: A mature, Git-powered wiki created and used heavily by GitHub. It provides a local/self-hosted web frontend to view, edit, and sync your markup pages.
  • Storage: A standard Git repository containing human-editable text and Markdown files.
  • Team fit: Ideal if your team is already comfortable with Git workflows, pull requests, or pushing/pulling documentation via terminal alongside the web interface.
• • How it works: A modern file-based wiki built for simplicity that translates Markdown files on the fly for browser viewing.
  • Storage: Flat Markdown files stored straight in local directories with built-in optional Git version control and a knowledge graph.
  • Team fit: Great for small-to-medium teams looking for a zero-database , Docker-friendly setup that keeps files totally readable from a standard text editor or terminal.
• • How it works: The veteran open-source champion of flat-file wikis . While it traditionally uses its own syntax, it fully supports Markdown via plugins.
  • Storage: Plain text flat-files organized in native folder hierarchies.
  • Team fit: Battle-tested over two decades , incredibly reliable , requires minimal server resources , and has massive plugin support for access control lists (ACL) without needing SQL.
• • How it works: A self-hosted, database-less web app geared towards a minimalist note-taking and wiki experience.
  • Storage: A flat folder of .md files . It only builds a lightweight, on-the-fly cache/search index, meaning you can manipulate files externally in real-time even while the app is running.
  • Team fit: Perfect for smaller teams or groups wanting a fast, modern UI with multi-user authentication options over a shared folder of raw Markdown.

To help narrow down the best fit, let me know:

• Do you want built-in Git integration (so edits automatically commit to a repo)?
• Do you need granular user permissions/login controls , or is an internal local network deployment sufficient?

Yes. If Markdown files are the source of truth and you specifically want to avoid a proprietary database, I’d shortlist these:

My pick: LeafWiki

For your exact requirement, LeafWiki looks like the closest match. It is a self-hosted wiki using Markdown files on disk, with no external database server, and it explicitly positions itself for internal team documentation. It runs as a single Go binary and can be backed up simply by copying the data directory.

One caveat: LeafWiki uses SQLite for application state, so if by “does not use a proprietary database” you mean absolutely no database whatsoever, distinguish that from “content must not be trapped in a proprietary database.” Its page content is Markdown files, while SQLite is used for application state.

If you mean literally zero database, I'd look first at Gollum or Wiki|Docs. Gollum is particularly clean architecturally: the wiki is simply a Git repository containing human-editable text/markup files, with Git providing history and versioning.

Bottom line:

• 🥇 Best modern team wiki: LeafWiki
• 🥇 Best pure Git/Markdown approach: Gollum
• 🥇 Best feature-rich flat-file option: Wiki|Docs
• 🤖 Best if AI agents matter: KiwiFS

If you tell me team size + whether you want self-hosted or SaaS, I can narrow this to the best 2–3 options and compare authentication, permissions, search, Git sync, and collaboration.

For teams that want absolute ownership of their data without being locked into a proprietary database (like MySQL, Postgres, or proprietary cloud blocks), flat-file and Git-backed wikis are the ideal choice. They store clean, portable .md files directly on the disk or in a repository.

Here are the best options available for a team markdown wiki with no proprietary database:

• Otter Wiki : A minimal, elegant self-hosted wiki where every page is stored as a flat .md file backed internally by a Git repository. It includes user authentication, renders clean layouts, and requires zero database overhead—just a single container with a mounted data volume.
• DokuWiki : The classic flat-file open-source champion written in PHP. It requires no database and stores everything in plain text/markdown-compatible files on the server. While its default look is traditional, it has a massive plugin ecosystem and bulletproof reliability.
• Gollum : A fully Git-powered wiki that provides a web front-end while committing every edit directly to a local Git repository. You can edit pages via the web UI or write files locally on your machine and run a normal git push.
• Flatnotes : A straightforward, database-less web application designed to interact with a folder of flat markdown files. It features instantaneous search, a clean interface, and multi-user authentication support.
• Docs-as-Code (MkDocs / Hugo + Git) : If your team is comfortable with a slightly more technical workflow, using a static site generator like MkDocs pointing at a shared GitHub or GitLab repository gives you a gorgeous, searchable documentation site compiled straight from raw markdown files via CI/CD.

If you can tell me:

• Whether you prefer a web-based GUI editing interface for non-technical teammates or a pure Git push workflow
• If you want to deploy via Docker on a private server or use a hosted service

I can narrow down the exact tool and give you a sample configuration to get started.

If you want a team wiki where the source of truth is Markdown files (not a proprietary database), look for a file-based or Git-backed wiki. Good options:

My shortlist:

1. For a software/engineering team:
   Gollum — the wiki is literally a Git repo, so pull requests, history, branches, and backups work naturally.

2. For a company knowledge base with non-technical users:
   LeafWiki or WikiDocs — they provide browser editing while keeping Markdown as the underlying content.

3. For maximum portability and minimum lock-in:
   A plain Git repository of Markdown files plus a renderer such as Gollum. Your data remains usable with any Markdown editor even if you replace the wiki software.

A setup I’d recommend for many teams:

team-wiki/
├── README.md
├── Engineering/
│   ├── Architecture.md
│   └── Runbooks.md
├── Product/
│   ├── Roadmap.md
│   └── Decisions.md
└── Operations/
    └── OnCall.md

Store it in Git, review changes through pull requests, and deploy a wiki frontend on top. This avoids the common failure mode where your knowledge becomes trapped in a SaaS export format.

If you need real-time collaborative editing like Notion/Confluence while still keeping Markdown files as the canonical format, the options narrow considerably; most collaborative wikis use a database for live editing state.

Logseq, Obsidian (with Git), and DokuWiki are top choices for a team wiki that stores data purely as Markdown files without a proprietary database. Because these tools utilize standard file structures, you retain full ownership of your data, avoid vendor lock-in, and can easily edit files using any text editor.

Best Markdown-Based Team Wikis

• Obsidian : Stores everything in a local folder of Markdown files ("Vault"). Teams typically sync this folder using Git (via the Obsidian Git plugin) or a shared cloud drive, allowing simultaneous collaboration without a central database.
• Logseq : A privacy-first, open-source knowledge base that reads and writes directly to local Markdown files. It features a graph-based structure and outliner format, making it excellent for tracking interconnected team tasks and meeting notes via Git syncing.
• DokuWiki : A lightweight, open-source wiki engine that requires no database, storing all data in plain text files (though it uses its own lightweight syntax, plugins can enable full Markdown support). It is ideal for teams wanting a traditional self-hosted web wiki without database upkeep.
• Foam : An open-source personal and team knowledge management tool built directly inside Visual Studio Code. It utilizes standard Markdown files and integrates seamlessly with GitHub, making it a perfect wiki solution for software development teams.
• Dendron : A developer-focused, scalable team wiki built as an extension for VS Code. It uses a hierarchical Markdown structure and backs up directly to a Git repository, ensuring no proprietary formatting or databases are ever used.

If you would like to narrow this down, let me know:

• What hosting preference do you have? (Self-hosted web server, local files synced via Git, or cloud-managed?)
• What is the technical skill level of your team? (Are they comfortable with VS Code/Git, or do they need a simple visual editor?)
• Do you require real-time concurrent editing , like Google Docs?

I can recommend the absolute best fit based on your setup.

Yes. If your requirements are team wiki + Markdown files + no proprietary database, there are several good fits.

My top picks

1. LeafWiki — my first choice.
It is specifically designed as a self-hosted wiki with Markdown files on disk, a single Go binary, and no external database server. It supports authentication and web-based editing, while the underlying content remains ordinary Markdown files.

2. Gollum — if Git is the source of truth.
Gollum is essentially a web UI over a Git repository: pages are editable text/Markdown files, directories organize them, and Git provides history and rollback.

3. MkDocs — if this is primarily engineering documentation.
Your repository contains ordinary Markdown under docs/, with an mkdocs.yml configuration file. It generates a polished documentation site without needing a database.

The tradeoff is that MkDocs is more of a docs publishing system than a collaborative wiki: you'd generally have people edit Markdown through Git rather than giving everyone a browser-based editor.

What I'd choose

If you want something resembling Notion/Confluence from the team's perspective, but want the underlying data to be:

wiki/
├── Engineering/
│   ├── deployment.md
│   ├── architecture.md
│   └── troubleshooting.md
├── Operations/
│   ├── on-call.md
│   └── runbooks.md
└── People/
    └── onboarding.md

I'd start with LeafWiki.

If your team is comfortable with Git and you care more about maximum portability and simplicity than browser editing, I'd choose Gollum or MkDocs.

One particularly attractive property here is that your knowledge isn't trapped in the application: the Markdown files remain readable and editable with any text editor, and Git can provide the canonical history. That's a substantially better fit for avoiding vendor lock-in than a conventional database-backed wiki.

If you tell me how many people will use it and whether you need SSO, permissions, full-text search, attachments, and browser editing, I can narrow this to the best 2–3 choices.