PrivateBin Hosting

How PrivateBin works

PrivateBin encrypts paste content in the browser before it is uploaded, and decryption also happens in the recipient’s browser. The project describes the server as having zero knowledge of the stored paste data. A complete share URL carries the information needed by the browser to retrieve and decrypt the ciphertext, so losing or truncating the link can make the paste unrecoverable.

Depending on instance configuration, creators can select expiration, burn-after-reading, password protection, syntax highlighting, Markdown, discussions, file attachments, previews, themes, and QR codes. Optional features may be enabled or disabled by the container configuration. Recipients who obtain the complete link and any required password can access the content while the paste remains live.

Key PrivateBin features

PrivateBin reduces the amount of plaintext visible to the server by performing encryption in the client. This makes it different from a conventional paste site, but security still depends on the browser, delivered JavaScript, the complete share URL, password handling, recipient devices, and whether the content is copied after decryption.

The service does not create recipient identities, revoke copied material, scan attachments, moderate content, certify deletion, or replace a password manager. Public availability also creates abuse and storage concerns. Use short expiry where appropriate and share the decryption link through an authorised channel.

PrivateBin vs Pastebin

PrivateBin stores encrypted paste data that the browser decrypts for a recipient with the complete link. Pastebin is a provider-operated website for storing readable text online for a selected period, with public, unlisted, private, account, syntax, and API workflows controlled by the service operator.

Pastebin may suit users who need a familiar maintained text-sharing site and do not require a self-hosted zero-knowledge design. PrivateBin is more suitable when browser-side encryption and infrastructure control are priorities, while accepting responsibility for configuration, capacity, abuse handling, and secure link delivery.

Who uses PrivateBin

Developers share temporary snippets or logs, support teams send short-lived diagnostic material, and privacy-conscious users exchange encrypted notes or files. Burn-after-reading can reduce the live window for content intended for one retrieval, while password protection adds a separate secret.

PrivateBin is not a durable archive, identity-verification service, malware scanner, digital-signature platform, or substitute for rotating credentials. A recipient can copy decrypted content, and anyone with the complete link and required password can read it before expiration.

Self-hosting PrivateBin: requirements and cost

PrivateBin is storage-driven because live encrypted pastes and optional file attachments occupy the plan volume. Capacity also depends on paste size, expiry settings, burn mode, discussions, previews, attachments, download traffic, and concurrent visitors. PostgreSQL and MariaDB are Not required; the container uses its own persisted data path. PrivateBin is marked storage-driven in the plan mapping, so 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 provides more room for a large working set.

On AvaHost, PrivateBin uses Plan 1 at €2. The hosted PrivateBin package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Recipient verification, malware scanning, moderation, delivery certification, deletion certification, and permanent archival storage are not included. Protect complete share URLs, use separate passwords where appropriate, restrict public use, and keep authorised originals outside the paste service.