docbin vs rentry
rentry has run since 2017 as a free markdown pastebin with edit codes instead of accounts. docbin does a narrower job with an open api and a version on every edit. here is the whole comparison, including where rentry is the better pick.
the numbers
| feature | docbin | rentry |
|---|---|---|
| max text size | 5 MB25 MB pro | 200,000 characters |
| account required | never | never |
| shared editing | owner account only | edit code, share with anyone |
| write rate | 15/min75/min pro | not published |
| versions | every edit | not published |
| markdown | renders as the page | renders, plus tables, admonitions and a toc |
| price | free$4/mo pro | free, no tiers |
rentrys numbers come from its own what page. its api docs page 404s, so an api key requirement and a rate limit arent published anywhere we could find.
where docbin wins
- a version for every edit
- rentry doesnt publish any version or history feature - edits look like they just overwrite the page. docbin keeps every edit as its own immutable version.
- multi-file docs
- up to 20 files (50 pro) share a single docbin link. rentrys text field holds one page.
- a byte ceiling, not a character cap
- 5 MB (25 MB pro) of anything, not 200,000 characters of text only.
- open scraping api, no key needed
- GET /api/docs/public just works. rentrys own docs dont publish an api key requirement or a rate limit anywhere.
where rentry wins
- a page you name and keep
- pick your own rentry.co/slug and it stays up forever, no account. a docbin anonymous paste gets a generated name and expires after a year.
- edit codes for shared ownership
- hand the code to a few people and they all edit one entry, no shared account required. docbin has no edit-code model at all - editing means being logged into the owning account.
- free forever, no tiers
- one plan, no price to unlock more room. rentry says it plainly: "we don't and won't bug you for payment... ever!"
so which one
use rentry when a few people need to co-own one page and none of you want to make an account. an edit code passed around a group chat does the whole job.
use docbin when the content needs a version history, more than one file, or a size limit that isnt measured in characters. push it from a script and skip the account for the paste itself.
paste a documentor from your shell:
npx docbin push ./file.md