Skip to content

smart-shield: clarify Regional Tiered Cache availability (SHIP-15052)#30674

Open
cnachiappan-dev wants to merge 2 commits intocloudflare:productionfrom
cnachiappan-dev:cnachiappan/SHIP-15052-rtc-availability
Open

smart-shield: clarify Regional Tiered Cache availability (SHIP-15052)#30674
cnachiappan-dev wants to merge 2 commits intocloudflare:productionfrom
cnachiappan-dev:cnachiappan/SHIP-15052-rtc-availability

Conversation

@cnachiappan-dev
Copy link
Copy Markdown

Summary

Clarify that Regional Tiered Cache is included with Enterprise plans, and that Smart Shield Advanced is the path for non-ENT (Free/Pro/Business) plans. Current docs state only "Available with Smart Shield Advanced," which implies all plan tiers must purchase Smart Shield Advanced — incorrect.

This was the source of in-product confusion where an Enterprise zone sees the RTC toggle on the free Smart Shield package while the docs and the dashboard Explore Packages modal both imply Smart Shield Advanced is required. Confirmed with the Smart Shield PM that the correct positioning is: ENT plans include RTC as they always have; Smart Shield Advanced adds RTC for non-ENT plans.

Changes

  • src/content/docs/smart-shield/configuration/regional-tiered-cache.mdx — rewrite the availability note from Available with Smart Shield Advanced. to Included with Enterprise plans. Available to Free, Pro, and Business plans through Smart Shield Advanced.
  • src/content/docs/smart-shield/get-started.mdx — add a callout under the Smart Shield Advanced subsection (parallel in style and placement to the existing Dedicated CDN Egress IPs callout) explaining ENT entitlement.
  • src/content/docs/smart-shield/index.mdx — extend the Regional Tiered Cache bullet on the overview page to reflect the dual availability path.

Why this matters

The Regional Tiered Cache PRD explicitly states: "Regional Tiered Cache is ENT-only and is included in that plan level." Smart Shield Advanced was introduced later as a way to extend RTC (and Cache Reserve, Aegis) to PAYGO/non-ENT customers — it does not replace the existing ENT plan entitlement.

Field-side this caused a multi-surface contradiction across the dashboard splash, Explore packages modal, and developer docs in the same customer session. The dashboard-side fixes are tracked under SHIP-15053; this PR fixes the docs side.

Verification

Reviewer

Requested review: Cody Anthony (canthony@cloudflare.com — please add yourself as a reviewer when you see this; I could not resolve your GitHub handle confidently).

References

  • Internal: SHIP-15052 (this work)
  • Internal: SHIP-15053 (sibling: dashboard fix)
  • Internal: SHIP-14978 (parent: Smart Shield Master Task)

The current docs state that Regional Tiered Cache is "Available with
Smart Shield Advanced," which implies all plan tiers must purchase
Smart Shield Advanced to access it. This is incorrect: Enterprise
plans include Regional Tiered Cache regardless of Smart Shield
package, and Smart Shield Advanced only adds it for Free, Pro, and
Business plans.

This is the source of in-product confusion where ENT zones see the
RTC toggle on a free Smart Shield package while the docs and Explore
Packages modal imply Smart Shield Advanced is required.

Updates:
- regional-tiered-cache.mdx: rewrite the availability note to call
  out Enterprise inclusion and the Smart Shield Advanced path for
  non-ENT plans.
- get-started.mdx: add a callout under Smart Shield Advanced
  (parallel to the existing Dedicated CDN Egress IPs callout)
  explaining ENT entitlement.
- index.mdx: extend the RTC bullet on the overview page to reflect
  the dual availability path.

Refs SHIP-15052.
Copy link
Copy Markdown
Contributor

@codyanthony850 codyanthony850 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look correct — builds clean locally. One minor suggestion on the index.mdx parenthetical for consistency with sibling bullets.

Comment thread src/content/docs/smart-shield/index.mdx Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants