Document and announce the "used by" feature for Private Registry components (#16332)

* Fixes: pulumi/pulumi-service#33383
Fixes: pulumi/pulumi-service#33384

Document and announce component usage tracking feature

Adds documentation for the component usage tracking feature in the
private registry and a blog post announcing its availability.

The usage tracking feature shows which stacks are using components
from the private registry, including version information and last
update timestamps. This helps platform teams understand component
adoption and plan updates.

Changes:
- Add usage tracking section to private registry documentation
- Create blog post announcing the feature

* latest

* date fix

* Update title for IDP component usage tracking post

---------

Co-authored-by: Mark <[email protected]>

Author: fnune

content/blog/idp-component-usage-tracking/idp-component-used-by.png

@@ -0,0 +1,56 @@
+---
+title: "Component Usage Tracking in Pulumi Private Registry"
+date: 2025-10-28
+draft: false
+meta_desc: "Track which stacks use components from your private registry to understand version sprawl, plan deprecations, and respond to security issues."
+meta_image: meta.png
+authors:
+    - idp-team
+tags:
+    - idp
+    - features
+    - platform-engineering
+---
+
+Platform teams publishing components to the Pulumi Private Registry can now see exactly which stacks are using each component and at which version.
+<!--more-->
+
+## The visibility problem
+
+You've published a new major version of a component to your private registry. Most teams across your organization have adopted it. Then you need to answer a critical question: "Which teams still haven't adopted it?"
+
+This visibility gap creates real consequences. When a security vulnerability appears in an old version, you can't assess the blast radius. When you want to deprecate a version, you don't know which teams need to migrate. When you release a new feature, you can't measure adoption. Version sprawl accumulates silently.
+
+## Centralized components, centralized visibility
+
+The Pulumi IDP registry solves this by providing both centralized distribution and centralized insight. When you publish a component to the registry, you automatically gain visibility into its usage across your organization.
+
+The new usage tracking feature shows:
+
+- Which stacks are using your component
+- What version each stack is running
+- When each stack was last updated
+
+![Component usage tracking in the Pulumi IDP registry](idp-component-used-by.png)
+
+Access usage data through the "Used By" tab on any component's detail page in the registry. The view respects your existing access controls, showing only stacks you have permission to see.
+
+## Why this matters
+
+This visibility transforms conversations that were previously not possible or painfully slow.
+
+**Security response:** When a vulnerability is discovered in version 1.2.0 of your component, you can immediately identify every affected stack and reach out to the right teams. What used to take hours or days of detective work now takes minutes.
+
+**Deprecation planning:** Before removing support for version 1.x, you can see exactly which teams are still using it and coordinate migration timelines with complete information.
+
+**Version sprawl management:** See the full distribution of versions in use across your organization and make informed decisions about consolidation.
+
+The registry becomes your source of truth, not just for distributing components, but for understanding how they're used.
+
+## Get started
+
+If you're already publishing components to the Pulumi IDP registry, usage tracking is automatically available. Visit any component detail page to see the "Used By" tab.
+
+If you haven't published to the registry yet, now is the time to start. Publishing a component is as simple as running `pulumi publish`.
+
+For more information, see the [private registry documentation](/docs/idp/get-started/private-registry/).

content/blog/idp-component-usage-tracking/index.md

@@ -138,6 +138,18 @@ func (f *PetAbstractedOutputs) Annotate(a infer.Annotator) {
 
 {{< /chooser >}}
 
+#### Component usage tracking
+
+Each component in the private registry includes a usage tab that shows which stacks are using that component. This helps platform teams understand component adoption and assess the impact of changes before updating versions.
+
+The usage tab displays:
+
+- Stack name and project
+- Component version in use
+- Last update timestamp
+
+This information helps you identify stacks that may need updating when releasing new component versions and provides visibility into which teams are adopting standardized components.
+
 #### Specifying an Organization
 
 If you're part of multiple organizations and do not have a [default organization](/docs/iac/cli/commands/pulumi_org_set-default/) set, you must specify the org by using the `--publisher` flag.