Sitebin documentation

Sitebin is a dead-simple, no-login service for publishing and previewing files on the web. Upload one or more files — from the browser, a script, or an AI agent — and instantly get a public URL.

What a site is

Every upload becomes a site: a folder of files served on its own random subdomain. A site acts either as a web server (files served as-is, index.html as the entry point, optional SPA fallback) or as a file viewer (in-browser rendering for PDF, Markdown, DOCX, CSV/TSV, Jupyter notebooks, images, video, audio and source code). Switching between the two modes is lossless.

Creating a site returns a claim ticket — view URL, edit URL, edit password — shown exactly once. There are no accounts in the core: the ticket is the whole credential model. See Using Sitebin.

Ways to run it

• Hosted — app.sitebin.io, zero setup, free without an account. Plans.
• Self-hosted community — MIT-licensed, one container, one volume, no database. Start with the quickstart.
• Self-hosted Enterprise — adds accounts, OAuth, tiered quotas, billing and custom domains. See Enterprise setup.

Find your page

• Quickstart — DNS, docker run, compose variants, local testing.
• Using Sitebin — the claim ticket, modes, viewer, editor, expiry, view-access modes.
• API — every endpoint with copy-paste curl.
• Deploy from CI — the deploy script and GitHub Action.
• WebDAV & FTP — mount a site as a drive, and the client gotchas.
• Custom domains — DNS setup and automatic TLS (Enterprise).
• Embed component — put the drop area on your own site with <sitebin-drop>.
• Configuration — the full environment-variable reference.
• Operations & security — operator CLI, backup/restore, hosting responsibly.
• Enterprise setup — modes, tiers.json, OAuth, SMTP, billing, license keys.
• SaaS-Stack integration — SSO and subscriptions from the open-source IT-Trail SaaS Stack.