A visual editor for the docs in your repo.

Docusaurus and Fumadocs have dedicated support: their callouts, tabs and other components are edited as visual blocks and written back the way each framework expects. Any other site that keeps its content in Markdown or MDX files, such as Next.js, Astro or TanStack Start, works too. There, standard Markdown is edited visually, and callouts and captioned images are written as Prose UI components. See all platforms.

Yes. Import your GitHub repo and start editing pages right away, with no setup and no changes to your project structure. One feature takes a one-time setup: to edit the sidebar visually, you add a short adapter that builds your site sidebar from the navigation.json file Dhub saves. The docs have adapters for Docusaurus and Fumadocs. Read about navigation.

No. Once you connect a repo, anyone on your Dhub team can edit and push changes without a GitHub account, and their name still shows up in the commit history. If you choose to use pull requests, someone with GitHub access will need to merge them.

Yes, and some teams use Dhub for exactly that. When an agent pushes a branch or opens a pull request, open it in Dhub and every change is highlighted on the page, so a person can read the changed page instead of working through a Markdown diff. Fix anything in place and push to the same pull request. Branches, pull requests and review are part of the Pro plan.

Most Git-based CMSs are built around forms: you describe your content in a schema, then fill in fields. Dhub is built for documentation. It opens your Markdown and MDX pages as documents with no schema to write, edits callouts, tabs and tables in place, lets you rearrange the sidebar visually, and shows the changes in a pull request highlighted on the page. We ran Dhub, CloudCannon, TinaCMS, Decap CMS and GitCMS against the same Docusaurus repo. Read the full comparison.

No, Dhub is a closed-source cloud service. Your content stays in your repository as plain Markdown and MDX files, so you can stop using Dhub at any time and keep it all. It is the same ownership model as Obsidian: the app is proprietary, your files are yours.

Teams whose documentation is Markdown or MDX files in a GitHub repository: product docs, a help center, a knowledge base. Developers keep the repo, the build and the review process they already have. Writers, support and product people get a visual editor in the browser, so a docs change no longer has to wait for someone who knows Markdown and Git.

No. Pages open as formatted text, the way they would in Google Docs or Notion, and sending a change to GitHub is one button. Connecting the repository the first time takes someone with access to it on GitHub. After that, anyone you invite can edit.

Through a GitHub app that you install on your account or organization. During installation you choose exactly which repositories Dhub can access. It needs permission to read and write their contents and to open pull requests. Every push and pull request Dhub makes is an ordinary commit in your history.

Components Dhub does not recognize are displayed as embedded MDX blocks. You can edit the JSX code directly within these blocks, and the content around them is still edited visually. Frontmatter fields such as title and description are edited in a form.

The Hobby plan is free and covers personal, non-commercial projects with personal GitHub accounts and public repositories, pushing to your default branch. The Pro plan is $49 per month and includes 3 seats, GitHub Organizations, private repositories, branches and pull requests, review, and real-time collaboration. Additional seats are $10 per seat per month. The Business plan is $299 per month with unlimited seats, an onboarding call, priority support, and help with migration and custom MDX components. Pro comes with a 14-day free trial.

Yes. Seats are $10 per seat per month on the Pro plan and can be added at any time from your team settings. Business has unlimited seats.

No. Existing subscriptions keep their current plan and price.