VoidPaste vs Hastebin / haste-server
Haste is minimal paste UX; public hastebin.com has been unreliable. VoidPaste is a maintained hosted product with explicit privacy controls.
This comparison sticks to documented, shipped VoidPaste behavior — no fake migration stats or features we do not run.
Create a VoidPaste · All alternatives · github.com/seejohnrun/haste-server
Side-by-side
| VoidPaste | Hastebin | |
|---|---|---|
| Primary job | Hosted ephemeral paste with privacy modes and API/CLI | Minimal paste UX; open-source haste-server for self-hosting |
| Account | Optional accounts for private history and keys | Typically none in the classic design |
| Privacy | Public / unlisted / private / password / optional client encryption | Mostly URL secrecy — little access-control or client encryption classically |
| Expiration / burn | Rich TTL, max views, burn-after-reading | Often short-lived or instance-configured only |
| API / CLI | REST + Go CLI — Documented REST + Go CLI | Simple HTTP POST create; forks and wrappers vary by instance |
| Cost / limits | Free hosted SaaS | Self-host free; public instances depend on whoever runs them |
Choose VoidPaste when
- You need a stable production origin (voidpaste.com) with documented burn and privacy modes.
- You want private pastes, passwords, or optional client encryption without operating a server.
- You want scoped API keys for automation.
Choose Hastebin when
- You want the smallest self-hosted paste daemon and will operate it yourself.
- URL secrecy alone is enough for your threat model.
- You already run haste-server behind your own reverse proxy.
Public Hastebin availability
Public hastebin.com has had ownership and availability churn. Treat random public Haste instances as untrusted for production secrets. Self-host haste-server if you want that UX under your control; otherwise prefer a maintained hosted product with explicit expiry and burn.
Try it
Create a paste · Security model · Private & encrypted pastes