Dhub

Dhub is a visual workspace for Markdown and MDX documentation kept in GitHub. It suits product and documentation teams that need nontechnical contributors to edit alongside repository-based workflows. The main decision is whether its collaborative review features justify moving beyond Hobby’s narrow personal-project boundaries.

Overview

Dhub adds a visual editing layer to Git-based documentation without taking content out of the repository. Contributors can change pages, push updates, open pull requests, and pull current GitHub content from one interface. That is a sensible fit for product docs, help centers, and knowledge bases whose source of truth remains Markdown or MDX.

Real-time editing also broadens participation: colleagues can work together without each person having a GitHub account. The limitation is access policy rather than editing capability. Hobby is restricted to personal, non-commercial use, personal GitHub accounts, public repositories, and pushes to the default branch, so it is not a realistic team workflow for private or commercial documentation.

Key features

Visual authoring and repository sync

The editor renders Markdown and MDX as visual content, reducing the syntax burden for writers and subject-matter experts. GitHub integration preserves repository review: users can push changes, create pull requests, and retrieve the latest version. Pro is the point at which branches, pull requests, private repositories, and GitHub Organizations become part of the supported workflow.

Collaboration and review

Shared, real-time editing is useful when documentation ownership extends beyond engineers. Dhub can also show pull-request changes as page highlights, including changes made by teammates or AI agents, giving reviewers a visual way to inspect proposed edits instead of reading source diffs alone.

Frameworks, media, and navigation

Dhub supports Markdown or MDX projects built with Docusaurus, Next.js, TanStack Start, Astro, Hugo, VitePress, and Fumadocs. Its image tools handle uploads, storage, and file paths inside the editor, removing a common source of broken documentation assets. A visual sidebar editor writes its structure to navigation.json; Docusaurus and Fumadocs require a framework-specific adapter for that feature, an important setup condition for those stacks.

Privacy

Dhub’s privacy policy describes GDPR and applicable Lithuanian and EU data-protection compliance, industry-standard technical and organisational safeguards, and access to repository content and metadata only within the GitHub permissions granted for editing and synchronisation. It says personal data is not sold.

Pricing

Dhub is freemium, with a 14-day trial and paid plans from $16/mo. Hobby costs nothing for one user. It permits personal GitHub accounts, public repositories, editing, and pushes to the default branch, but its personal, non-commercial terms and lack of private-repository or branch workflows make it suitable mainly for an individual project.

Pro costs $41 a month, or billed Billed $588 $490 / year, with three seats included. Additional seats cost $100/seat/year. It adds GitHub Organizations and private repositories, branches and pull requests, visual review, and real-time collaboration, making it the practical plan for a small professional documentation team.

Business costs $249 a month, or billed Billed $3,588 $2,990 / year. It includes unlimited seats, an onboarding call, priority support, migration help, and assistance with custom MDX components. Choose it when adoption, migration, or a large contributor base matters more than minimizing subscription cost.

Platforms

Dhub is web-based and vendor-hosted. Its integration is specifically with GitHub, while the content can target the supported Markdown and MDX frameworks.

Who it's for

Dhub is best for teams maintaining documentation in GitHub repositories that want writers, support staff, or other contributors to work visually. Hobby is appropriate for a personal, public, non-commercial repository, not as a representative trial of a team’s intended workflow.

Pros and cons

Pros: visual Markdown and MDX editing lowers the syntax barrier; real-time collaboration does not require every editor to hold a GitHub account; pull-request highlights make review more legible; image handling and visual navigation reduce file-management work.

Cons: Hobby excludes private repositories, GitHub Organizations, branches, and commercial use; Docusaurus and Fumadocs need an adapter for visual sidebar editing; Pro’s additional-seat charge can materially raise the annual cost.

Alternatives

For a wider comparison, see the Git-Based CMS list. Choose Kiln instead when self-hosting, API access, or an AGPL-3.0 open-source worker matters. Decap CMS is the better fit for a self-hosted web CMS with a free one-site, one-seat plan. Pick Siteleaf when a hosted API-oriented workflow and a 100 MB/100-page developer tier are enough. Mattrbld suits projects wanting Android, iOS, web, or self-hosted access. Outstatic is worth choosing for a self-hosted GitHub CMS with unlimited repositories on its free tier. Quiqr is the open-source, free-forever option with desktop platforms. deco CMS is preferable when an open-source, self-hostable core is the priority. Choose Netlify when the central requirement is hosted deployment rather than Dhub’s documentation editing and review workflow.

Verdict

Choose Dhub if your team keeps technical documentation in GitHub and needs a visual, collaborative authoring and review layer for Markdown or MDX. Its strongest reason to buy is bringing non-GitHub contributors into a repository-aware workflow without abandoning pull requests. Look elsewhere if you need a genuinely team-capable free tier, self-hosting, or a workflow not constrained by GitHub and framework adapter requirements.