From 9b519588c31e17cf69bfcc4e935452f84259f280 Mon Sep 17 00:00:00 2001 From: workprentice <257153108+workprentice@users.noreply.github.com> Date: Sat, 22 Aug 2026 00:17:51 +0000 Subject: [PATCH 1/2] Improve CTR and internal linking for 'agentic infrastructure' query - Rewrite the-agentic-infrastructure-era meta_desc to lead with the answer-first definition (was reading as a dated launch announcement, suppressing CTR at position ~6.7 for the query 'agentic infrastructure') - Add an early orientation link from that post to the definitional what-is/what-is-agentic-infrastructure page - Add exact-phrase internal links from two more blog posts that already use the bare phrase 'agentic infrastructure' in prose - Split a what-is-agentic-infrastructure.md FAQ section so its comparison table sits under a non-question sub-heading, preventing raw markdown table syntax from leaking into the rendered FAQPage acceptedAnswer text (verified via isolated Hugo schema harness: 19 clean FAQ entities, zero leaked '|'/'#'/code-fence characters) --- .../index.md | 2 +- content/blog/the-agentic-infrastructure-era/index.md | 4 +++- content/blog/why-choose-pulumi-over-terraform/index.md | 2 +- content/what-is/what-is-agentic-infrastructure.md | 6 +++--- 4 files changed, 8 insertions(+), 6 deletions(-) diff --git a/content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md b/content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md index 79bf5e545f48..cccf7c253fc2 100644 --- a/content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md +++ b/content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md @@ -39,7 +39,7 @@ social: Here's what shipped today. --- -At Pulumi, we are building the platform for agentic infrastructure. Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in this new era. While we are seeing extraordinary adoption — over 40% of our users now manage infrastructure using AI agents — we know many organizations are at different phases in their AI journey and have to balance building for the future with maintaining their existing infrastructure as code (IaC) solutions like Terraform. +At Pulumi, we are building the platform for [agentic infrastructure](/what-is/what-is-agentic-infrastructure/). Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in this new era. While we are seeing extraordinary adoption — over 40% of our users now manage infrastructure using AI agents — we know many organizations are at different phases in their AI journey and have to balance building for the future with maintaining their existing infrastructure as code (IaC) solutions like Terraform. Today, [we are launching](/releases/terraform-state-backend-modules-hcl/) three ways that Pulumi lets you avoid trading off building for the future against building for today. You don't have to rip out Terraform to enter the agentic era. Pulumi Cloud brings agentic infrastructure to the IaC estate you already have. diff --git a/content/blog/the-agentic-infrastructure-era/index.md b/content/blog/the-agentic-infrastructure-era/index.md index 970c17b52b73..47b706ba94d2 100644 --- a/content/blog/the-agentic-infrastructure-era/index.md +++ b/content/blog/the-agentic-infrastructure-era/index.md @@ -2,7 +2,7 @@ title: "The Agentic Infrastructure Era" date: 2026-05-19T03:00:00-07:00 draft: false -meta_desc: "Why infrastructure as code is the natural substrate for AI agents, and what we're shipping today to make agentic infrastructure even better." +meta_desc: "Agentic infrastructure is cloud infrastructure that AI agents provision, govern, and operate through code. See what Pulumi is building to make it real." feature_image: feature.png authors: - joe-duffy @@ -28,6 +28,8 @@ But as the AI tsunami whips up reams of code, what happens to it becomes just as +New to the term? Start with [what agentic infrastructure is](/what-is/what-is-agentic-infrastructure/) and how it works. + [See Pulumi Neo in action →](/product/neo/) Neo is the agent at the center of everything below: it previews changes, checks them against policy, and opens PRs for your review. ## LLMs are natural coders diff --git a/content/blog/why-choose-pulumi-over-terraform/index.md b/content/blog/why-choose-pulumi-over-terraform/index.md index 359053f6b691..5f93ad819beb 100644 --- a/content/blog/why-choose-pulumi-over-terraform/index.md +++ b/content/blog/why-choose-pulumi-over-terraform/index.md @@ -241,7 +241,7 @@ You also don't have to do it alone. Pulumi provides [self-serve conversion tools ## Manage Terraform state in Pulumi Cloud -You don't have to rewrite anything to start getting value from Pulumi. Pulumi Cloud can serve as a Terraform state backend, letting you store and manage Terraform state alongside your Pulumi stacks. Your team can keep using the Terraform or OpenTofu CLI for day-to-day operations while gaining encrypted state storage, update history, state locking, role-based access control, audit policies, and unified resource visibility through Pulumi Insights — with agentic infrastructure coding through Neo on top. +You don't have to rewrite anything to start getting value from Pulumi. Pulumi Cloud can serve as a Terraform state backend, letting you store and manage Terraform state alongside your Pulumi stacks. Your team can keep using the Terraform or OpenTofu CLI for day-to-day operations while gaining encrypted state storage, update history, state locking, role-based access control, audit policies, and unified resource visibility through Pulumi Insights — with [agentic infrastructure](/what-is/what-is-agentic-infrastructure/) coding through Neo on top. It uses Terraform's standard remote backend, so you point the CLI at Pulumi Cloud without changing your infrastructure code: diff --git a/content/what-is/what-is-agentic-infrastructure.md b/content/what-is/what-is-agentic-infrastructure.md index 09dc8ef94d52..9202728c7645 100644 --- a/content/what-is/what-is-agentic-infrastructure.md +++ b/content/what-is/what-is-agentic-infrastructure.md @@ -84,9 +84,9 @@ What makes this different from a generic coding assistant is that Neo is [ground ## What about infrastructure for AI agents? -The phrase "agentic infrastructure" is also used to describe a second thing: the compute, networking, and data infrastructure that AI agents themselves run on. GPU clusters, inference endpoints, vector databases, and RAG pipelines: the platform underneath AI workloads. +The phrase "agentic infrastructure" is also used to describe a second thing: the compute, networking, and data infrastructure that AI agents themselves run on. GPU clusters, inference endpoints, vector databases, and RAG pipelines: the platform underneath AI workloads. That is related to, but distinct from, this page's subject, which is infrastructure *managed by* AI agents. Most organizations need to think about both, and the two compound: agents that understand infrastructure can also manage the infrastructure their own workloads run on. -These two meanings are related but distinct: +### The two meanings compared | | Infrastructure *managed by* AI agents | Infrastructure *for* AI agents | |---|---|---| @@ -94,7 +94,7 @@ These two meanings are related but distinct: | **Example** | Neo provisions and updates your AWS environment | A GPU cluster running a training job or inference service | | **Who manages it** | The AI agent, with human review | Your platform team, often using IaC | -Most organizations will need to think about both. Teams building AI products need the platform layer (infrastructure *for* agents). Those same teams also benefit from AI agents operating that platform (infrastructure *managed by* agents). The two compound: agents that understand infrastructure can also manage the infrastructure their own workloads run on. +Teams building AI products need the platform layer (infrastructure *for* agents). Those same teams also benefit from AI agents operating that platform (infrastructure *managed by* agents). ## How do you govern and secure agentic infrastructure? From 78a291c34128f52747813051db29a1ac2c719da2 Mon Sep 17 00:00:00 2001 From: workprentice <257153108+workprentice@users.noreply.github.com> Date: Sat, 22 Aug 2026 00:28:11 +0000 Subject: [PATCH 2/2] Address pre-merge review nit: restore build-to-conclusion order in the two-meanings section Move the compounding/conclusion sentence to close the section after the comparison table instead of before it, per the pre-merge review's non-blocking readability note. No schema impact: the table remains under the non-question '### The two meanings compared' sub-heading. --- content/what-is/what-is-agentic-infrastructure.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/what-is/what-is-agentic-infrastructure.md b/content/what-is/what-is-agentic-infrastructure.md index 9202728c7645..36ba5288117f 100644 --- a/content/what-is/what-is-agentic-infrastructure.md +++ b/content/what-is/what-is-agentic-infrastructure.md @@ -84,7 +84,7 @@ What makes this different from a generic coding assistant is that Neo is [ground ## What about infrastructure for AI agents? -The phrase "agentic infrastructure" is also used to describe a second thing: the compute, networking, and data infrastructure that AI agents themselves run on. GPU clusters, inference endpoints, vector databases, and RAG pipelines: the platform underneath AI workloads. That is related to, but distinct from, this page's subject, which is infrastructure *managed by* AI agents. Most organizations need to think about both, and the two compound: agents that understand infrastructure can also manage the infrastructure their own workloads run on. +The phrase "agentic infrastructure" is also used to describe a second thing: the compute, networking, and data infrastructure that AI agents themselves run on. GPU clusters, inference endpoints, vector databases, and RAG pipelines: the platform underneath AI workloads. That is related to, but distinct from, this page's subject, which is infrastructure *managed by* AI agents. ### The two meanings compared @@ -94,7 +94,7 @@ The phrase "agentic infrastructure" is also used to describe a second thing: the | **Example** | Neo provisions and updates your AWS environment | A GPU cluster running a training job or inference service | | **Who manages it** | The AI agent, with human review | Your platform team, often using IaC | -Teams building AI products need the platform layer (infrastructure *for* agents). Those same teams also benefit from AI agents operating that platform (infrastructure *managed by* agents). +Most organizations need to think about both. Teams building AI products need the platform layer (infrastructure *for* agents), and those same teams also benefit from AI agents operating that platform (infrastructure *managed by* agents). The two compound: agents that understand infrastructure can also manage the infrastructure their own workloads run on. ## How do you govern and secure agentic infrastructure?