content: rename platform "add-ons" to "packages" for Boost/Scale/Enterprise#17068
Merged
Conversation
…rprise Boost, Scale, and Enterprise are now referred to as platform packages, not add-ons. The word "add-on" was implying a bolt-on rather than the foundational nature of these packages, so billing has dropped the term and the rest of the site should follow. This sweep updates the language across docs, handbook, blog, and a few page files. Other true add-ons (Group Analytics, Mobile Replay retention, CDP) keep the "add-on" wording. Generated-By: PostHog Code Task-Id: 799eadec-c3b1-4ee5-a01d-c441211a538a
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 123 errors, 567 warnings, 12 suggestions in your markdown Full report → · Copy the Job Summary code block into an LLM to batch-fix issues.
|
a-lider
approved these changes
May 27, 2026
ReeceJones
approved these changes
May 27, 2026
Contributor
ReeceJones
left a comment
ReeceJones
left a comment
There was a problem hiding this comment.
Make sure to also update the monorepo so that the frontend displays the new package terminology on billing pages and components.
Member
Author
|
@ReeceJones Alex already updated billing! |
Member
Author
|
Oh wait there is still one ref on billing page, will fix |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Boost, Scale, and Enterprise are now referred to as platform packages, not "add-ons". The word "add-on" was implying a bolt-on rather than the foundational nature of these packages — billing has already dropped the term, so the rest of the site should follow.
This PR sweeps the language across docs, handbook, blog, and a few page files. True add-ons (Group Analytics, Mobile Replay retention, CDP, etc.) are intentionally left alone, as are references to competitor "add-ons" (e.g. Mixpanel's Enterprise add-on in comparison blog posts).
Notable changes:
src/pages/baa.tsx— user-facing BAA copy and legal text now call Boost/Scale/Enterprise "packages"src/pages/terms.tsx— Uptime SLA clause references "Enterprise package"src/pages/startups/[...slug].tsx— startup credit FAQ uses "Boost package" / "platform package"contents/docs/— HIPAA, migration, access control, activity logs, SSO, dashboards, transformations docs all updatedcontents/handbook/— sales, onboarding, billing, and cross-selling handbook entries updatedposthog-vs-optimizely,posthog-vs-mixpanel,best-hipaa-compliant-ab-testing-tools,the-posthog-array-1-41-0) updated where they describe PostHog's own packagescontents/teams/platform-features/— team objective/strategy doc referenceshttps://posthog.com/platform-addons→https://posthog.com/platform-packagesinslack-channels.md/platform-packages#boost-add-oncollapsed to/platform-packages(those anchors don't exist on the page)Checklist
Created with PostHog Code