Skip to content

feat: added new content #4783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
108 changes: 108 additions & 0 deletions sites/platform/src/administration/organizations.md
Original file line number Diff line number Diff line change
Expand Up @@ -146,3 +146,111 @@ Ownership transfer automatically transfers subscription charges to the new organ
To transfer an organization to a different owner, first make sure that user is part of the organization.
If they aren't yet, [add them](/administration/users.md#add-a-user-to-an-organization).
Then open a [support ticket](/learn/overview/get-support.md) from the current organization to ask for the transfer.

## Fixed and Flex organizations

### What is a fixed organization?
Ideal for workloads that have consistent resource requirements with stable and predictable usage.
Users can select a plan with predefined CPU and Memory resources. You can not adjust these resources, nor scale them automatically. To increase capacity, you’ll need to upgrade to a higher plan.

### What is a flex organization?
Ideal for workloads that evolve over time or have dynamic resource requirements.
Flex will suit most use cases.
Users will be able to allocate the exact CPU and Memory resources that your applications and services need. You can adjust these resources at any time, or configure them to adapt automatically. You are charged based on the resources you allocate.

### What can you do?
When creating a new organization, users will be able to select the organization type from a drop-down option based on their preference. Once the organization is created, users can manage their organizations like they do today.

## FAQs
### Will customers who have organizations in both fixed and flex still switch between two different consoles?
Correct, they will be able to select their organization (fixed or flex) from a drop-down.

### How will fixed vs flex be identifiable in the console?
Organizations will have tags next to the names in the console.

### Will customers with fixed projects be able to access them via the upsun cli tool?
Correct.

### Will customers with fixed projects still use the same configuration files and configuration file structures (ie .platform.app.yaml, .platform/services.yaml, .platform/routes.yaml, etc?
Correct.

### Will mount differences still exist between fixed and flex after Sept?
Yes, waiting for the git fixes for this.

### Beyond the name “platform.sh” going away in console, are there other visual changes in the fixed console that will be different than it is today?
Org creation flow is being updated, free trial for only flex orgs, @Ndifreke @Miguel is there anything else?

### Assuming a unified CLI, will there be a new field when viewing a project list to identify fixed vs flex?
Users have a list of all the organizations and right now there is no field for flex/fixed in the cli.







This document provides content for new information to be displayed on Upsun docs and Platform.sh docs for fixed and flex org types as part of Brand Merger 2025.
What is happening?
As part of Brand Merger in Sep 2025, users will have the option to create either a fixed organization (currently known as PSH) or flex organization.

Where should we reflect this update?
This requires a new section in:
https://docs.upsun.com/ particularly under this section: https://docs.upsun.com/administration/organizations.html
https://docs.platform.sh/ particularly under this section https://docs.platform.sh/administration/organizations.html
Potentially a new page?

Content
What is a fixed organization?
Ideal for workloads that have consistent resource requirements with stable and predictable usage.
Users can select a plan with predefined CPU and Memory resources. You can not adjust these resources, nor scale them automatically. To increase capacity, you’ll need to upgrade to a higher plan.

What is a flex organization?
Ideal for workloads that evolve over time or have dynamic resource requirements.
Flex will suit most use cases.
Users will be able to allocate the exact CPU and Memory resources that your applications and services need. You can adjust these resources at any time, or configure them to adapt automatically. You are charged based on the resources you allocate.

What can the customer do?
When creating a new organization, users will have the option to select the organization type from a drop-down option based on their preference.


Once the organization is created, users can manage their organizations like they do today.

More to follow: There will be a table in this section highlighting the feature differences between fixed and flex (WIP)

Feature chart

Flexible Resource Allocation
Flex: Users can customize resources per container (per app or service) for ALL environments.
Fixed: Resource from the plan is applied to the production environment. For preview, the user has the default small size for all containers.
FAQs
What happens to my URL?
https://auth.api.platform.sh/ will become https://auth.upsun.com/.

If I had a fixed organization (previously Platform.sh), will I be redirected to my organizations?
Yes, you will be automatically redirected to the new console. You will be able to login using the same credentials.

Will I be able to switch if I have both fixed and flex organizations?
Yes, you will be able to navigate between your organizations (fixed or flex) from a drop-down list.

How will fixed vs flex be identifiable in the console?
Organizations will have tags next to the names in the console. Organizations will also be categorized by organization types in console.

Will I be able to access fixed projects via the upsun CLI?
Correct.

