Docsheaf
Integrations Partly available

Connect Docsheaf to the rest of your stack

A REST API for everything in the app, embeds for the tools your team already uses, and open formats in and out. A runtime for custom integrations is on the roadmap.

Available today: the REST API with personal tokens, embeds from YouTube, Vimeo, Loom, Figma and CodeSandbox, Markdown import and export, Git Sync with GitHub, llms.txt, S3 or Cloudflare R2 storage and SMTP email. Coming soon: an integrations runtime for custom blocks and extensions, and Git Sync with GitLab.

Runs on infrastructure you choose

Docsheaf stores data in services you already trust, configured with environment variables — no code changes.

PostgreSQL

All content, revisions and settings live in Postgres. Migrations run automatically on start-up.

AWS S3 or Cloudflare R2

Uploads go to an S3-compatible bucket in production, or to local disk on a single server.

Any SMTP provider

Sign-up codes, password resets and security alerts are delivered through the SMTP service you configure.

Frequently asked questions

What can I connect Docsheaf to today?

Anything that can call a REST API with a token. Inside pages you can embed YouTube, Vimeo, Loom, Figma and CodeSandbox, and every site exposes Markdown and llms.txt for other tools to read.

Can I build my own integration?

Yes, on the REST API: create pages, import Markdown, open change requests, publish sites and read Insights from scripts or CI. A runtime for integrations that run inside Docsheaf is on the roadmap.

Which embed providers are supported?

YouTube, Vimeo, Loom, Figma and CodeSandbox render inline. Any other http(s) link is shown as a link card.

Do I need S3 or R2?

Not for a single server — uploads can be stored on local disk. For production, configure an AWS S3 or Cloudflare R2 bucket.

Accurate docs. Better answers.

Start writing for free, or talk to us about bringing your team and your existing docs.