Fully Managed MicroBin
as a Service

Deploy MicroBin as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

MicroBin is a self-hosted pastebin and file-drop server: text snippets, file uploads, link shortening, QR codes and expiring or burn-after-reading links, with the convenience of a public paste site and the privacy of software you own.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

MicroBin

MicroBin

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
MicroBin Preview Image

ABOUT THE SOFTWARE

What is MicroBin

MicroBin is an open-source pastebin and file-sharing server written in Rust. It handles text snippets, file uploads, shortened links and QR codes, with expiry, burn-after-reading and encryption on every entry. One binary, one data directory, no database server.

The project is maintained by Dániel Szabó and released under the BSD 3-Clause licence; permissive, with no restriction on running it as a hosted service and no clause reserving commercial hosting to the author. The repository carries about 4,600 stars and the official container image has passed 1.7 million pulls, which puts it among the better-travelled small self-hosted tools rather than a weekend experiment.

Technically it is a single self-contained binary built on Actix Web, with templates and static assets embedded at compile time. State goes to SQLite by default, or to a flat JSON store if you prefer; either way there is no separate database process to run, back up or upgrade. The project describes its footprint as a few megabytes of memory and disk, which is why an instance costs the same €9 whether two people use it or forty.

FEATURES

What MicroBin does

MicroBin covers four jobs that usually take four services: sharing text, sharing files, shortening links and handing something to a phone. Every entry carries its own privacy tier, its own lifetime and its own encryption setting, chosen at the moment you create it.

Text pastes with syntax highlighting

Paste code, config or a log excerpt and MicroBin renders it with syntax highlighting and a language selector. A raw endpoint serves the same content unstyled for scripts and terminals.

File uploads

Share arbitrary files on a short URL. The unencrypted ceiling defaults to 2048 MB per file and the encrypted ceiling to 256 MB, both adjustable per instance.

Five privacy tiers per entry

Each upload is public, unlisted, private with server-side encryption, secret with client-side encryption, or a read-only postbox where people can add files without reading anyone else's.

Expiry and burn-after-reading

Lifetimes run from one minute to never. Entries can also destroy themselves after a set number of reads. The shipped defaults are a 24-hour expiry and a one-week ceiling.

AES-256 encryption, two ways

Server-side encryption protects an entry at rest. Client-side encryption locks it in the browser before it leaves the machine, so the instance never holds anything readable.

Link shortening and redirects

An entry can be a redirect rather than content, so the same instance works as a private link shortener without adding a second service for you to run.

QR codes

Generate a QR code for any paste or file to move it from a desktop to a phone without retyping a URL. It needs the public path set correctly, which we do at provisioning.

Memorable URLs and an admin panel

Links use readable animal words instead of random characters, and an admin panel lists and removes entries across the whole instance from one screen.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to MicroBin the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed MicroBin

Buyers move after a hosted transfer service rewrites its terms to claim a licence over uploaded content, or caps the free tier at ten transfers a month. MicroBin removes that exposure. Running it well, though, is a set of small operational chores that repeat forever.

The chores are specific. MicroBin ships with a published administrator username and password (literally admin and m1cr0b1n) which are fine on a laptop and an open door on a public address. Its garbage collector is the only thing that removes forgotten entries, so an instance with collection switched off grows until the disk stops. And large uploads fail at the reverse proxy long before they reach MicroBin's own size ceiling, because the proxy has its own limit that nobody thinks to raise.

The gotcha that costs people real data is the data directory. Operators have reported pastes disappearing after a container restart because the directory was never mounted on persistent storage; the service came back clean and the shares were gone. The related failure, fixed upstream, was the flat JSON store losing already-saved entries after a power cut. Both are volume and storage-engine decisions made once, at build time, by someone who has seen them fail.


REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run MicroBin on DANIAN

The pattern repeats across very different teams: something sensitive was being pasted or emailed to a service nobody controlled, and the fix had to be boring. These three show the configuration choices that follow from each starting problem.

12-PERSON SECURITY CONSULTANCY

Getting log excerpts off a public paste site

Analysts were pasting indicators and log fragments into a public site during triage. Their instance runs in an Asian region near the client estate, uploads disabled entirely, burn-after-reading as the default, and collection set to seven days so nothing outlives an engagement.

SIX-LAWYER PRACTICE

A client drop-box that replaced email attachments

Clients were mailing 40 MB scans that bounced. The practice runs the read-only postbox tier with an upload password, so a client can drop a file without seeing anyone else's. The region is set where the practice actually sits, so a 40 MB scan uploads without stalling on a slow round trip.

30-SEAT GAME STUDIO

Build handoffs after the per-seat transfer bill crossed $200

Ten paid transfer seats were costing more than the rest of the toolchain. One instance now serves the whole studio at €9: 2 GB build uploads, QR codes to push a test build straight to a handset, and a 72-hour default expiry so old builds clear themselves.

COMPARISON

Four ways to run MicroBin

The cost question is not really about the software, which is free. It is about who carries the storage growth, the restart behaviour and the proxy limits. Here is what each path costs at one, five and ten people, and what each one leaves on your desk.

Path1 user5 users10 usersWhat you also carry
Proprietary transfer service (WeTransfer Starter)$8/mo$40/mo$80/moPer-seat billing, vendor-set retention, and terms the vendor can rewrite. The free tier allows ten transfers a month with three-day expiry.
Self-host on a VPS$24/mo$24/mo$24/moYour evenings: volume mounts, garbage-collection tuning, proxy body-size limits, patching and off-site copies. Storage planning starts once uploads pass a few hundred gigabytes.
Home server (Raspberry Pi 5, 8 GB)$80 once + ~$8/yr powersamesameNo off-site copy, a residential uplink your share links depend on, and no cover when the disk fails while you are away.
DANIAN managed MicroBin€9/mo€9/mo€9/moNothing. Flat per instance regardless of how many people use it, with updates, backups, monitoring and a human on support included.

