Use case

Simple private docs for Markdown-first teams

For small engineering teams, startups, and founders who already write in Markdown. OpenDocs isn't trying to replace Notion. It's the missing step between docs/ in the repo and "can someone send me that runbook?"

What this is, what it isn't

What it is: a one-command publishing layer. You have a Markdown file, you want it readable at a URL, you run opendocs publish and you have one. Workspace-only by default, public if you want.

What it isn't: a wiki, a project tracker, a database, a real-time collaborative editor, or any of the other things that come up when teams say "we should set up Notion." If your team needs a knowledge base with linked pages and embedded databases, this isn't that.

It's the simpler thing. For teams that keep their docs in the repo and just need a way to share them.

When this is right for your team

You already write in Markdown. Your README, your ADRs, your runbooks all live as .md files. Switching to Notion would mean copy-pasting hundreds of files.
Your team is small. Five engineers, ten engineers. The cost of running a wiki and maintaining it is more than just sharing files.
You use AI agents. Claude Code, Cursor, Codex. They all output Markdown. OpenDocs lets them publish that output without bouncing through a wiki.
Source-of-truth lives in git. The doc is in the repo. The published version is just a snapshot. Re-publishing keeps the URL stable.

When you should use Notion instead

Honestly, plenty of teams. If you need:

A linked knowledge base with backlinks and embedded queries: Notion or Obsidian Publish.
A wiki that non-technical people will edit directly: Notion or Confluence.
A real-time collaborative editor: Google Docs or Notion.

We're not the right tool for any of those. We're the right tool when your team's docs already live in Markdown and the sharing step is what's broken.

What teams publish

Runbooks. On-call docs, incident response. Workspace-only link.
ADRs. Architecture decision records. Often public so the broader org can read them.
Postmortems. Blameless writeups, workspace-internal so the conversation stays focused.
Onboarding docs. The README a new hire sees on day one.
Specs and PRDs. Drafted in the repo, published for review.

Keep writing in Markdown. We'll handle the URL.

Free plan publishes up to 10 docs. Pro adds unlimited docs and custom branding.