pricing link and SCU

Author: aimurphy

modules/developing/pages/astream-functions.adoc

@@ -12,7 +12,7 @@ Functions are implemented using https://pulsar.apache.org/docs/en/functions-over
 
 [IMPORTANT]
 ====
-Custom functions require a xref:operations:astream-pricing.adoc[paid {product} plan].
+Custom functions require a xref:operations:astream-pricing.adoc[paid {product-short} plan].
 
 Organizations on the *Free* plan can use xref:streaming-learning:functions:index.adoc[transform functions] only.
 ====
@@ -249,7 +249,7 @@ bin/pulsar-admin functions create --function-config-file **PATH_TO_FUNCTION_CONF
 ====
 A response of `Created Successfully!` indicates the function is deployed and ready to accept messages.
 
-If the response is `402 Payment Required` with `Reason: only qualified organizations can create functions`, then you must upgrade to a xref:operations:astream-pricing.adoc[paid {product} plan].
+If the response is `402 Payment Required` with `Reason: only qualified organizations can create functions`, then you must upgrade to a xref:operations:astream-pricing.adoc[paid {product-short} plan].
 Organizations on the *Free* plan can use xref:streaming-learning:functions:index.adoc[transform functions] only.
 ====
 +

modules/operations/pages/astream-limits.adoc

@@ -4,13 +4,13 @@
 {product} includes guardrails and limits to ensure best practices, foster availability, and promote optimal configurations for your databases.
 
 Unless otherwise noted, the following limits apply to shared clusters.
-In general, xref:operations:astream-pricing.adoc#dedicated-clusters[dedicated clusters] have more relaxed limits than shared clusters, and some limits can be changed by contacting {support_url}[{company} Support].
+In general, xref:operations:astream-pricing.adoc#dedicated-clusters[Streaming Capacity Units] have more relaxed limits than shared clusters, and some limits can be changed by contacting {support_url}[{company} Support].
 
 == {product} guardrails
 
 Guardrails are provisioned in the default settings for {product}.
 You can't directly change these guardrails.
-For dedicated clusters, some guardrails can be changed by contacting {support_url}[{company} Support].
+For Streaming Capacity Units, some guardrails can be changed by contacting {support_url}[{company} Support].
 
 [cols="1,1,1"]
 |===