BY INDUSTRY

MicroBin for specific industries

Four sectors put unusual demands on a paste and file tool: they care less about sharing and more about what happens to the content afterwards. Retention windows, confidentiality duties and handling rules all land on the same three settings.

Broker-dealers work under FINRA Rule 4511 and SEC Rule 17a-4, which require business records to be preserved for three years with the first two immediately accessible, and many categories for six. A paste tool that silently deletes content on a 24-hour default cuts across that.

For these instances we invert the shipped defaults: expiry set to never as the baseline, garbage collection switched off, and the retention decision moved to the backup copies rather than the live store. A typical workflow is an operations analyst pasting a reconciliation extract for a colleague to check before a settlement cut-off. Because the whole state is one directory, a six-year record set of text entries usually sits under 2 GB, small enough that we keep daily copies for the full window without a storage upgrade.
ABA Model Rule 1.6 makes confidentiality of client information a duty that extends to how a firm transmits documents, and Rule 1.15 pushes the same care onto file custody. Emailing a scanned exhibit to a personal address fails both in a way that is hard to walk back.

We provision legal instances in the read-only postbox tier with an upload password, so a client can deposit a file without being able to list or read anything else on the instance, and we set client-side encryption as the default so the server holds no readable copy. The common workflow is intake: a new client drops five to fifteen scanned documents against a matter reference, typically 20 to 60 MB in total, and the fee earner pulls them once and files them in the practice management system.
NIST SP 800-61 sets the handling expectation for incident data: evidence is collected, restricted to the people working the incident, and not scattered across services outside the responder's control. Pasting a log excerpt containing internal hostnames into a public site breaks that in one click.

Response instances are configured with public listing off, uploads disabled, burn-after-reading enabled as the default and garbage collection at seven days, so triage material does not outlive the incident. The workflow is a responder pasting a 200-line log excerpt or a set of indicators for a second analyst, then the entry destroying itself on read. A busy response team generates a few hundred such entries a month, none of which should still exist a quarter later.
FERPA, at 20 U.S.C. 1232g and 34 CFR Part 99, restricts disclosure of student education records and gives families a 45-day window to inspect them. Records moving between offices on shared drive links, with no expiry and no record of who could reach them, is the failure mode.

For schools and departments we run the instance with listing off, uploads behind an upload password, and a 14-day default expiry so a transfer link does not survive the term. The workflow is a registrar moving a student file between campuses as a single encrypted entry rather than a mail attachment. A department handling 300 students typically moves 40 to 80 such files a term, each a few megabytes, which never approaches the included storage.

FAQ

Frequently asked questions

Three groups below: how MicroBin behaves and which settings we change, how you move onto it and what that takes, and how the DANIAN platform bills, backs up and supports the instance. Every answer is on this page rather than behind a support login.

01

Technical and configuration

MicroBin ships with a 2048 MB ceiling for unencrypted files and 256 MB for encrypted ones. Both are adjustable. We set them against your plan storage and match the reverse proxy body-size limit at the same time, which is the step most self-hosters miss.
We turn the public listing off by default, so the instance has no browsable index. Individual entries stay reachable only by their URL. If you want a shared listing for an internal team, say so and we switch it back on.
The garbage collector removes entries that have not been accessed for a set number of days, ninety by default. We tune that number to your plan storage and put a disk alert above it, because a forgotten never-expire entry has no other way of being cleared.
Yes. This is the failure people hit self-hosting: the data directory is not on persistent storage, the container restarts and the entries are gone. We mount that directory on backed-up persistent storage before the instance is handed over.
We run SQLite. The flat JSON store had a known failure where already-saved entries were lost after a crash or power cut, and although that has been fixed upstream, the database path is the one we would rather defend at three in the morning.
A private entry is encrypted by the server, so the instance can read it. A secret entry is encrypted in your browser before it is sent, so the instance holds nothing readable. Choose secret when the content should outlive our access to it.
Yes. We can disable file upload entirely, which is what response teams and some finance instances ask for. The paste, expiry, encryption and shortening features all keep working; only the file field disappears from the page.
By default MicroBin reports configuration and a periodic check-in upstream, and checks for new versions. We turn both off on every instance we run. If you want the update check on for your own visibility, we will leave it.
Yes. The title, footer text and custom stylesheet are all settable, and the logo and header can be hidden. Teams putting the instance in front of clients usually hide the logo and set their own title and colours.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
There is no built-in importer. In practice most teams do not migrate history: they stand the new instance up, point people at it, and let the old links expire.
You choose the app and region, we provision it, and you get a URL with TLS already working and the defaults set. There is no server for you to build, and no proxy configuration file for you to edit.
Yes. Custom domains are included at no extra cost. Point the record at the instance and the certificate is issued and renewed automatically. We set the public path at the same time, which is what makes QR codes resolve correctly.
Yes. Send us the registrar you use and we will tell you exactly which record to create, or check it after you have created it. This is the step that most often stalls a launch, so we do not leave it to a documentation link.
Yes. The entire state is one data directory containing the database and the uploaded files. Ask and we hand it to you. There is no proprietary format and nothing of yours stays behind.

03

Billing, support and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed MicroBin for 7 days

No card. Cancel from the dashboard.