Native OpenAPI, GraphQL & Doxygen documentation
One engine, every API
See it live
Built in-house, not a static-site generator
Prose and reference, together
What if you ship more than one API surface?
One engine, every API Most docs tools handle prose and bolt on a third-party widget for API reference. DSR Docs renders OpenAPI, GraphQL, and Doxygen natively — same engine, same search, same look — so you can document a REST API and a C/C++ SDK together, with your GraphQL API alongside them, in one site instead of three. Format You bring We render --- --- --- OpenAPI 3.x A spec file An interactive, scroll-spy reference one operation per anchor, prose mixed right in GraphQL SDL or an introspection dump Every query, mutation, and type as its own navigable page Doxygen The XML your build already emits C/C++ headers with call and caller graphs Drop in a spec and the reference appears — anchored, searchable, and styled to your brand. No copy-paste, no embed, no separate tool to license. See it live This very site renders all three - OpenAPI — Pets a REST spec as one scroll-spy page, with narrative pages woven in. - GraphQL — Banking schema-derived pages for every operation and type. - Doxygen — cJSON a real ingestion of the open-source cJSON library, graphs and all. Three renderers, one engine, one search box, one bill — the REST spec, the GraphQL schema, and the C/C++ SDK above are all served by the same self-hosted container, not three separately-licensed tools stitched together. Built in-house, not a static-site generator DSR Docs is not a theme layered on top of Docusaurus, MkDocs, or another static-site generator. It's a custom engine — a React and Vite single-page app with an Express backend and its own renderers for each API surface. That's precisely what makes the things above possible native OpenAPI, GraphQL, and Doxygen rendering, a live Try It console, an in-app editor with page history, and full-text search all live in one application rather than being bolted onto a generic SSG. If you've seen "Docusaurus" mentioned around DSR Docs, that's because it's one of the tools teams compare DSR Docs against (see DSR Docs vs Docusaurus) — not what it runs on. Prose and reference, together Every API section mixes hand-written Markdown with generated reference on the same page. Explain the auth flow in prose, then drop straight into the endpoints — readers never bounce between a "guide" site and a "reference" site, because there's only one. What if you ship more than one API surface? When a product exposes a REST control plane, a GraphQL API, and an embedded C/C++ SDK, each renderer attaches to its own domain and they all share the same search, chrome, and branding. See Document OpenAPI, GraphQL & C/C++ SDKs together for how that maps to domains — and the one honest constraint (one schema kind per domain) — when you outgrow a single API surface. [!IMPORTANT] Want this on your own documentation? Write to docs@dsr-corporation.com. Ask about migration, licensing, or anything this page didn't cover.