@@ -19,7 +19,7 @@ For dedicated clusters, some guardrails can be changed by contacting {support_ur
 |Number of tenants per organization
 a|
 * Shared clusters: 10
-* Dedicated clusters: Unlimited
+* Streaming Capacity Units: Unlimited
 
 |This limit can't be changed for shared clusters.
 
@@ -30,32 +30,32 @@ a|
 |Number of topics per namespace
 a|
 * Shared clusters: 100
-* Dedicated clusters: 5000
+* Streaming Capacity Units: 5000
 |
 
 |Max message size
 a|
 * Shared clusters: 5MB
-* Dedicated clusters: Customizable
+* Streaming Capacity Units: Customizable
 |
 
 |Max throughput per topic for consumers
 a|
 * Shared clusters: 5000 messages per second, 25MB per second
-* Dedicated clusters: Customizable
+* Streaming Capacity Units: Customizable
 |This limit applies to non-partitioned topics and individual partitions of partitioned topics.
 
 |Max throughput per topic for producers
 a|
 * Shared clusters: 5000 messages per second, 25MB per second
-* Dedicated clusters: Customizable
+* Streaming Capacity Units: Customizable
 |This limit applies to non-partitioned topics and individual partitions of partitioned topics, regardless of the number of producers to a topic.
 If there are multiple producers to a topic, they can produce a _combined maximum_ of 5000 messages per second.
 
 |Max throughput per topic for subscriptions
 a|
 * Shared clusters: 5000 messages per second, 25MB per second
-* Dedicated clusters: Customizable
+* Streaming Capacity Units: Customizable
 |This limit applies to non-partitioned topics and individual partitions of partitioned topics, regardless of the number of subscribers to a topic.
 If there are multiple subscriptions to a topic, they can dispatch a _combined maximum_ of 5000 messages per second.
 
@@ -70,19 +70,19 @@ If there are multiple subscriptions to a topic, they can dispatch a _combined ma
 |Number of producers per topic
 a|
 * Shared clusters: 50
-* Dedicated clusters: 500
+* Streaming Capacity Units: 500
 |
 
 |Number of consumers per topic
 a|
 * Shared clusters: 50
-* Dedicated clusters: 500
+* Streaming Capacity Units: 500
 |
 
 |Number of subscriptions per topic
 a|
 * Shared clusters: 50
-* Dedicated clusters: 500
+* Streaming Capacity Units: 500
 |
 
 |Max unacknowledged messages per consumer
@@ -314,12 +314,12 @@ The default settings are as follows:
 |===
 |Cluster type |CPU per instance |RAM per instance |Maximum function instances per namespace
 
-|Shared
+|Shared clusters
 |0.25 core
 |500MB
 |Varies by plan
 
-|Dedicated
+|Streaming Capacity Units (dedicated clusters)
 |0.50 core
 |1GB
 |5000

modules/operations/pages/astream-pricing.adoc

@@ -3,43 +3,50 @@
 
 {product} is a fully-managed, software-as-a-service (SaaS) offering embedded in {astra-db}.
 
-{product} offers three subscription plans, as well as pricing for dedicated clusters.
-An {product} subscription is associated with an {astra-db} organization, but {product} subscription plans are separate from {astra-db} organization subscription plans.
+{product-short} offers three subscription plans with options for {product}, as well as pricing for Streaming Capacity Units.
+//An {product} subscription is associated with an {astra-db} organization, but {product} subscription plans are separate from {astra-db} organization subscription plans.
 
-For {product} plans and pricing details, see https://www.datastax.com/pricing/astra-streaming[{product} pricing].
-For information about {astra-db} plans, billing, and usage, see xref:astra-db-serverless:administration:subscription-plans.adoc[].
+For {product-short} plans and pricing details, see https://www.datastax.com/pricing?product=astra-db[{product-short} pricing] and xref:astra-db-serverless:administration:subscription-plans.adoc[].
 
-== {product} subscription plans
+== {product} availability by subscription plan
 
-{product} subscription plans include *Free*, *Pay As You Go*, and *Annual*.
+The availability of {product} features depends on your {product-short} subscription plan.
 
 The *Free* plan allows only one topic.
 It is meant for evaluation before upgrading to a paid plan.
 
-*Pay As You Go* and *Annual* plans realize the benefits of fully-managed SaaS offerings: You only pay for the resources you use to produce, process, and consume messages.
+*Pay As You Go* and *Enterprise* plans can realize the benefits of fully-managed SaaS offerings.
+You only pay for the resources you use to produce, process, and consume messages.
 These plans require a payment method on file.
-For metering details, see see https://www.datastax.com/pricing/astra-streaming[{product} pricing].
+For {product} metering details, contact your {company} account representative or {support_url}[{company} Support].
 
-By default, {product} plans use secure, shared {pulsar-reg} clusters.
+== Shared clusters
+
+By default, {product} uses secure, shared {pulsar-reg} clusters.
 Your data and interaction with {pulsar-short} are secured over a public internet connection.
-If desired, you can opt in to <<dedicated-clusters,dedicated clusters>>.
+If desired, you can opt in to <<dedicated-clusters,Streaming Capacity Units>>.
 
 [#dedicated-clusters]
-== Dedicated clusters
+== Streaming Capacity Units
+
+[TIP]
+====
+Streaming Capacity Units are also known as _dedicated clusters_.
+====
 
-If you prefer not to use shared clusters, you can opt for dedicated clusters.
+If you prefer not to use shared clusters, you can opt for Streaming Capacity Units.
 
-With dedicated clusters, you have your own private {pulsar-short} cluster with all the benefits of {product} as a managed service.
+With Streaming Capacity Units, you have your own private {pulsar-short} cluster with all the benefits of {product} as a managed service.
 You sign in to {astra-db} and use {product} in the same way that you would on shared clusters.
 When you create a tenant, you have the option to deploy to your private cluster.
-This means that you can use both shared or dedicated clusters, depending on your tenants' use cases.
+This means that you can use both shared clusters and Streaming Capacity Units, depending on your tenants' use cases.
 
-Dedicated clusters are an addition to your base {product} subscription plan, and billing for dedicated clusters is unique to each customer.
-For information about dedicated cluster pricing and metering, see https://www.datastax.com/astra-streaming-dedicated-clusters[{product} Dedicated Clusters pricing].
+Streaming Capacity Units are an addition to your base {product} subscription plan, and billing for Streaming Capacity Units is unique to each customer.
+For information about Streaming Capacity Unit pricing and metering, see https://www.datastax.com/astra-streaming-dedicated-clusters[{product-short} Streaming Capacity Units pricing].
 
-Like shared clusters, all connections for dedicated clusters in {product} are guarded by authentication, authorization, and secure (TLS) communications.
+Like shared clusters, all connections for Streaming Capacity Units in {product} are guarded by authentication, authorization, and secure (TLS) communications.
 By default, these connections are over the public internet.
-Additionally, dedicated clusters support xref:operations:private-connectivity.adoc[private connectivity].
+Additionally, Streaming Capacity Units support xref:operations:private-connectivity.adoc[private connectivity].
 
 == Additional billed charges
 
@@ -55,14 +62,14 @@ These include, but are not limited to, the following:
 
 Regardless of your subscription plan or cluster type, {product} applies xref:astream-limits.adoc[guardrails and limits] on resource creation to ensure best practices, foster availability, and promote optimal configurations for your databases.
 
-Dedicated clusters have fewer limits than shared clusters.
+Streaming Capacity Units have fewer limits than shared clusters.
 
 == Regions
 
 With shared clusters, you can create tenants in any of the xref:astream-regions.adoc[supported regions].
 
-Dedicated clusters are open to almost any public cloud region.
-For this reason, dedicated clusters offer more flexibility for xref:operations:astream-georeplication.adoc[geo-replication].
+Streaming Capacity Units are open to almost any public cloud region.
+For this reason, Streaming Capacity Units offer more flexibility for xref:operations:astream-georeplication.adoc[geo-replication].
 If your preferred region isn't already available, you can contact your {company} account representative or {support_url}[{company} Support] to request it.
 
 == See also

modules/operations/pages/astream-release-notes.adoc

@@ -63,7 +63,7 @@ For more information, see xref:developing:clients/spring-produce-consume.adoc[Sp
 
 === {new}
 
-* Custom functions require a xref:operations:astream-pricing.adoc[paid {product} plan].
+* Custom functions require a xref:operations:astream-pricing.adoc[paid {product-short} plan].
 Organizations on the *Free* plan can use xref:streaming-learning:functions:index.adoc[transform functions] only.
 
 == February 27, 2023

modules/operations/pages/onboarding-faq.adoc

@@ -15,19 +15,19 @@ In traditional cloud environments, you would pay hourly for every machine whethe
 
 A serverless environment removes those operational burdens, and you pay only for the resources you actually use.
 
-== What is the difference between shared and dedicated clusters for {product}?
+== What is the difference between shared clusters and Streaming Capacity Units for {product}?
 
 See xref:operations:astream-pricing.adoc[].
 
-== Are connections to shared clusters less secure than dedicated clusters?
+== Are connections to shared clusters less secure than Streaming Capacity Units?
 
 Connections to both cluster types are secure.
-However, dedicated clusters offer the option for private connectivity.
+However, Streaming Capacity Units offer the option for private connectivity.
 
-For dedicated {pulsar-short} clusters, all connections in {product} are guarded by authentication, authorization, and secure (TLS) communications.
+For Streaming Capacity Units, all connections in {product} are guarded by authentication, authorization, and secure (TLS) communications.
 You can connect over the public internet or xref:operations:private-connectivity.adoc[establish a private connection].
 
-Shared {pulsar-short} clusters also use a secure connection over the public internet.
+Shared clusters also use a secure connection over the public internet.
 However, shared clusters don't support private links.
 
 For more information, see xref:operations:astream-pricing.adoc[].
@@ -45,20 +45,20 @@ See xref:ROOT:astream-org-permissions.adoc[].
 
 See xref:operations:astream-token-gen.adoc[].
 
-== What are the differences in geo-replication for shared and dedicated clusters?
+== What are the differences in geo-replication for shared clusters and Streaming Capacity Units?
 
-Geo-replication is available for both shared and dedicated clusters.
+Geo-replication is available for both shared clusters and Streaming Capacity Units.
 Both cluster types can replicate to other clusters, but there are some differences:
 
 Connections::
 For shared clusters, traffic between clusters is secured over the public internet.
 +
-Dedicated clusters can use either the default secure public internet connection or enable private links.
+Streaming Capacity Units can use either the default secure public internet connection or enable private links.
 
 Regions::
 Shared clusters can replicate between any xref:astream-regions.adoc[supported region] of the same cloud provider.
 +
-Dedicated clusters can use almost any region supported by your cloud provider, as well as across cloud providers.
+Streaming Capacity Units can use almost any region supported by your cloud provider, as well as across cloud providers.
 
 For more on geo-replication, see xref:astream-georeplication.adoc[].
 

modules/operations/pages/private-connectivity.adoc

@@ -15,7 +15,7 @@ Be prepared to provide the <<credentials,credentials>> required for your cloud p
 
 The first inbound traffic pattern describes {pulsar-reg}, Apache Kafka(R), and RabbitMQ messaging traffic, as well as Prometheus metrics traffic, flowing from a user's private endpoint to {product}.
 
-You create a connection to the {company} private link service, and then {company} routes traffic to your {product} dedicated cluster.
+You create a connection to the {company} private link service, and then {company} routes traffic to your {product} Streaming Capacity Units.
 If you have multiple tenants, they can have different VPCs.
 Each VPC will have the same private FQDN with different VNETs.
 The traffic on separate private end point connections is isolated until it reaches the {company} load balancer.