docu.so
A publishing platform that turns Markdown into branded documents and web pages. People and AI agents can create, style and publish through the editor, API or MCP.
Overview
An AI agent can draft a proposal, report or set of instructions, but the result still needs formatting and somewhere to live. That often means copying the content into another tool, applying the brand and arranging a way to share it.
We built docu.so to handle that last step. Markdown becomes a finished, branded page at a shareable link. The same publishing engine serves a browser editor, a REST API and MCP tools, so a person or an agent can take the work from draft to published page.
Inside the build
More than a text document
A rendering engine turns Markdown into proposals, reports, landing pages and video watch pages. Reusable blocks add columns, callouts, cards, pricing sections and calls to action without requiring the author to write HTML or CSS.
A brand that carries through
Brand Book stores logos, colours, typography and layout preferences. Templates provide the structure and the brand supplies the styling, giving different outputs a consistent appearance.
Built for people and agents
People can write and preview in the editor. Agents can create, update and publish through the API or MCP, using the same templates and brand profiles. The user’s own AI does the writing; docu.so handles the finished output.
Publishing and controlled sharing
Published pages have a short link that can be shared and updated. Private sharing supports passcodes, expiry dates and limits on opens, giving authors options for time-sensitive or restricted material.
Implementation details
One source, one rendering engine
Markdown remains the source of truth. The same engine renders the editor preview and the published page, with reusable block and template definitions. New output types can build on that foundation instead of requiring a separate application.
A shared API underneath
The React editor, REST endpoints and MCP tools use shared application services. A Hono API handles publishing and access, backed by Supabase. Markdown and styling pass through a sanitisation layer before they become a page.
From a draft to a page people can use
An agent can read the available templates and block syntax, prepare the Markdown and create a document with a chosen brand profile. The author can then review the same content in the browser editor, adjust the structure and publish it. Both routes use the same rendering engine, so the preview and the shared page follow the same rules.
Content, structure and styling each have a clear role. Markdown holds the words, blocks provide elements such as a pricing section or a two-column layout, and the brand profile supplies the visual choices. This lets a proposal and a report look like they belong to the same business without asking the model to design a new page from scratch.
The document stays editable after publication. A correction or a new section can be made against the existing source and shared at the same link. Agents can also update sharing settings or unpublish through the API, making publishing part of a wider workflow rather than a separate manual step at the end.