MicroBin Hosting

How MicroBin works

MicroBin creates a shareable upload from text, code, a file, or a destination URL. The creator can select an expiry period, a burn-after access limit, visibility options, syntax highlighting, and other supported controls. Generated links and QR codes make the upload available to recipients until the configured lifecycle condition removes it.

The application also includes an administrator interface when administrator credentials are configured. In the hosted template, a generated administrator password protects that interface, and the catalogue note states that the administrator can see and delete every paste. That means MicroBin should not be described as a zero-knowledge service merely because an individual upload uses a password or encryption option.

Key MicroBin features

MicroBin combines paste sharing, file uploads, URL shortening, syntax display, expiration, burn limits, and QR codes in one small service. This makes it useful for temporary troubleshooting material or files that are inconvenient to place in a chat message, while keeping the storage location under the operator’s control.

Public upload services require moderation and capacity controls. File type, size, retention, download traffic, and anonymous use can consume storage or create abuse risk. The hosting service does not provide malware scanning, recipient verification, content review, legal retention, or a guarantee that an expired link removes copies already downloaded by recipients.

MicroBin vs Pastebin

MicroBin runs the paste and file service on the hosted installation, with administrator control over configuration and stored uploads. Pastebin is a provider-operated website for storing text online for a chosen period, with public and account-based workflows, syntax formats, and developer APIs managed by the service operator.

Pastebin may suit users who need a familiar public text-paste site without maintaining an instance. MicroBin is more suitable when the operator wants a custom domain, local administration, file uploads, burn limits, and direct storage control, while accepting moderation and capacity responsibilities.

Who uses MicroBin

Developers share logs and code fragments, support teams exchange temporary diagnostic files, and small organisations distribute short-lived documents or download links. URL shortening and QR codes can also help when a long destination needs to be transferred to another device.

It is not a document archive, secret vault, malware-analysis service, recipient identity system, or compliance platform. Sensitive credentials should be rotated after sharing, and important files should remain in an independent authorised storage system.

Self-hosting MicroBin: requirements and cost

MicroBin is storage-driven because retained files and paste content consume the plan volume directly. Capacity also depends on upload size, expiry choices, burn limits, download traffic, concurrent visitors, syntax rendering, QR generation, and administration activity. PostgreSQL and MariaDB are Not required; the template persists MicroBin’s own data directory. MicroBin 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, MicroBin uses Plan 1 at €2. The hosted MicroBin package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The generated administrator account can inspect and remove every paste. Malware scanning, recipient verification, content moderation, legal retention, delivery certification, and permanent archival storage are not included. Restrict public use, choose short retention where appropriate, and keep original files separately.