diff --git a/docs/src/components/pricing/FAQ.tsx b/docs/src/components/pricing/FAQ.tsx
index 32cc0cd3e2c5a2..904440afa0db4b 100644
--- a/docs/src/components/pricing/FAQ.tsx
+++ b/docs/src/components/pricing/FAQ.tsx
@@ -17,15 +17,11 @@ const faqData = [
summary: 'How do I know if I need to buy a license?',
detail: (
- If you are in doubt, check the license file of the npm package you're installing.
-
-
- For instance
- @mui/x-data-grid
- {' '}
- is MIT while{' '}
- @mui/x-data-grid-pro is
- commercial.
+ If you are in doubt, check the license file of the npm package you're installing. For
+ instance @mui/x-data-grid is
+ an MIT License (free) while{' '}
+ @mui/x-data-grid-pro is a
+ Commercial License.
),
},
@@ -64,20 +60,30 @@ const faqData = [
),
},
{
- summary: 'Why does developers using MUI X indirectly needs to be licensed?',
+ summary: 'Why do we must license developers not using the software directly?',
detail: (
- The number of seats purchased must include developers using MUI X Pro or Premium directly{' '}
- and indirectly.
+ Our pricing model requires all developers working on the same project that the software is
+ used into to be licensed. This is designed to make it easier for your engineers to use the
+ software without having to constantly verify if they have the right number of seats. It aims
+ to replicate one of the great properties open-source licenses have: simplicity.
- We are including indirect developers in the pricing model to help reduce the creation of
- silos in your engineering organization. If only direct developers needed a license, then
- only a handful of engineers would be allowed to use MUI X.
+ Our pricing model also requires developers using the software indirectly to be licensed,
+ e.g. through a wrapper library. This is because the more developers in your organization
+ using the software, the more they need comprehensive documentation, and the more hedge cases
+ they will ask to be supported.
- In exchange, the price point per developer is lower than it would be if only direct
- developers needed a seat.
+ The price point per developer was adjusted to be much lower than what it would be if only
+ direct use needed a license.{' '}
+
+ The clause in the EULA.
+
),
},
diff --git a/docs/src/components/pricing/WhatToExpect.tsx b/docs/src/components/pricing/WhatToExpect.tsx
index fb101774e9509b..ae68685e6aa998 100644
--- a/docs/src/components/pricing/WhatToExpect.tsx
+++ b/docs/src/components/pricing/WhatToExpect.tsx
@@ -36,8 +36,9 @@ export default function WhatToExpect() {
You can use the software in a production environment forever. All the versions of the
- software released until the end of your subscription are available. There are no
- further charges unless you choose to continue development.
+ software released until the end of your subscription are available in perpetuity.
+ There are no further charges unless you choose to continue development. See the
+ "Development license" section of this page for more details.
@@ -56,10 +57,10 @@ export default function WhatToExpect() {
- The licenses are sold on a per-developer basis. The Pro plan includes a cap at 10
- developers, extra developers do not need to be licensed. You can contact{' '}
- sales for a volume discount when licensing
- over 50 developers under the Premium plan.
+ The licenses are sold on a per-developer basis, using the software directly or
+ indirectly. The Pro plan includes a cap at 10 developers, extra developers do not need
+ to be licensed. You can contact sales for a
+ volume discount when licensing over 50 developers under the Premium plan.
@@ -78,9 +79,11 @@ export default function WhatToExpect() {
- With your purchase you are entitled to technical support (for MUI X components) and
- access to new versions for the duration of your subscription. You can{' '}
- learn more about support{' '}
+ With your purchase you receive support and access to new versions for the duration of
+ your subscription. You can{' '}
+
+ learn more about support
+ {' '}
in the docs. Note that, except for critical issues, e.g. security, we release bug
fixes, and other improvements on top of the latest version, instead of patching older
versions.