-
Notifications
You must be signed in to change notification settings - Fork 124
NLB-7074: Update docs to add standardv3 plan for azure #1435
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview will be available once build job completes!
|
| */ | ||
| currencyFormatter: (n, significantDigits) => { | ||
| return new Intl.NumberFormat("en-US", { | ||
| currencyFormatter: (n, significantDigits = 5) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function should either return a formatted currency with either two digits (e.g. n is 4.1) or zero digits (e.g. n is 4).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated suggested changes
| ### Standard V3 plan | ||
|
|
||
| The Standard V3 plan is an upgraded, purpose-built solution for modern enterprises looking to simplify application traffic management and scale workloads effortlessly. This improved plan offers a [99.95% uptime SLA](https://www.f5.com/pdf/customer-support/eusa-sla.pdf), high availability through active-active deployments, redundancy, lossless rolling upgrades, and dynamic autoscaling capabilities to optimize both performance and cost. | ||
|
|
||
| The Standard V3 plan introduces dynamic autoscaling that ensures consumption pricing - customers pay only for what they use. Each NGINX Capacity Unit (NCU) delivers 2.2 Mbps bandwidth and 3,000 connections, providing unmatched flexibility and scalability to suit diverse workloads. | ||
|
|
||
| The Standard V3 pricing model is designed to optimize efficiency and transparency: customers benefit from an affordable fixed price per deployment ($0.25/hour) that covers baseline overhead, while NCU usage ($0.008/hour/unit) and data processing ($0.005/GB) allow costs to scale precisely with demand. NGINXaaS is a consumption-based service, metered hourly, and billed monthly in NGINX Capacity Units (NCUs). | ||
|
|
||
| The SKU for the Standard V3 pricing plan is `standardv3_Monthly`. | ||
|
|
||
| The Standard V3 plan allows for optional Web Application Firewall (WAF) configuration and a higher number of listen ports, offering enhanced security and connectivity options for enterprise applications. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lets run this by Sundar and check if he is okay with this description. I would rephrase this to make it more human written.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took this description from this confluence doc. I will check with sundar on this.
|
Proposal looks good to me |
| * Total: `40 NCU·hour * $0.03/NCU/hour = $1.20`. | ||
| * Fixed deployment cost: `2 hours * $0.25/hour = $0.50` | ||
| * NCU usage cost: `40 NCU·hour * $0.008/NCU/hour = $0.32` | ||
| * Data processing cost: `1 GB * $0.0096/GB = $0.005` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The math looks wrong for data processing cost, or I don't quite understand it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I forgot replacing $0.0096 with $0.005.
The correct value updated is : Data processing cost: 1 GB * $0.005/GB = $0.005``
|
I couldn't get the calculator to work. Should I be able to in preview? |
Yes, in preview mode calculator doesn't work. I confirmed from docs team too but it works well in prod. The only way to look at it is in local for now. |
|
|
||
| The Standard V3 pricing model is designed to optimize efficiency and transparency: customers benefit from an affordable fixed price per deployment ($0.25/hour) that covers baseline overhead, while NCU usage ($0.008/hour/unit) and data processing ($0.005/GB) allow costs to scale precisely with demand. NGINXaaS is a consumption-based service, metered hourly, and billed monthly in NGINX Capacity Units (NCUs). | ||
|
|
||
| The SKU for the Standard V3 pricing plan is `standardv3_Monthly`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move this to the bottom
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean to the bottom of the page? Since this info is related to standardv3 plan, I added it under
Standard V3 plan heading
| ## December 13, 2025 | ||
|
|
||
| {{< icon-warning >}} **Standard V2 plan retirement**<a name="standard-plan-v2-retirement"></a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets rename title to "Standard V3 Plan", we'll announce standard v2 retirement at a later date.
|
|
||
| To review older entries, visit the [Changelog archive]({{< ref "/nginxaas-azure/changelog/archive" >}}) section. | ||
|
|
||
| ## December 13, 2025 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: update to 15 December
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated to 15 December
|
|
||
| {{< icon-warning >}} **Standard V2 plan retirement**<a name="standard-plan-v2-retirement"></a> | ||
|
|
||
| NGINXaaS for Azure now supports the [Standard V3]({{< ref "/nginxaas-azure/billing/overview/#standardv3-plan" >}}) plan. We encourage you to use the Standard V3 plan for all new NGINXaaS deployments to take advantage of modern features like F5 WAF for NGINX and additional listen ports. The Standard V3 plan introduces an efficient and transparent pricing model: $0.25/hour fixed per deployment, $0.008/hour per NGINX Capacity Unit (NCU), and $0.005/GB for data processing. This allows costs to scale precisely with demand. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should leave out pricing info in the changelog, it's a complicated topic and the exact $ amount depends on the tier
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed the pricing info from the changelog
| - **Recommended action:** | ||
|
|
||
| Update your automation scripts to use the Standard V3 plan. The SKU for the Standard V3 pricing plan is `standardv3_Monthly`. | ||
|
|
||
| If you have any questions or concerns, please [contact us](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview). | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove, the changelog should be a brief summary with a link to the page containing more information. Let's add a link to the standardv3 billing overview section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added link to the standardv3 billing overview section
| {{< icon-warning >}} **Standard V2 plan retirement**<a name="standard-plan-v2-retirement"></a> | ||
|
|
||
| NGINXaaS for Azure now supports the [Standard V3]({{< ref "/nginxaas-azure/billing/overview/#standardv3-plan" >}}) plan. We encourage you to use the Standard V3 plan for all new NGINXaaS deployments to take advantage of modern features like F5 WAF for NGINX and additional listen ports. The Standard V3 plan introduces an efficient and transparent pricing model: $0.25/hour fixed per deployment, $0.008/hour per NGINX Capacity Unit (NCU), and $0.005/GB for data processing. This allows costs to scale precisely with demand. | ||
| {{< call-out "important" >}}The Standard V2 plan will be deprecated and will not be available for new deployments starting January 1, 2026.{{< /call-out >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't know the date for Standardv2 retirement yet so let's leave this out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed the callout related to the standardv2 plan retirement
|
|
||
| F5 NGINXaaS for Azure (NGINXaaS) provides two pricing plans. | ||
|
|
||
| ### Standard V3 plan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to also add the Developer plan. Instead of creating a separate entry for developer. I would just replace basic with developer everywhere.
Proposed changes
standardv3as default plan instead ofstandardv2in NginxaaS Azure.standardv3planstandardv3plan.Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