Skip to content

Status pages: which Communicate plan unlocks what, and status pages vs dashboards - #794

Merged
hlenke merged 2 commits into
mainfrom
docs/status-page-plans
Nov 7, 2026
Merged

hlenke merged 2 commits into
mainfrom
docs/status-page-plans

Conversation

@hlenke

@hlenke hlenke commented Nov 7, 2026

Copy link
Copy Markdown
Member

What changed

  • Status pages overview: new Plans section with a table of which Communicate plan unlocks each status page feature (custom domain, incident automation, status page maintenance, password protection, theme customization), and a note that the plan for your checks doesn't include them. Links to pricing for limits.
  • Status pages overview: new Status pages and dashboards section explaining when to use which.
  • Incident automation notes (overview and incidents page): "Team and Enterprise plans" → "Communicate Team and Enterprise plans".
  • Maintenance windows overview: "part of the Communicate add-on" → "available on Communicate Team and Enterprise plans", matching the status page maintenance page.

Why

"Team" was ambiguous: users on the Team plan for checks expected incident automation and status page maintenance to work, but those come with the Communicate Team plan. Users also regularly ask whether they need a status page or a dashboard.

Verification

Verified against the product code and on a local instance: with the Team plan for checks and no Communicate plan, custom domains, password protection, theme customization and automation rules were refused; Communicate Starter added custom domains; Communicate Team and Enterprise allowed all of them. Status page maintenance gating was verified against the code.

Checks

frontmatter, anchors, internal links, redirects, sitemap and mint broken-links: all pass.

🤖 Generated with Claude Code

Incident automation and status page maintenance need Communicate Team,
not the Team plan for checks. Add a feature/plan table and a short
comparison of status pages and dashboards to the overview.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
checkly-422f444a 🟢 Ready View Preview Nov 7, 2026, 9:14 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@hlenke hlenke left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Needs changes · The plan table is accurate, but three sibling pages still use the wording this PR fixes. Update them in this PR so the docs agree.

I checked every entry in the new Plans table against the product's plan definitions, and all of them are correct. It's a useful addition. Nothing blocks the merge. Only the sibling sweep is missing, plus one wording fix.

Important: siblings that still say the old thing (not in this diff, so they're listed here)

  • guides/communicate-availability.mdx:231 still has Incident automation is available on Team and Enterprise plans. That's the same ambiguous sentence this PR changes on the overview and incidents pages. Suggested: Incident automation is available on Communicate Team and Enterprise plans.
  • learn/incidents/anatomy-of-a-status-page.mdx:60 says on Team and Enterprise plans, [automation rules](...). Suggested: on Communicate Team and Enterprise plans.
  • communicate/status-pages/password-protection.mdx:9 says Password protection is available as a Communicate Team add-on. That leaves out Enterprise, which the new table lists, and it still uses "add-on", the term this PR replaces on the maintenance windows overview. Suggested: Password protection is available on Communicate Team and Enterprise plans.

I grepped main for the other plan notes on status page features. custom-domain.mdx (Starter, Team and Enterprise), customization.mdx and status-pages/maintenance-windows.mdx (Team and Enterprise) already match the table.

Merge readiness

  • CI: all six checks pass (docs-gate, static-docs-checks, preview-checks, Mintlify deployment, link-rot, vale-spellcheck).
  • Mergeable, state CLEAN. Since the merge base, main changed communicate/status-pages/overview.mdx in 415f636 (#799), which added a maintenance-window sentence under Uptime calculation. GitHub reports no conflict, and the new Plans section still lands after that paragraph.
  • Overlap: #792 touches communicate/status-pages/custom-domain.mdx, which this PR only links to. Either can land first.
  • pr_impact.py: no removed pages or anchors and no broken links. The only note is that communicate/maintenance-windows/overview is a hub page, and its slug and anchors are unchanged.

Section placement: Plans and Status pages and dashboards come after Uptime calculation and before Monitoring as code, so the page's main content stays first. That position works.

Inline: 0 blockers, 0 important, 1 wording.

What I checked
  • Read the full diff from merge base 7da4a04 to head 339491b: communicate/status-pages/overview.mdx, communicate/status-pages/incidents.mdx, communicate/maintenance-windows/overview.mdx. Also read the whole overview page at the head and communicate/dashboards/overview.mdx on main.
  • Verified against source (monorepo origin/main@2d79b98589):
    • apps/backend/api/src/common/services/billing-ng/products/communicate/communicate-hobby.ts, communicate-starter.ts and communicate-team.ts. Hobby includes status pages, components (services), subscribers and email notifications. Starter adds custom domain. Team adds status page maintenance, incident automation, theme colors (custom CSS), password protection and custom domain.
    • apps/backend/api/src/common/services/entitlements/lib/plan-overrides.ts: the Enterprise (contract) plan includes all five gated features. The Team plan for checks includes none of them, which supports "A Team plan for checks doesn't include the Communicate Team features".
    • The theme customization row maps to the custom CSS entitlement, which gates theme colors. See apps/webapp/src/pages/status-pages-next/status-pages-editor/sections/StatusPageEditorThemeColorsSection.vue and enforcement rule 201-status-page-custom-css.ts.
  • https://www.checklyhq.com/pricing/: the Communicate section uses the tier names Hobby, Starter, Team and Enterprise. The extracted text appears to list custom domain from Starter and the other four features from Team. The feature matrix didn't extract cleanly, so the source files above are the primary evidence. The tier names support the "Communicate Team and Enterprise" wording.
  • Grepped main for "Team and Enterprise", "Communicate add-on" and related plan notes in *.mdx to find the siblings above.
  • CI (gh pr checks), mergeability (gh pr view), git log <base>..origin/main on the touched files, the open-PR file list for overlap, and pr_impact.py.
  • No end-to-end test. Plan entitlements depend on billing, and checkly test can't exercise them, so the claims were verified against source.
  • Could not verify: nothing outstanding.

Comment thread communicate/status-pages/overview.mdx Resolved
@hlenke
hlenke enabled auto-merge (squash) November 7, 2026 21:14
@hlenke
hlenke merged commit dbf2776 into main Nov 7, 2026
6 checks passed
@hlenke
hlenke deleted the docs/status-page-plans branch November 7, 2026 21:17

This branch was successfully deployed

1 active deployment
staging — e4957c93 Deployed Nov 7, 2026 by mintlify[bot]
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.

1 participant