Everything you need to
publish at speed

Pubby publishes in under 3 seconds. Not "fast for a static host." Under 3 seconds, consistently, whether you're pasting raw HTML in the editor, uploading a folder of files, or hitting the API from a script.

There's no build step. No queue. No waiting for a CI job to pass. You give Pubby content and Pubby gives you a URL. SSL is provisioned automatically on the same request. The page is live before you've alt-tabbed away.

Why does speed matter here? Because the whole point of a shareable page is sharing it. Every second between "I have something to show" and "here's the link" is friction you don't need.

Use case

A designer finishes a mockup and exports it as an HTML file. They drag it into Pubby, copy the URL, and paste it into Slack. The whole thing takes under 30 seconds from export to link in chat.

Point any domain you own at Pubby and your pages live there instead of on a Pubby subdomain. SSL is still automatic. DNS propagation is the only thing that takes time, and that's your registrar's problem, not ours.

Custom domains are available on Pro and above. Pro gives you one domain. Teams gives you three. Business gives you as many as you need. Each domain gets its own SSL cert, provisioned and renewed without you doing anything.

This matters for client work, where your page living at their-brand.com vs yourslug.pubby.au is the difference between looking professional and looking like a prototype. It also matters for any AI-generated content you're publishing at scale, where URL branding is part of the product.

Use case

An agency publishes monthly SEO reports for 12 clients. Each client has a subdomain on their own domain pointing to Pubby. Reports are auto-published via the API at the end of each month. Clients see their own domain in the URL, with SSL.

The Pubby API is a single endpoint. POST your file, get a URL back. That's it. No SDK required. No OAuth dance. No webhook config. One authenticated POST and your content is live.

It was designed specifically for programmatic publishing: AI agents that generate reports, scripts that export dashboards, pipelines that need to turn a file into a public URL without a human in the loop. If you can write a curl command, you can use the Pubby API.

Rate limits apply on the free plan. Pro and above get higher limits with documented burst capacity, so you can publish in batches without hitting a wall.

Use case

An AI research assistant generates a formatted HTML summary after each task. At the end of the run, it POSTs the file to the Pubby API and logs the returned URL. The user gets a permanent, shareable link to the report without ever touching a browser.

A shared workspace means the whole team publishes to the same place, with the same domains, under the same account. No more "I'll just use my personal account" workarounds. No more lost pages when someone leaves the company.

Roles are simple: Admin, Editor, Viewer. Admins manage billing and settings. Editors publish and manage content. Viewers can see what's published but can't change anything.

Shared API keys live at the workspace level, so your team's scripts and agents all publish to the same workspace without sharing personal credentials. Activity logs show who published what and when.

Use case

A startup's backend team uses the API to auto-publish internal release notes after each deploy. The product team edits and manages those pages in the web UI. Leadership has Viewer access to stay in the loop. One workspace, three different use patterns.

Basic analytics on every paid plan. You get page views, unique visitors, referrer sources, and geographic breakdown. Not a full analytics suite, but enough to know whether your page is being read or ignored.

Data is updated in near real-time. No third-party scripts are injected into your pages. The tracking is server-side, which means it works even if your visitors have ad blockers. You don't need to modify your HTML to get it.

Business plan gets advanced analytics: time-on-page estimates, download tracking for file attachments, and CSV export. Useful if you're publishing reports and need to prove they were actually opened.

Use case

A freelancer publishes project proposals as Pubby pages. Analytics tell them when a client opened the proposal and how long they spent on it. Not foolproof, but a useful signal before a follow-up call.

White-label removes all Pubby branding from published pages and from the URLs. Your clients see your name, your domain, your product. Nothing points back to Pubby unless you choose to mention it.

This is a Business plan feature. It covers the published page footer, browser tab titles, error pages, and password-protection screens. If Pubby would normally put its name somewhere, white-label takes it out.

You provide your brand name and optionally a logo, configure it once in your workspace settings, and every page published through that workspace picks it up automatically.

Use case

A digital agency builds a client reporting product on top of Pubby's API. Their clients receive monthly reports at reports.their-agency.com with the agency's logo on every page. The clients have no idea Pubby exists, which is exactly the point.