Pay for room,
not for permission

One upload = one site: a bundle of files served together on its own random subdomain (like k3x9q2.sitebin.app), managed by one edit URL and password. A site can be a full HTML app or a single PDF — same thing to us.

After 24 hours it answers "410 Gone" and its files are deleted shortly after. Want it to last? Create a free account and publish it there: Free sites live seven days and the clock restarts every time you change them, and paid plans keep sites until you delete them.

Always. Every site's edit page has a one-click ZIP download — sites with an account get the same export over the API — and the whole platform is open source, so you can move to your own server and keep the exact same workflow.

You can cancel any time in the plan page of your account — no notice period, no email to write — or, without signing in, on the cancellation page, which confirms by email at once. The plan keeps running until the end of the period you already paid for and is not charged again. Then your account drops back to Free limits, and your existing sites get 30 days — the date shows on each one in your dashboard. Upgrade again within that window and it disappears; the sites carry on as before. Sites over the Free storage quota stay online but stop accepting uploads until you're back under the caps. Custom domains you already attached keep serving — the cap is only checked when you add one, so you cannot attach new ones beyond what Free allows.

On Pro and Studio a site can run your project instead of serving its files: a Node.js app and a MySQL database, declared in a small sitebin-container-compose.yaml in the site's root. Sitebin puts it on the site's own address and your custom domains, and restarts it on every change to that file. The number is how many containers run at once across all your sites — Pro 3, Studio 20 — each with fixed memory and CPU. When a paid plan ends, running containers stop; their files stay with the site. How containers work.

On Pro and Studio a site's pages can have forms — contact, quote request, sign-up — without any backend. Add one on the edit page, paste its snippet into a page, and every submission arrives as an email with the fields laid out, the attachments, and a JSON copy. The recipient confirms once before anything is sent, and can stop it at any time. Sitebin keeps no copy of what is submitted. Pro has 1 form per site, Studio 10. How forms work.

Add it on the site's edit page and prove it is yours with one DNS record: a TXT record at _sitebin-challenge.<your domain> with the token the page shows, or a CNAME from your domain to the site's own <id>.sitebin.app address. Until the record is visible the domain is pending — not served, no certificate — and the claim is dropped after seven days if it never verifies. Route with the CNAME, or with an A record plus the TXT record kept in place. The certificate is issued on the first visit. Details in the docs.

On Studio you can add a domain you own as a zone — say clients.example.com — and point all of it at Sitebin with one wildcard record. You prove it once with a TXT record, and from then on every name under it attaches to your sites at once: no DNS record per site, and no limit on how many names — they do not count against your 25 custom domains. Nobody else can use a name in your zone. Details in the docs.

Drop and Free sites are where phishing pages turn up, so they are served with a strict content-security policy: the browser loads images and media only from the site itself, scripts, styles and fonts only from the site and the major CDNs (cdnjs, jsDelivr, unpkg, Tailwind, jQuery, Google Fonts), and lets the page send nothing to another server. Upload the image into the site and it shows. Pro and Studio sites are not restricted — they can hotlink, call any API and have forms. Details.

The claim ticket (edit URL + password) manages an anonymous site from its edit page for as long as it lives — but that is 24 hours, and scripted API access needs an account. Sign in and the same site type gets seven days that reset on every change, a dashboard, and the API.

Yes. The prices shown are what you pay as a consumer in the EU, VAT included; the rate — and so the net amount on the invoice — follows your billing country. Businesses that enter a valid EU VAT ID at checkout are charged without Austrian VAT under the reverse-charge mechanism where it applies, and the invoice says so. Payment is by card through Stripe.

If you buy as a consumer in the EU you can withdraw from the purchase within 14 days, no reason needed. Because the plan starts the moment you buy it, the checkout asks you to request that immediate start; withdraw afterwards and you pay only for the days you had the plan, the rest comes back to the same card. Details, and the model form, are in the withdrawal policy. After the 14 days, cancelling stops the next charge but does not refund the current period — except for a consumer in Germany on a yearly plan past its first year, who can cancel with one month's notice and gets the rest of the year back (terms, section 4). Everything else that governs a plan is in the terms of service.