Skip to content

Retire the free shared-realm offering across docs, marketing, and legal - #347

Open
pnzrr wants to merge 7 commits into
mainfrom
update/retire-free-shared-realms
Open

Retire the free shared-realm offering across docs, marketing, and legal#347
pnzrr wants to merge 7 commits into
mainfrom
update/retire-free-shared-realms

Conversation

@pnzrr

@pnzrr pnzrr commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Free, shared realms were discontinued and the shared infrastructure was shut down on 2026-07-30 (announcement). The site still sold, documented, and legally described that product. This brings phasetwo.io in line with what we actually ship: dedicated clusters in three tiers, with Starter carrying a 30-day free trial.

All product facts here are taken from dashboard (create-dedicated-cluster.tsx, detailed-comparison.tsx), not from the old copy.

Commits, in review order

  1. legal: describe the tiers we actually sell — the Service Agreement's "Starter" entry was the retired free-realm definition (1,000 users, <10 IdP connections, community support) wearing the new tier's name. Replaced all three tier descriptions with real terms. The SLA named only "Dedicated" and "Enterprise", leaving Starter outside a document the pricing page referenced. Also drops a 99.99% uptime SLA claim we do not sell.
  2. legal: scope the SLA to Premium and Enterprise — Starter is best-effort with no commitment, stated at the top of the SLA, in the uptime clause, and over the response/resolution times. Pricing surfaces that claimed a "95% uptime guarantee" / "Standard" SLA for Starter now read as a target on best effort.
  3. marketing: sell the trial, not a free deployment — 17 surfaces promised a free deployment. The 15 that shared one string now inherit it from homepage-dual-line-cta.jsx, so the next pricing change is one line instead of fifteen.
  4. docs: realms live in clusters now — realm docs renamed and rewritten around clusters; dead /realms/add-realm links and the shared-deployment migration section removed; the tier table corrected.
  5. blog: point the tutorials at the Starter trial — six evergreen tutorials repointed. Dated announcements deliberately untouched.

Verification

npx docusaurus build passes. Both moved URLs get client redirects, verified in the build output:

  • /docs/self-service/deployments//docs/self-service/realms/
  • /hosting/deployments//hosting/dedicated-clusters/

The only build warnings are a pre-existing broken /product/sso/#idp-wizard anchor that fires on every page — unrelated to this change.

TODO before or shortly after merge

  • Re-shoot static/docs/dashboard/realms.png — referenced by dash-overview.md; shows the removed standalone realms view.
  • Re-shoot static/docs/dash-v2-open-console-realms-view.png — referenced by realms.md; same screen.
  • Delete the now-unreferenced screenshots once the above land: overview-add-realm.png, realms-create-realm.png, realms-add-realm.png.
  • Companion dashboard PR (queued separately): detailed-comparison.tsx still carries "Allowed on Starter, but voids the SLA" plus Starter: "95%" / sla: "Standard", now out of step with the SLA page.

Decisions worth a second opinion

  • Pen-test policy — resolved. The old restriction was scoped to shared clusters. Confirmed with Jeff that the policy is no pen tests on Starter, so penetration-tests.md now says that explicitly and points at the upgrade path (commit docs: no penetration testing on Starter).
  • hosting/deployments.jsx deleted. Nothing linked to it, it duplicated hosting/dedicated-clusters, and it advertised a flat 99.95% SLA. Redirected rather than kept.
  • Formatting. The touched files are not Prettier-clean on main and there is no format gate in CI, so they are left as-is. Running Prettier would bury a ~20-line change in a ~2,000-line diff.

pnzrr added 5 commits August 19, 2026 10:28
The Service Agreement's "Starter" entry was the retired free-realm
definition (1,000 users, <10 IdP connections, community support) wearing
the new tier's name. Replace all three tier descriptions with the terms
the checkout flow actually sells, and select a tier at cluster creation
rather than deployment creation.

The SLA named only "Dedicated" and "Enterprise" plans, leaving Starter --
a dedicated cluster with a 95% guarantee -- outside a document the
pricing page nonetheless referenced. Name the three tiers, and scope
Starter to an availability target without service credits; the feature
table's "voids the SLA" note becomes "not covered by the uptime
guarantee" to match.

Also drop two stale claims from the comparison layout: a 99.99% uptime
SLA we do not sell, and shared clusters we no longer offer.
Starter is a best-effort tier: we operate it toward 95% but commit to
nothing. Say so once at the top of the SLA, restate it in the uptime
clause, and scope the response and resolution times -- previously stated
unconditionally -- to the two tiers that pay for them.

The pricing surfaces claimed more than that: the Starter card advertised
a "95% uptime guarantee" and the comparison table gave Starter a
"Standard" SLA. Both now read as a target on best effort.
Seventeen surfaces still promised a free deployment. Fifteen of them
passed the same "Create Your Free Deployment Today." string into the
shared CTA, so make that component own the default copy -- now the
30-day trial -- and delete the prop from every call site. The next
pricing change is one line instead of fifteen.

The hosting page was still framed around Deployments as a product and
advertised a flat 99.95% uptime SLA, which is the Enterprise number.
Reframe it on clusters and qualify the headline stats.

Formatting note: these files are not Prettier-clean on main and this
repo has no format gate, so they are left as-is rather than reformatted
-- running Prettier here would bury a 20-line change in a 2,000-line diff.
Free shared realms were shut down on 2026-07-30, so the docs no longer
describe a real product. Rename the realm page to match what it is,
delete the standalone creation flow it documented (two links into
dash.phasetwo.io/realms/add-realm, a route that no longer exists) and
keep only the cluster-scoped path. A note points readers at the Starter
tier and the announcement.

Drop the shared-deployment migration section, and reword the passages
that explained clusters by comparison to shared deployments -- there is
no longer a reader who knows what those were.

The tier table in create-a-cluster claimed 99/99.5/99.9% uptime; we sell
95% target, 99.5% and 99.95%, and size tiers by monthly active users
rather than concurrent sessions everywhere else. Correct both.

Also retire the standalone hosting/deployments page: nothing linked to
it, it duplicated hosting/dedicated-clusters, and it advertised a flat
99.95% SLA. Both moved URLs get client redirects.

The pen-test policy forbade tests on shared clusters. That rationale was
multi-tenancy; with every cluster dedicated the sentence has no subject,
so it is removed rather than reassigned to a tier -- see the PR body.
Eight passages across six evergreen tutorials told readers to create a
free realm to follow along. That path is gone, so each now sends them to
a Starter cluster and its 30-day trial.

Dated announcements are left alone -- they were true when published, and
rewriting them would falsify the record. The multi-tenancy walkthrough
is the one substantive edit: it walked through creating a deployment,
which is now creating a cluster and adding a realm to it.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 19, 2026

Copy link
Copy Markdown

Deploying phasetwo-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: d7733fd
Status: ✅  Deploy successful!
Preview URL: https://6ec75455.phasetwo-docs.pages.dev
Branch Preview URL: https://update-retire-free-shared-re.phasetwo-docs.pages.dev

View logs

pnzrr added 2 commits August 19, 2026 12:31
The old restriction was scoped to shared clusters and I removed it with
them rather than invent a replacement. Confirmed with Jeff: the policy
is that Starter does not get pen tests. State it, and point at the
upgrade path rather than leaving a flat no.
One conflict, in docs/self-service/resources.md. Main rewrote the
section to add Password Denylists and an "Apply to Realm" flow; our side
had only renamed "Realm (deployment)" to "Realm" in the same sentence.
Took main's rewrite whole and reapplied the rename to it.
@pnzrr
pnzrr requested a review from xgp August 19, 2026 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants