Why We Called It "Gated Publishing" (And the 7 Names We Rejected)

Category naming is a consequential decision. The name determines which searches find you, which analogies come to mind, and whether you're competing in a crowded space or creating an empty one.

We evaluated eight names before settling on "gated publishing." Here's the decision — including the reasoning behind each rejection.

The job we're naming

The job: take a file (HTML or Markdown), give it a permanent URL, and make that URL accessible only to people with a verified company email.

This sounds simple. The naming challenge is that it's adjacent to many established categories — hosting, sharing, deployment, documentation — without being exactly any of them. Every obvious name imports baggage from the wrong category.

The 8 candidates

1. "Secure sharing" ❌

The problem: "Secure sharing" is owned by enterprise file sharing (Dropbox Business, Google Drive, SharePoint). It implies sharing files — with download buttons and storage. Our product serves rendered pages, not files. Positioning ourselves in the file sharing category invites comparison to products with 10-year head starts that aren't actually competitors.

Also: every security product calls itself "secure." The word has lost all meaning.

2. "Private hosting" ❌

The problem: "Private" in hosting usually means "you pay for the server" (private VPS vs. shared hosting). The search intent for "private hosting" is developers looking for VPS services. Not our audience.

3. "Authenticated static hosting" ❌

The problem: Technically accurate. Searches for "authenticated static hosting" are rare and typically come from DevOps engineers already deep in the infrastructure approach (building their own S3 + Cognito stack). Good for SEO in that specific context — which is why we use it as a secondary keyword in some pieces — but not strong enough as a primary category name. It describes the mechanism, not the job.

4. "Internal publishing" ❌

The problem: "Internal" is redundant. Every product in this category is inherently internal — the whole point is restricting to your company. It also doesn't distinguish publishing (serving a rendered page at a URL) from sharing (sending a file). A Confluence page is "internal publishing" by this definition.

5. "Access-controlled hosting" ❌

The problem: Accurate but mechanical. "Access-controlled" describes IT infrastructure. It positions the product as a technical implementation rather than a workflow solution. Developers would use this phrase in a security document, not when describing what they need.

6. "Company auth hosting" ❌

The problem: Too narrow and too technical. "Company auth" doesn't describe an established concept; it describes one mechanism among several. Also awkward as a noun phrase.

7. "Private static sites" ❌

The problem: "Private static sites" is a real search term (mostly GitHub Pages-related), which is good. But "site" implies a multi-page, maintained structure — a developer documentation site, a marketing site. Our typical artifact is a single file: one HTML report, one architecture diagram, one competitive analysis. "Sites" suggests scale we don't require.

8. "Gated publishing" ✅

Why it works:

"Publishing" captures the right action. Publishing is an intentional act: making something available at a permanent address for a specific audience. It's distinct from sharing (transient, file-based), hosting (infrastructure-focused), and deployment (code-centric). Publishing implies that the artifact is complete and ready for its audience — which is exactly the workflow.

"Gated" captures the right restriction. A gate is a feature you control: open or closed. "Private" implies permanently restricted; "gated" implies access control you can configure. You can open the gate (make an artifact public) or close it (company auth only). The gate is a capability, not a state.

It's a phrase that doesn't exist yet. Searching "gated publishing" returns almost nothing before our content. We own it by default. There's no established player in the category who gets found first.

It describes the job, not the mechanism. A user searching "gated publishing" is thinking about the workflow — publish something, gate the access. Not about S3 buckets, Lambda@Edge, or Cognito user pools.

It scales. As the category grows, "gated publishing" can expand to cover more scenarios: gated video hosting, gated interactive content, gated data products. The name isn't locked to HTML files.

The criteria we used

We evaluated each name against five criteria:

1. Search intent match: Do people searching this phrase want what we offer?
2. Category ownership: Can we own this phrase, or is it contested by larger incumbents?
3. Conceptual accuracy: Does it describe the job correctly?
4. Expandability: Does it still work if the product grows?
5. Memorability: Can someone repeat it accurately in a sentence?

"Gated publishing" scores highest on all five. "Authenticated static hosting" is a close second on accuracy and search intent, but loses on memorability and category ownership.

What we're building

By naming the category, we're making a bet: there are enough people with this specific problem — publish HTML, gate by company email — that they'll search for it, and finding "gated publishing" will immediately resonate.

The bet seems to be paying off. If you're reading this because you searched "gated publishing," we named the right thing.