WillI I be able to (with fixed projects) still use the same configuration files and configuration file structures (ie .platform.app.yaml, .platform/services.yaml, .platform/routes.yaml, etc?
Correct.

Will mount differences still exist between fixed and flex after Sept?
Yes, waiting for the git fixes for this.

Beyond the name “platform.sh” going away in console, are there other visual changes in the fixed console that will be different than it is today?
New way to create organizations ( either fixed or flex).
Be able to navigate between the two organization types.
15-day free trial for users creating flex organizations.

Assuming a unified CLI, will there be a new field when viewing a project list to identify fixed vs flex?
You will have a list of all the organizations. There is no field for flex/fixed in the CLI.



36 changes: 36 additions & 0 deletions sites/upsun/src/administration/organizations.md
Original file line number Diff line number Diff line change
Expand Up @@ -154,3 +154,39 @@
To transfer an organization to a different owner, first make sure that user is part of the organization.
If they aren't yet, [add them](/administration/users.md#add-a-user-to-an-organization).
Then open a [support ticket](/learn/overview/get-support.md) from the current organization to ask for the transfer.

## Fixed and Flex organizations

### What is a fixed organization?
Ideal for workloads that have consistent resource requirements with stable and predictable usage.
Users can select a plan with predefined CPU and Memory resources. You can not adjust these resources, nor scale them automatically. To increase capacity, you’ll need to upgrade to a higher plan.

### What is a flex organization?
Ideal for workloads that evolve over time or have dynamic resource requirements.
Flex will suit most use cases.
Users will be able to allocate the exact CPU and Memory resources that your applications and services need. You can adjust these resources at any time, or configure them to adapt automatically. You are charged based on the resources you allocate.

### What can you do?
When creating a new organization, users will be able to select the organization type from a drop-down option based on their preference. Once the organization is created, users can manage their organizations like they do today.

## FAQs
### Will customers who have organizations in both fixed and flex still switch between two different consoles?
Correct, they will be able to select their organization (fixed or flex) from a drop-down.

### How will fixed vs flex be identifiable in the console?
Organizations will have tags next to the names in the console.

### Will customers with fixed projects be able to access them via the upsun cli tool?

Check failure on line 179 in sites/upsun/src/administration/organizations.md

View workflow job for this annotation

GitHub Actions / vale

[vale] sites/upsun/src/administration/organizations.md#L179

[Vale.Terms] Use 'Upsun' instead of 'upsun'.
Raw output
{"message": "[Vale.Terms] Use 'Upsun' instead of 'upsun'.", "location": {"path": "sites/upsun/src/administration/organizations.md", "range": {"start": {"line": 179, "column": 71}}}, "severity": "ERROR"}

Check failure on line 179 in sites/upsun/src/administration/organizations.md

View workflow job for this annotation

GitHub Actions / vale

[vale] sites/upsun/src/administration/organizations.md#L179

[Vale.Spelling] Did you really mean 'cli'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'cli'?", "location": {"path": "sites/upsun/src/administration/organizations.md", "range": {"start": {"line": 179, "column": 77}}}, "severity": "ERROR"}
Correct.

### Will customers with fixed projects still use the same configuration files and configuration file structures (ie .platform.app.yaml, .platform/services.yaml, .platform/routes.yaml, etc?

Check failure on line 182 in sites/upsun/src/administration/organizations.md

View workflow job for this annotation

GitHub Actions / vale

[vale] sites/upsun/src/administration/organizations.md#L182

[Vale.Spelling] Did you really mean 'ie'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'ie'?", "location": {"path": "sites/upsun/src/administration/organizations.md", "range": {"start": {"line": 182, "column": 114}}}, "severity": "ERROR"}
Correct.

### Will mount differences still exist between fixed and flex after Sept?
Yes, waiting for the git fixes for this.

### Beyond the name “platform.sh” going away in console, are there other visual changes in the fixed console that will be different than it is today?
Org creation flow is being updated, free trial for only flex orgs, @Ndifreke @Miguel is there anything else?

Check failure on line 189 in sites/upsun/src/administration/organizations.md

View workflow job for this annotation

GitHub Actions / vale

[vale] sites/upsun/src/administration/organizations.md#L189

[Vale.Spelling] Did you really mean 'orgs'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'orgs'?", "location": {"path": "sites/upsun/src/administration/organizations.md", "range": {"start": {"line": 189, "column": 62}}}, "severity": "ERROR"}

### Assuming a unified CLI, will there be a new field when viewing a project list to identify fixed vs flex?
Users have a list of all the organizations and right now there is no field for flex/fixed in the cli.

Check failure on line 192 in sites/upsun/src/administration/organizations.md

View workflow job for this annotation

GitHub Actions / vale

[vale] sites/upsun/src/administration/organizations.md#L192

[Vale.Spelling] Did you really mean 'cli'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'cli'?", "location": {"path": "sites/upsun/src/administration/organizations.md", "range": {"start": {"line": 192, "column": 98}}}, "severity": "ERROR"}
Loading