What it does
OpenDocs is a documentation publishing platform with a named internal-wiki workflow. The vendor describes restricted or public spaces, a visual block editor, built-in search, page feedback for outdated material, clear space ownership, and two-way GitHub sync for engineering pages. Its docs are accessible to human readers and, through MCP, connected assistants within the granted scope.
Treat internal knowledge as published documentation
OpenDocs approaches the company wiki as a documentation site rather than a general workspace. Teams can separate knowledge into spaces, restrict access to internal pages, assign an owner, and use built-in search. Readers can flag a page as stale with feedback; engineering teams can keep selected pages synced with a GitHub repository so docs changes can be reviewed with related code changes.
The vendor also describes making the wiki queryable through MCP and publishing other kinds of customer documentation from the same account. The internal-wiki page explicitly says the product is publishing-first, not an all-in-one workspace with tasks, databases, or whiteboards. This makes it a narrower fit for organizations that need documents and search, rather than an app for every team activity. No space, access rule, or sync was configured.
Strengths
- Restricted spaces and named ownership support an internal knowledge base with audience boundaries.
- The vendor describes in-place stale-page feedback and optional GitHub sync for engineering documentation.
Watch out for
- OpenDocs is intentionally a documentation-publishing product, not a general-purpose workspace with project databases or whiteboards.
Best for
- Teams publishing an internal handbook or runbook with controlled access and clear page ownership