How publr works

Five steps from "I have a file" to "I have a URL". The private beta exposes only the capabilities whose production switches are enabled; the pricing page previews the broader launch tiers.

• 1 · Upload

  Drop a PDF, image or another file type explicitly enabled for the private beta. We take the file directly to Cloudflare R2 instead of relaying the bytes through the API Worker.

• 2 · Sandbox

  The file is published to a sandbox URL on publr.site. It's already live and shareable. Anonymous uploads do not require an account; the sandbox is meant for trying things out and quick shares.

• 3 · Claim

  Receive a one-click claim link. Sign up (or sign in) and click it once — the URL moves into your account. The slug stays the same. Version history, analytics, password protection and custom-domain support unlock at this point.

• 4 · Schedule

  Approved Pro and Agency tester accounts can schedule a future publish date. Visitors see a countdown before the URL flips live without a redirect.

• 5 · Share

  Share the URL anywhere — Twitter, Notion, Slack, email signature. Pro+ accounts can attach a custom subdomain (CNAME) so the URL becomes mysite.example.com. Privacy-respecting analytics start the moment a visitor lands.

Built-in safety nets

• OpenAI moderation on every upload

  Every file is scored before going live. CSAM, malware, phishing pages and explicit content get blocked. Visitors never see a takedown banner.

• IP-free analytics

  Visitor fingerprinting derives from a daily-rotated salt + UA + country bucket — no plain-text IP storage. GDPR/LGPD-aware from day one.

• No vendor-locked content

  Your file lives in your Cloudflare R2 bucket on the Agency plan, or in our R2 on lower tiers — either way, exportable any time. No HTML embedded in our database.