[Hold] New pricing and account tiering #783
Merged
+242
−271
Conversation
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
Paul-Cornell
requested review from
MKhalusova,
ajaykrish-uns and
ron-unstructured
MKhalusova
approved these changes
Nov 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ready for review in advance of launch.
DO NOT MERGE until the related Marketing content has gone live. Coordinate with Marketing accordingly.
Main pages of interest:
Most of the other content updates are somewhat minor. These include renaming account tiering names, changing "enterprise" mentions and branding to "business" including URL redirects from
enterprise->business, and making clear technical distinctions where needed for the functionality of Business SaaS deployments verses the two other Business deployment types (dedicated instances and in-VPC).