Skip to content
docbin logo

docbin

Stores markdown docs behind shareable URLs, keeping every edit as an immutable version, with a REST API and CLI upload.

At a glanceswept 2026-10-12

not read yet

Use

For
Developers and teams who share markdown docs and build logs as links, via API, CLI, or MCP.
Price
Free plan · From $4/mopricing page, read 2026-10-14 ↗
Activity
Actively maintainedsite updated 12 days ago
Company
Domain since 2026domain registered
Runs as
CLIAPI
What people do with itread off docbin.app on 2026-10-14
  • Share a markdown doc as a link
  • Push build logs from the command line
  • Publish versioned docs through the REST API
The companyeach fact with its source · read 2026-10-14
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-14

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Knowledgeby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Knowledge tools →

Questions this page answers
  • What is docbin?

    Stores markdown docs behind shareable URLs, keeping every edit as an immutable version, with a REST API and CLI upload. It is listed in the Atlas under Knowledge.

  • Who is docbin for?

    Developers and teams who share markdown docs and build logs as links, via API, CLI, or MCP.

  • How much does docbin cost?

    docbin has a free plan; paid plans start at $4/mo, per its pricing page on 2026-10-14.

  • Is docbin free?

    Yes, docbin has a free plan, per its pricing page on 2026-10-14.

  • Do people use docbin?

    Little sign of use.

  • Is docbin still maintained?

    Actively maintained: site updated 12 days ago.

  • What are alternatives to docbin?

    In Knowledge, by use: makesPDF, Repage, Physea Labs, Metapad, memsprout, Handover.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.