Every engineering team has a graveyard somewhere. Old MkDocs pages nobody touches. A Docusaurus site frozen in 2022. A GitBook instance three platform migrations behind. Moving that content manually is the kind of work that gets assigned on a Friday and silently abandoned by Monday. Nobody wants to do it, and honestly, nobody should have to.
DocPatch is a lightweight API that automates the conversion of Markdown documentation between frameworks. Point it at your source content (Docusaurus, MkDocs, GitBook, Jekyll, Sphinx), tell it your target framework, and it handles everything: formatting, links, metadata preservation.
Single documents convert in seconds. Hundreds convert via a simple loop script. No manual intervention. No lost links. No stripped metadata.
It launched this week on Product Hunt under Oculix, an infrastructure-focused software company founded by an engineer with 25+ years of performance and infrastructure experience and three Google Cloud Professional certifications. The product is solid at its core—the edges are still being refined, but the core idea is sharp and the execution is clean.
Documentation consolidation is becoming a common challenge as teams migrate frameworks and platforms. DocPatch automates what most teams do manually (and expensively). For teams sitting on a documentation backlog, it can save a week or more of engineering time. That’s engineering cycles freed up for actual feature work instead of documentation drudgery.
Ready to try it? DocPatch is free to get started, or you can check it out on Product Hunt. For engineering teams with documentation backlogs, it’s worth 15 minutes to see if it solves your conversion headache.
Key Features of DocPatch
Markdown-to-Framework Conversion
The core function is converting Markdown files into the format expected by a target documentation framework. You pass in raw Markdown content, specify a target like docusaurus or gitbook, and get back a properly formatted document with the right frontmatter, heading structure, and metadata. Currently supported targets include Docusaurus, MkDocs, and GitBook, with Sphinx in the mix too. Direct source conversion from Confluence, Notion, or HTML is listed on the roadmap but not live yet.
Metadata and Link Preservation
This is where most manual migrations fall apart. Links rot. Frontmatter gets stripped. Titles disappear. DocPatch preserves all of it during the transformation. The converted output keeps internal links intact, retains metadata fields, and maintains formatting structure so the migrated docs don’t need a cleanup pass after conversion.
Synchronous API with No Polling
The API is synchronous, which is a deliberate and welcome choice. You send a POST request and get the converted document back in the same response. No job IDs to track, no webhooks to configure, no polling loop to write. For teams integrating this into a CI pipeline or a migration script, that simplicity matters a lot.
Batch Processing via Script
Individual conversions are fast, but the real productivity gain comes from batch workflows. Oculix’s own documentation describes a tested pattern: export your docs as Markdown, loop through the files with a short Python or Bash script, call the DocPatch API on each one, and save the output directly into your target framework. Fifty documents can realistically be converted in under an hour using this approach, depending on your plan’s conversion limits.
How Marcus Migrated 80 Docs on a Tuesday Morning
Marcus, a backend engineer at a small SaaS startup, had been putting off a docs migration for three months. His team had been using MkDocs for their internal developer documentation, but the whole organization was moving to Docusaurus as part of a broader developer experience push. The migration had 83 Markdown files, assorted frontmatter inconsistencies, and a deadline of end of week.
At 9:15 AM on a Tuesday, Marcus signed up for DocPatch, copied his API key from the dashboard, and spent about 20 minutes writing a Python script that iterated over his docs folder and fired a POST request for each file. By 10:40 AM, all 83 documents had been converted and saved to a new directory with Docusaurus-compatible frontmatter and intact internal links. He spent the rest of the morning doing a spot-check pass on about a dozen files and found only two minor formatting issues that needed manual edits.
The whole thing took under two hours. His original estimate, doing it manually, had been three to four days. His team pushed the new Docusaurus site to staging before lunch.
How DocPatch Processes a Document
Step 1: Sign Up and Get Your API Key
Free signup takes about 30 seconds at the DocPatch site. No credit card required. Your API key appears on the dashboard after email verification. Copy it immediately; the current dashboard doesn’t let you retrieve it later without contacting support.
Step 2: Send Your Markdown via POST Request
Make a POST request to https://api.docpatch.dev/v1/docpatch/migrate with your API key in the x-api-key header. The request body takes two fields: markdownContent (your raw Markdown string) and targetFramework (your destination platform).
Step 3: Receive the Converted Document
The response returns immediately with a status field and a migratedDocument field containing your converted content. Write it to a file, check it, and import it into your target platform. That’s the full loop.
DocPatch Pricing Tiers
DocPatch runs on a conversion-count model, where each API call processes one document:
- Free: 100 conversions per month, no credit card needed
- Developer: $39 per month, 500 conversions, priority support, batch API access
- Team: $149 per month, 5,000 conversions, Slack support, scheduled API, and team collaboration features
For a one-time migration project, the free tier is worth trying first. Most small-to-medium doc sets will fit within the 100-conversion limit or require just one month at the Developer tier.
Worth Trying If You Have a Docs Backlog
DocPatch is not a finished product in the polished sense. A few features are still listed as coming soon, and the dashboard is minimal. But the core API works, the pricing is fair, and the problem it solves is real. If your team has been sitting on a documentation migration because nobody wants to do it by hand, this is a practical way to knock it out in a morning. Start with the free tier at DocPatch and see how far 100 conversions gets you.
