# pulumi-neo

Pulumi Neo is an AI infrastructure agent that automates, governs, and optimizes cloud infrastructure tasks.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Introducing Pulumi Agents

DevFeed: [Introducing Pulumi Agents](<https://devfeed.tech/articles/introducing-pulumi-agents-140949.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/introducing-pulumi-agents/>)

Author: Pulumi AI Team

Published: 2026-11-18T12:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-infrastructure](<https://devfeed.tech/tags/agentic-infrastructure.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [code](<https://devfeed.tech/tags/code.md>), [confluence](<https://devfeed.tech/tags/confluence.md>), [context](<https://devfeed.tech/tags/context.md>), [data](<https://devfeed.tech/tags/data.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [decision](<https://devfeed.tech/tags/decision.md>), [define](<https://devfeed.tech/tags/define.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [diagnosis](<https://devfeed.tech/tags/diagnosis.md>), [product](<https://devfeed.tech/tags/product.md>), [product-launches](<https://devfeed.tech/tags/product-launches.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>)

### AI overview

Pulumi Agents run in Pulumi Cloud to investigate incidents, plan infrastructure changes, and perform maintenance, then prepare findings or pull requests for team review. They combine infrastructure code, resource state, update history, and authorized connected sources; for incident work, they can consult runbooks, query logs and metrics, and use Pulumi's Context API to examine resource and stack dependencies. Tasks can be started manually, by events such as drift or failed updates, through integrations for Datadog, Honeycomb, and PagerDuty, via webhooks, or on a schedule. Agent instructions, integrations, and roles can be defined in code and reviewed before changes apply. Each agent has its own Pulumi Cloud role; connected-system credentials separately govern access, and task requests must be permitted for both the teammate and the agent. In Pulumi Delivery pipelines, agents can assess proposed changes against defined risk criteria and return structured results that pipeline rules use to require human approval. Teams can configure agents using a coding agent or the Pulumi Cloud console.

### Source excerpt

It's hard to overstate how much AI agents have changed the way we make software. When it comes to managing your cloud infrastructure, though, we're still very much in the early days. This is why we're excited to announce Pulumi Agents, your agentic infrastructure team. Pulumi Agents are digital teammates that assist with incident investigation, program and resource planning, or proactive infrastructure maintenance. The user experience with Pulumi Agents will feel familiar to anyone who has used agents before: you define the goal or tasks an agent performs, the constraints it must respect, and its permissions. Pulumi then runs the agent in the cloud, where it works with your existing infrastructure and connected tools to prepare findings and pull requests for your team to review. Delegate infrastructure work To carry out a task, agents combine infrastructure code, recorded resource state, and update history with data from connected systems. They can retrieve the runbooks and engineering standards your team keeps in Confluence, Notion, or GitHub, through connections authorized to read them. During an incident, an agent can consult those runbooks, query logs and metrics, and use Pulumi's Context API to examine dependencies between resources and stacks as it prepares a diagnosis or proposed fix. Authorized teammates can collaborate with the agent on the same task through Pulumi Cloud or Slack. The agent can ask for information or a decision, and teammates can ask it to explain a finding or revise its proposal. Tasks can start on request, in response to events, or on a schedule. Pulumi includes trigger setup for Datadog monitor alerts, Honeycomb triggers, and PagerDuty incidents, plus generic webhooks for other systems. Pulumi events, such as detected drift or failed updates, can also start tasks, and schedules can kick off recurring work such as dependency reviews. Define each agent's responsibility and access You can define agents in code, keeping their instructions, i

## Running Pulumi Neo in a Docker Sandbox: workshop recap

DevFeed: [Running Pulumi Neo in a Docker Sandbox: workshop recap](<https://devfeed.tech/articles/running-pulumi-neo-in-a-docker-sandbox-workshop-recap-92883.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/running-pulumi-neo-in-a-docker-sandbox/>)

Author: Mike Coleman

Published: 2026-10-21T00:00:00Z

Content type: article

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [World models](<https://devfeed.tech/topics/world-models.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [community](<https://devfeed.tech/tags/community.md>), [data](<https://devfeed.tech/tags/data.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-sandbox](<https://devfeed.tech/tags/docker-sandbox.md>), [esc](<https://devfeed.tech/tags/esc.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [neo](<https://devfeed.tech/tags/neo.md>), [policy](<https://devfeed.tech/tags/policy.md>), [production](<https://devfeed.tech/tags/production.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [recap](<https://devfeed.tech/tags/recap.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>), [workshop](<https://devfeed.tech/tags/workshop.md>)

### AI overview

The workshop describes running Pulumi Neo in a Docker Sandbox with controls outside the agent's prompt. Neo runs in an isolated microVM with access limited to mounted files and permitted network hosts; a proxy injects the Pulumi token so Neo does not hold the real credential. Pulumi governs permissions and approvals: manual asks before each tool call, balanced before `pulumi up`, and auto never asks. Read-only blocks Pulumi Cloud writes but does not prevent access to ESC environments or their cloud accounts; role permissions must restrict environment access. Preventative Pulumi Policies can block violations, `protect: true` can stop deletion of protected resources, and ESC can issue short-lived AWS credentials, which limit leak damage but do not prevent it. Docker's network proxy can deny unapproved hosts, though allowed hosts still receive what Neo sends. The excerpt recommends starting with a locked-down network preset and balanced approvals near production. Centralized Docker sandbox controls are paid; local sandboxes and the `sbx` CLI are free. The final teardown demonstration was not completed.

### Source excerpt

The more an agent can do on its own, the more infrastructure work you can hand it, as long as its limits hold when it gets something wrong. In April, they didn't hold for PocketOS. A coding agent on a routine staging task deleted the company's production volume in 9 seconds. According to founder Jer Crane's account, it used an API token it found in an unrelated file. Its explanation afterward: "I guessed that deleting a staging volume via the API would be scoped to staging only. I didn't verify." Railway recovered the data two days later. The agent had been told not to. "System prompts are advisory, not enforcing," Crane wrote afterward. If the prompt can't stop an agent, the limits have to sit where the agent can't negotiate with them. That was the premise of Neo in a Docker Sandbox, the workshop Adam Gordon Bell and I ran with Mike Coleman from Docker. So we gave Pulumi Neo two layers. The first is a Docker Sandbox. Neo runs in its own microVM and reaches only the files and hosts we allow. The Pulumi token gets injected by a proxy on the way out, so Neo never holds the real credential. The second is Pulumi itself, which decides what Neo may change and when it has to ask. With both in place, you can let Neo work without approving every step. For why YOLO mode belongs in a sandbox at all, see my August post. Mike Coleman is a Principal Solutions Architect at Docker. His running joke is that agents "want to be helpful". It happens in his own demos: Mike Coleman I talk to people about agents a lot. They just really want to please you. I don't know how many times I've done a demo [of] governance for MCP servers, and I'll be like, "Can you write to my Notion page?" And there will be a policy applied to the sandbox that says it can't. But I have a connector enabled in Claude somewhere. And it's like, "Well, not with that MCP server, but I can use this thing over here to do it." Mike's answer is to close those doors before the agent finds them: Mike Coleman The more you c

## Self-driving infrastructure with Pulumi and Jev

DevFeed: [Self-driving infrastructure with Pulumi and Jev](<https://devfeed.tech/articles/self-driving-infrastructure-with-pulumi-and-jev-61357.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/self-driving-infrastructure-pulumi-jev/>)

Author: Peter Yoakum

Published: 2026-09-28T00:00:00Z

Content type: tutorial

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>)

Tags: [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [automation-api](<https://devfeed.tech/tags/automation-api.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [multi-cloud](<https://devfeed.tech/tags/multi-cloud.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

The article describes GeoDeploy, an example agentic workflow built with Pulumi and TypeSafe AI's Jev. It uses deployment inputs such as user locations, residency rules, container image, workload needs, provider constraints, and budget to choose cloud regions and provision infrastructure.

### Source excerpt

It's been a weirdly great time to be building software. We've never had so many tools that help us get things done: endless cloud providers, regions, deployment frameworks, and now AI agents that can actually build and manage infrastructure for us. That's part of what made this past week feel so big. TypeSafe AI opened early access to Jev, their SystemOne model, and we here at Pulumi were bitten by the excitement bug and got straight to work building. Almost immediately we were able to whip up some test agentic workflows that were making real, live decisions about infrastructure. If you're not familiar with TypeSafe's Jev, it comes with a powerful set of AI primitives that let your apps, agents, and workflows make decisions based on context. Jev's decision-making primitives are the perfect complement to agentic work. When you combine that reasoning power with Pulumi, the gap between dreaming up your ideal infrastructure and deploying it to production practically vanishes. In the past, having more choices usually meant dealing with more complexity, which added technical debt and inevitably meant someone (perhaps you) spent hours setting things up. Now you can let agents handle provisioning and the day-to-day scaling and reliability decisions while you stay focused on defining how your infrastructure should work. Okay, but how does it work? Our example, GeoDeploy, answers one question: my users are in these places and I have this container image, so where should it run and what will it cost? Then it builds the answer. You give it a deployment request with four parts: Target geos: where your users are, what share of traffic each place sends, and any data-residency rule (EU-only, US-only, or in-country). An image: a container image and the platforms it's built for (amd64, arm64, or both). A workload shape: replicas, CPU and memory per pod, egress, and storage. Constraints: which providers are allowed, how many providers you'll tolerate, and a budget. From there, GeoDepl

## How Pulumi Neo Uses Kopia Snapshots to Preserve Long-Running Agent Workspaces

DevFeed: [How Pulumi Neo Uses Kopia Snapshots to Preserve Long-Running Agent Workspaces](<https://devfeed.tech/articles/ai-agents-need-continuity-not-just-context-60167.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/neo-kopia-workspace-snapshots/>)

Author: Derek Schaller

Published: 2026-09-25T19:00:00Z

Content type: article

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Persistence](<https://devfeed.tech/topics/persistence.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Repository](<https://devfeed.tech/topics/repository.md>), [Git](<https://devfeed.tech/topics/git.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [git](<https://devfeed.tech/tags/git.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [persistence](<https://devfeed.tech/tags/persistence.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [repository](<https://devfeed.tech/tags/repository.md>)

### AI overview

Pulumi describes how Neo preserves hosted-runtime workspaces for long-running agent tasks. After finding Git-based recovery insufficient for generated files, dependencies, scratch output, and other workspace state, the team chose Kopia for encrypted, incremental, content-addressed snapshots stored in backends such as object storage.

### Source excerpt

Pulumi Neo works on infrastructure the way an engineer does: it clones repositories, edits files, installs dependencies, runs previews, and produces intermediate work along the way. A task is not only a conversation with a model. It is also a working directory that has to survive long enough for the agent to keep making progress. Imagine asking an agent to upgrade a Pulumi provider version across a repository, regenerate SDK code, run previews and tests, inspect the failures, and open a pull request. Halfway through, the runtime restarts. Conversation replay can recover what the agent said and which tools it called, but it does not recover the generated files, dependency state, local commits, or scratch output the next step may depend on. Without workspace continuity, the agent can wake up remembering the plan but missing the room it was working in. For early hosted Neo tasks, workspace recovery started with Git. We persisted enough information to reconstruct repositories later: remotes, branches, commits, and local diffs. This was about the hosted runtime workspace, not a user's local checkout when running pulumi neo, where local filesystem and shell tools execute on the user's machine. The Git-based approach worked for simple hosted-runtime cases, but it was the wrong abstraction for long-running agent work. We needed to recover the workspace Neo had actually used. This post walks through how we tackled workspace continuity for long-running agent tasks, what we learned along the way, and how the same techniques can help you build more resilient agentic systems of your own. The core primitive we chose was Kopia, an open source backup tool that creates encrypted, incremental, content-addressed snapshots and stores them in backends such as object storage. Git was the wrong recovery boundary The original persistence model was repository-oriented. After a turn, the hosted agent runtime scanned its own working directory for Git repositories, recorded each remote, branch

## Neo Security: Securing Infrastructure in the Agentic Era

DevFeed: [Neo Security: Securing Infrastructure in the Agentic Era](<https://devfeed.tech/articles/neo-security-securing-infrastructure-in-the-agentic-era-19024.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/pulumi-neo-security/>)

Author: Joe Duffy

Published: 2026-08-28T00:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Security](<https://devfeed.tech/topics/security.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Security research](<https://devfeed.tech/topics/security-research.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [attack-paths](<https://devfeed.tech/tags/attack-paths.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [code-analysis](<https://devfeed.tech/tags/code-analysis.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [large-language-models](<https://devfeed.tech/tags/large-language-models.md>), [logs](<https://devfeed.tech/tags/logs.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [neo-security](<https://devfeed.tech/tags/neo-security.md>), [product](<https://devfeed.tech/tags/product.md>), [production](<https://devfeed.tech/tags/production.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Pulumi Neo Security is a research-preview agent that assesses cloud infrastructure for exploitable flaws by analyzing a context graph of resources, dependencies, runtime information, and related cloud context. It first builds a threat model identifying critical assets, externally accessible resources, production data accounts, trust boundaries, and realistic attackers to estimate relative risk and blast radius. It then maps attack vectors, including internet entry points, federation and trust relationships, workload identity, and lateral movement between accounts. The excerpt says findings are intended to form an actionable security posture report and work with existing infrastructure regardless of how it was provisioned, across providers including AWS, Azure, Google Cloud, and Kubernetes. Pulumi says it is beginning with a research preview and will work closely with customers to run it and address findings. The excerpt cuts off during the attack-vector description, so it does not establish the complete three-pass process.

### Source excerpt

Recently, AI systems have started turning up exploitable flaws in code that survived decades of human review. The frontier labs have released useful tools to help uncover many of these flaws through agent-led static code analysis. This is a huge leap ahead, but cloud infrastructure has many exploitable flaws that code analysis alone cannot find. These flaws are often as severe as the ones in code, or worse, and they await discovery by malicious agents on offense. We realized recently we can uniquely help here. At Pulumi, we have complete visibility into your entire cloud estate: infrastructure resources, their semantics, connections and dependencies between them, runtime logs and information, and more -- and have built an entire context graph out of them that is accessible to agents. Thanks to large language models, the cost of analyzing that full context graph is no longer prohibitive. As a result, today we're opening a research preview of Pulumi Neo Security. Neo Security is an agent that can find exploitable flaws in your cloud infrastructure. It starts with a threat model of your cloud estate, and then works systematically through every potential point of attack. The result is a security posture report that is immediately actionable thanks to Pulumi's infrastructure as code technology. Neo Security works on your existing infrastructure regardless of how it was provisioned, across any of our thousands of cloud providers including AWS, Azure, Google Cloud, and Kubernetes. We're releasing it in research preview to begin, so we can work closely with customers to run and address any findings. If you'd like to give it a try, contact us. How it finds attack paths Neo Security's aim is to provide a high-confidence, actionable security posture report. It gets there in three passes. The first builds a threat model, before it looks for anything. It works out what your crown jewels are, which resources are accessible to outside actors, which accounts hold production data, wh

## Pulumi Context API: query your infrastructure as a graph

DevFeed: [Pulumi Context API: query your infrastructure as a graph](<https://devfeed.tech/articles/pulumi-context-api-query-your-infrastructure-as-a-graph-19022.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/pulumi-context-api/>)

Author: Levi Blackstone

Published: 2026-08-26T00:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi](<https://devfeed.tech/topics/pulumi.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [pulumi-cli](<https://devfeed.tech/topics/pulumi-cli.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cleanup](<https://devfeed.tech/tags/cleanup.md>), [cli](<https://devfeed.tech/tags/cli.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [features](<https://devfeed.tech/tags/features.md>), [graph](<https://devfeed.tech/tags/graph.md>), [iac](<https://devfeed.tech/tags/iac.md>), [impact](<https://devfeed.tech/tags/impact.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code-iac](<https://devfeed.tech/tags/infrastructure-as-code-iac.md>), [product](<https://devfeed.tech/tags/product.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [query](<https://devfeed.tech/tags/query.md>), [relationships](<https://devfeed.tech/tags/relationships.md>), [resources](<https://devfeed.tech/tags/resources.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

### AI overview

Pulumi's read-only Context API connects Pulumi-managed and discovered resources, stacks, and their relationships into a queryable infrastructure graph. JSON queries specify starting nodes, relationship traversals, and returned results; they can run through the Pulumi CLI or REST API. The excerpt illustrates finding resources managed by AWS provider instances below version 7.0.0 and describes impact, infrastructure coverage, and cleanup queries. Pulumi Neo uses the API with the invoking user's permissions; other agents that can run authenticated Pulumi CLI commands can retrieve its graph vocabulary and query guidance. Public preview is available to Enterprise and Business Critical organizations. The excerpt points to guidance for assessing answer completeness but does not include its details.

### Source excerpt

Every platform team fields the same questions: What is running? What breaks if we change this? What can we safely delete? The answers exist, but they're scattered across state files, cloud consoles, and the memories of whoever set things up. Today we're launching the Pulumi Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. It's designed agent-first: Pulumi Neo, our infrastructure agent, uses it out of the box, and other agents can fetch the current graph vocabulary and query guidance on demand. It's available in public preview for organizations on the Enterprise and Business Critical editions. Answers that follow infrastructure relationships Pulumi already records the resources your programs manage, their dependencies, how stacks consume each other's outputs, and the resources Pulumi Discovery finds outside infrastructure as code (IaC). The Context API connects this data so you can ask questions that depend on the relationships: Impact: Which stacks are affected if we upgrade this provider? If this stack changes, what consumes its outputs? Coverage: How much of our infrastructure lives outside IaC, and in which accounts? Cleanup: Which stacks have no dependents and are candidates for retirement? A query is a JSON document with a handful of clauses. anchor names the starting nodes, traverse follows relationships from there, and return chooses what comes back. You can run a query through the Pulumi CLI or REST API. Here's a selector that starts from AWS provider instances older than version 7.0.0 and follows incoming provided_by relationships back to the visible resources they manage: { "anchor": { "nodeType": "resource", "match": { "type": "pulumi:providers:aws", "fields": { "provider_version": { "op": "lt", "value": "7.0.0" } } } }, "traverse": [ { "edgeTypes": ["provided_by"], "direction": "in", "alias": "managed" } ], "return": { "select": ["anchor", "managed"] } } A response for one m

## Never Miss What Your Infrastructure Is Telling You

DevFeed: [Never Miss What Your Infrastructure Is Telling You](<https://devfeed.tech/articles/never-miss-what-your-infrastructure-is-telling-you-19017.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/notification-center/>)

Author: Tom King

Published: 2026-08-11T00:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [notifications](<https://devfeed.tech/topics/notifications.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [pulumi-cloud](<https://devfeed.tech/topics/pulumi-cloud.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [alert](<https://devfeed.tech/tags/alert.md>), [billing](<https://devfeed.tech/tags/billing.md>), [change](<https://devfeed.tech/tags/change.md>), [channel](<https://devfeed.tech/tags/channel.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [community](<https://devfeed.tech/tags/community.md>), [console](<https://devfeed.tech/tags/console.md>), [email](<https://devfeed.tech/tags/email.md>), [esc](<https://devfeed.tech/tags/esc.md>), [event](<https://devfeed.tech/tags/event.md>), [features](<https://devfeed.tech/tags/features.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [issue](<https://devfeed.tech/tags/issue.md>), [neo](<https://devfeed.tech/tags/neo.md>), [notification](<https://devfeed.tech/tags/notification.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [organization](<https://devfeed.tech/tags/organization.md>), [override](<https://devfeed.tech/tags/override.md>), [product](<https://devfeed.tech/tags/product.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>)

### AI overview

Pulumi Cloud's Notification Center provides a real-time inbox behind the console sidebar bell for events that need attention, with each notification linking directly to its action. Initial alerts cover Neo tasks paused for approval or completed, ESC change requests awaiting sign-off, and billing conditions such as a locked organization or an ending trial. Relevant organization members receive pending approval and billing alerts. Each notification type can be delivered in the console, by email, or both; organization admins set defaults, and individuals can override them in account settings. The service is available now, with more notification types planned.

### Source excerpt

Plenty happens in a Pulumi organization while you're looking somewhere else. Neo finishes a task you kicked off just before taking lunch. A teammate submits an ESC change request that needs your approval before it can land. Until now, catching any of that meant either keeping the right tab open or hoping the right email reached you. Today we're introducing the Notification Center: a single inbox in the Pulumi Cloud console for the things that actually need you. It lives behind the bell in the sidebar, with a dot when something's waiting. Notifications arrive in real time -- no refresh -- and each one carries exactly one action: Review request, View task, Update billing. Click it and you land on the page where you can do the thing, not on a dashboard where you have to go find it. What you'll hear about We've started with the moments where being a few minutes late actually costs you something: a Neo task that's paused waiting on your approval, a Neo task that's finished, an ESC change request waiting on your sign-off, and billing conditions like a locked organization or a trial that's about to end. Relevant people in your organization will be notified when there's a pending approval, or billing alert. Nobody gets paged for someone else's work. Where you'll hear about it Every notification type can be delivered two ways -- in the console and over email -- and you choose per type, per channel. Organization admins set a sensible baseline for everyone; each person can override it for themselves on their account settings page. What's next The Notification Center is available today. We're starting with this set of notifications and expanding from there. If there's an event you'd rather hear about from the bell than from a colleague on Slack, we'd like to know which one. Join our Community Slack to connect with the Pulumi team and other users, or open an issue on our GitHub repository.

## Migrate CloudFormation to Pulumi with Discovered Stacks

DevFeed: [Migrate CloudFormation to Pulumi with Discovered Stacks](<https://devfeed.tech/articles/migrate-cloudformation-to-pulumi-with-discovered-stacks-18996.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/discovered-stacks-migrate-cloudformation-to-pulumi/>)

Author: Alejandro Cotroneo

Published: 2026-07-30T00:00:00Z

Content type: tutorial

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [pulumi-cloud](<https://devfeed.tech/topics/pulumi-cloud.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [database](<https://devfeed.tech/tags/database.md>), [dynamodb](<https://devfeed.tech/tags/dynamodb.md>), [iam-roles](<https://devfeed.tech/tags/iam-roles.md>), [import](<https://devfeed.tech/tags/import.md>), [insights](<https://devfeed.tech/tags/insights.md>), [kinesis](<https://devfeed.tech/tags/kinesis.md>), [kms](<https://devfeed.tech/tags/kms.md>), [migration](<https://devfeed.tech/tags/migration.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [s3](<https://devfeed.tech/tags/s3.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>)

### AI overview

Pulumi Discovered Stacks tracks each CloudFormation resource's migration status and treats migration as complete when the code matches the cloud. The excerpt's AWS example has 61 resources: 54 are ready to import, 2 are mapped but not found by Discovery, and 5 have no exact Pulumi type. After scanning the AWS account, users can enable Show Discovered Stacks in Pulumi Cloud and review these statuses in the Migration tab. The tutorial starts migration with Pulumi Neo, but says the same flow can be done with another coding agent or by hand; progress is derived from stack state. The stated quality gate is a zero-diff pulumi preview. The excerpt does not provide the remaining migration steps.

### Source excerpt

With Discovered Stacks, Pulumi Cloud does the bookkeeping for a CloudFormation migration: every resource in the stack gets an explicit migration status, and the migration is done when the code provably matches the cloud. In this tutorial, we take one real CloudFormation stack from discovered to migrated and managed by Pulumi IaC, end to end. What we're migrating Our example is payments-api, a CloudFormation stack with 61 resources: a VPC, an Aurora ledger database behind an RDS Proxy, an assets S3 bucket, a DynamoDB ledger table, a Kinesis payment-events pipeline, and the IAM roles, KMS keys, and secrets that wire them together. The plan has five steps: Find the stack in Pulumi Cloud. Review the migration breakdown at a glance. Start the migration. Resolve the stragglers, so every resource is accounted for. Confirm the quality gate: a zero-diff pulumi preview. We'll use Pulumi Neo to do the heavy lifting, but nothing here depends on it. The same flow works with your own coding agent or entirely by hand, because migration status is derived from actual stack state -- however the work gets done, the console shows the same progress. Step 1: Find your stack in Pulumi Cloud Discovered Stacks builds on Discovery, so the only prerequisite is a scanned cloud account -- the AWS account holding your CloudFormation stacks. Once a scan has run, open the Stacks page and turn on Show Discovered Stacks. Your CloudFormation stacks appear alongside your Pulumi stacks. The project name comes from the CloudFormation stack (payments-api), and the stack name encodes the account and region it came from, so the same template deployed to two regions shows up as two distinct discovered stacks. Step 2: Plan the migration at a glance Open the discovered stack's Migration tab. It lays out all 61 resources of payments-api by status, so you can visualize the migration before touching anything: 54 Ready: mapped to a Pulumi type and confirmed to exist -- importable right now. 2 Not found: mapped, but

## Kubernetes Agent Sandbox: What It Is and How to Deploy It with Pulumi

DevFeed: [Kubernetes Agent Sandbox: What It Is and How to Deploy It with Pulumi](<https://devfeed.tech/articles/kubernetes-agent-sandbox-what-it-is-and-how-to-deploy-it-with-pulumi-19011.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/kubernetes-agent-sandbox/>)

Author: Adam Gordon Bell

Published: 2026-07-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [container](<https://devfeed.tech/topics/container.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [containers](<https://devfeed.tech/tags/containers.md>), [crd](<https://devfeed.tech/tags/crd.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [gcp](<https://devfeed.tech/tags/gcp.md>), [gke](<https://devfeed.tech/tags/gke.md>), [isolated-environment](<https://devfeed.tech/tags/isolated-environment.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-cluster](<https://devfeed.tech/tags/kubernetes-cluster.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [network](<https://devfeed.tech/tags/network.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [pod](<https://devfeed.tech/tags/pod.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [statefulset](<https://devfeed.tech/tags/statefulset.md>), [supply-chain-attack](<https://devfeed.tech/tags/supply-chain-attack.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>)

### AI overview

Kubernetes Agent Sandbox packages disposable, kernel-isolated environments for coding agents as a Sandbox custom resource, avoiding the need to assemble a size-one StatefulSet, headless Service, PersistentVolumeClaim, and lifecycle machinery yourself. It uses gVisor or Kata Containers for isolation; ordinary containers share the host kernel and are not a strong security barrier. The excerpt describes two uses: assigning each organization user's agent session its own pod and persistent volume, or letting an external agent harness create, suspend, and resume disposable task environments. It frames scoped files, credentials, and network access as ways to limit what an agent can affect. Although the title promises deployment on GKE with Pulumi, the supplied text contains no deployment instructions.

### Source excerpt

When you use a coding agent, it can seem like there's a trade-off between autonomy and permissions. If you approve every command, it's safe but slow. Let it do whatever it likes and it works more autonomously, but as the nx supply-chain attack showed, that can go badly. The fix is to give the agent a sandbox: a box it's allowed to wreck, with limited permissions and scoped network access. The only files are the checkout you handed it, the only credentials are the task's own, and trashing the machine just means a disposable pod gets garbage-collected early. Pulumi Neo works this way, and if you want to scale that pattern up inside your own organization, the Kubernetes project Agent Sandbox is a great path to building your own. This post is what it is and how to deploy it on GKE with Pulumi. What is Agent Sandbox? Agent Sandbox is a Kubernetes SIGs project that gives AI agents isolated, disposable environments as Kubernetes resources: a Sandbox custom resource, backed by gVisor or Kata Containers for kernel-level isolation. You could build Agent Sandbox yourself. You'd need gVisor support, a userspace kernel that sits between the agent's code and your host. With that in place, you could approximate a sandbox for every agent by stringing together a StatefulSet of size one, a headless Service, and a PersistentVolumeClaim, plus some lifecycle machinery to keep warm pools of nodes around. Agent Sandbox wraps all of that up as a CRD, so you can run a Kubernetes cluster where each sandbox is a disposable, kernel-isolated environment a coding agent runs in. apiVersion: agents.x-k8s.io/v1beta1 kind: Sandbox metadata: name: demo-sandbox spec: podTemplate: spec: runtimeClassName: gvisor containers: - name: agent image: ubuntu:24.04 # swap in your coding-agent image command: ["sleep", "infinity"] The Sandbox CRD, the whole idea in one manifest. There are two common patterns for using it. In the first, every coding agent session in the organization maps to its own pod with a pers

## Introducing Usage Limits for Pulumi Neo

DevFeed: [Introducing Usage Limits for Pulumi Neo](<https://devfeed.tech/articles/introducing-usage-limits-for-pulumi-neo-19016.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/neo-usage-limits/>)

Author: John Keiser

Published: 2026-07-14T15:00:00Z

Content type: tutorial

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [pulumi-cloud](<https://devfeed.tech/topics/pulumi-cloud.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [features](<https://devfeed.tech/tags/features.md>), [limits](<https://devfeed.tech/tags/limits.md>), [neo](<https://devfeed.tech/tags/neo.md>), [product](<https://devfeed.tech/tags/product.md>), [pulumi](<https://devfeed.tech/tags/pulumi.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>)

### AI overview

Pulumi Neo usage limits let paid-plan organizations cap monthly spending across all Neo usage. An Admin or Billing Manager can set the organization limit in Pulumi Cloud under Settings -> Billing & usage -> Neo token usage. Neo pauses for the rest of the billing period at the limit and resumes automatically next period; an Admin or Billing Manager can raise the limit to resume sooner. Because pausing occurs after the current task step, usage may exceed the cap by a few dollars. Optional per-member limits also apply, with each member paused at whichever is lower: their own limit or the organization limit. Billing admins can receive email alerts at 50%, 80%, 95%, and 100% of the organization limit.

### Source excerpt

Pulumi Neo is an AI agent that takes on real infrastructure work, and it's natural to want to hand it more and more. Usage limits give you control so you can do exactly that: set a monthly dollar limit, and Neo pauses when your organization reaches it. How usage limits work Your organization limit is a single monthly dollar amount covering all Neo usage across the org. To set one: In the Pulumi Cloud console, navigate to Settings -> Billing & usage -> Neo token usage. In the Manage token usage panel, enter an organization limit. Save your changes. When usage reaches the limit, Neo pauses for the rest of the billing period and resumes automatically at the start of the next one. An Admin or Billing Manager can raise the limit to resume before then. Enforcement happens at a natural boundary in Neo's work, so a task already in progress finishes its current step before pausing. As a result, usage can go a few dollars over the set limit. Per-member limits and alerts You can also set a separate limit for each member. A member is paused at whichever limit is smaller: their own or the organization's. For example, a member with a $200 limit under a $150 organization limit pauses at $150, because the organization limit is smaller. Turn on Enable email notifications to get a heads-up before you reach the limit. Billing admins are alerted at 50%, 80%, and 95% of the organization limit, with a final notice at 100% when Neo pauses. Get started Set your usage limits and stay in control as your organization hands Neo more and more work. Usage limits are available today for organizations on a paid plan, and an Admin or Billing Manager can set them. Sign in to Pulumi Cloud and set your first organization limit Read the Neo usage limits documentation for per-member limits, alerts, and enforcement details Join the Community Slack to share your feedback

## Neo code reviews: AI code review built for infrastructure

DevFeed: [Neo code reviews: AI code review built for infrastructure](<https://devfeed.tech/articles/neo-code-reviews-ai-code-review-built-for-infrastructure-19014.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/neo-code-reviews/>)

Author: Pulumi Neo Team

Published: 2026-06-22T15:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [pulumi](<https://devfeed.tech/topics/pulumi.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [pulumi-cloud](<https://devfeed.tech/topics/pulumi-cloud.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [also](<https://devfeed.tech/tags/also.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [features](<https://devfeed.tech/tags/features.md>), [github](<https://devfeed.tech/tags/github.md>), [governance](<https://devfeed.tech/tags/governance.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [logging](<https://devfeed.tech/tags/logging.md>), [neo](<https://devfeed.tech/tags/neo.md>), [product](<https://devfeed.tech/tags/product.md>), [public](<https://devfeed.tech/tags/public.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [rbac](<https://devfeed.tech/tags/rbac.md>)

### AI overview

Pulumi Neo code reviews use Pulumi Cloud's infrastructure state, preview output, and cloud context such as stack relationships and dependencies to provide high-level and code-level feedback on GitHub pull requests. Reviews can run automatically or when requested by mention; drafts and bot-opened pull requests are skipped by default. They appear as comments alongside required checks and branch protection and follow Neo's RBAC, guardrails, and audit logging. Public preview requires Neo enabled, the Pulumi GitHub App installed on target repositories, and a one-time GitHub access grant from each organization user. Reviews are free during preview; from July 1, 2026, they count toward Neo token usage at the standard per-token rate.

### Source excerpt

Today we're introducing Pulumi Neo code reviews, now in public preview. Neo code reviews analyze pull request changes in conjunction with what Pulumi Cloud knows about your running infrastructure, providing both high-level and code-level feedback. Normal code review agents can't reliably anticipate the impact an infrastructure-as-code change will have. This is because they don't have access to critical aspects of the IaC workflow: the potential impact the update will have, in this case the pulumi preview output; and the current state of the cloud infrastructure. Neo not only has access to both of those, but also to the entirety of your other cloud context, such as stack relationships and dependencies. Running reviews Neo can review every pull request automatically, or only when someone mentions @pulumi-neo. Either way, it skips draft pull requests and those opened by bots by default. A review is a comment, so it informs the person approving the merge and sits alongside the required checks and branch protection you already enforce. Neo code reviews run inside the same governance as every other Neo task, with the RBAC, guardrails, and audit logging your organization has set. Enable code reviews Neo code reviews are available on GitHub during public preview. They require Pulumi Neo to be enabled for your organization, the Pulumi GitHub App installed on the repositories you want reviewed, and a one-time grant from each organization user to access their GitHub account under Management > Version control. If Neo currently posts preview summaries on your pull requests, code reviews are already enabled, and they take the place of those summaries. Neo code reviews are free while in public preview. On July 1, 2026, they'll be generally available, and reviews will begin counting toward your organization's Neo token usage, at the same per-token rate as any other Neo task. The pricing page shows that rate and the monthly token allotment included with each plan. Give it a try Open

## Best AI Infrastructure Tools in 2026

DevFeed: [Best AI Infrastructure Tools in 2026](<https://devfeed.tech/articles/best-ai-infrastructure-tools-in-2026-18987.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/ai-infrastructure-tools/>)

Author: Alex Leventer

Published: 2026-05-25T00:00:00Z

Content type: article

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [AI Platform](<https://devfeed.tech/topics/ai-platform.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-platforms](<https://devfeed.tech/tags/agentic-platforms.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [automation](<https://devfeed.tech/tags/automation.md>), [coreweave](<https://devfeed.tech/tags/coreweave.md>), [crossplane](<https://devfeed.tech/tags/crossplane.md>), [devops](<https://devfeed.tech/tags/devops.md>), [env-zero](<https://devfeed.tech/tags/env-zero.md>), [firefly](<https://devfeed.tech/tags/firefly.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [gemini-enterprise-agent-platform](<https://devfeed.tech/tags/gemini-enterprise-agent-platform.md>), [general](<https://devfeed.tech/tags/general.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-compute](<https://devfeed.tech/tags/gpu-compute.md>), [hyperscaler](<https://devfeed.tech/tags/hyperscaler.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The excerpt divides AI infrastructure tools into two markets: infrastructure for AI, such as GPU compute and MLOps, and AI that manages infrastructure. It names CoreWeave, Lambda Labs and Modal for GPU compute; Weights & Biases and MLflow for ML lifecycle work; and hyperscaler AI platforms. For infrastructure management, it lists Pulumi Neo, Firefly, env zero, Spacelift Intelligence, Crossplane with Upbound, hyperscaler agents, code assistants and AWS Infrastructure Composer. Its quick picks call Pulumi Neo an enterprise compliance option because it executes changes, includes policy packs for CIS, HITRUST, NIST and PCI DSS, and supports Terraform, CloudFormation and manually created resources. It describes CoreWeave as purpose-built for AI workloads and generally cheaper than hyperscalers, and Modal as Python-function-based serverless GPU compute billed by the second. The excerpt ends during the MLflow recommendation, so further comparisons and conclusions are unavailable.

### Source excerpt

"AI infrastructure tools" covers two distinct markets: infrastructure for AI (GPU clouds like CoreWeave, MLOps platforms like Weights & Biases) and AI for infrastructure (agentic platforms like Pulumi Neo that generate, deploy, and govern cloud resources for you). Most teams need tools from both categories, and picking the wrong one wastes budget and adoption goodwill. The pressure to get this right is real. McKinsey research puts the productivity lift from generative AI in software development at 20-45%, which is great for application teams and a problem for platform teams trying to keep up with the resulting feature flow. Infrastructure investment is climbing on both fronts: more spend on the compute that trains and serves models, more spend on AI tools that manage everything else. This guide covers both categories: the compute and MLOps stack in Part 1, and AI-powered infrastructure management in Part 2, where the more interesting product shift is happening. AI infrastructure tools overview Tools for building AI infrastructure CoreWeave: GPU cloud built for AI workloads Lambda Labs: straightforward GPU cloud for research and startups Modal: serverless GPU compute Weights & Biases: ML experiment tracking and model management MLflow: open-source ML lifecycle platform Hyperscaler AI platforms: AWS SageMaker, Google's Gemini Enterprise Agent Platform, Azure ML AI-powered infrastructure management tools Pulumi Neo: infrastructure agent with policy automation Firefly: asset codification with an emerging agent layer env zero: multi-IaC insights, now with an agent CLI Spacelift Intelligence: conversational Q&A and natural-language provisioning Crossplane with Upbound: Kubernetes-native infrastructure Hyperscaler infrastructure agents: Azure SRE Agent, Gemini Cloud Assist General-purpose code assistants: Copilot, Claude Code, Cursor, Gemini AWS Infrastructure Composer: visual builder for CloudFormation templates Quick picks If you only have two minutes: Enterprise complia

## Bringing Neo to GitHub and Slack

DevFeed: [Bringing Neo to GitHub and Slack](<https://devfeed.tech/articles/bringing-neo-to-github-and-slack-19015.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/neo-github-slack/>)

Author: Pulumi Neo Team

Published: 2026-05-21T15:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [features](<https://devfeed.tech/tags/features.md>), [github](<https://devfeed.tech/tags/github.md>), [product](<https://devfeed.tech/tags/product.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [pulumi-cloud](<https://devfeed.tech/tags/pulumi-cloud.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [slack](<https://devfeed.tech/tags/slack.md>)

### AI overview

Pulumi Neo is now available in GitHub and Slack, extending its existing Pulumi Cloud console and terminal capabilities into team discussion threads. Users can ask Neo to inspect stack state, explain changes, investigate failures, and perform approved actions, with responses and follow-up work recorded in the relevant thread.

### Source excerpt

This week, Pulumi Neo started working in two more places: GitHub and Slack. The agent that already runs Pulumi tasks from the Cloud console and the terminal now participates in the threads where your team discusses changes. Mention @pulumi-neo in a pull request or issue and Neo replies in the thread. Mention @Neo in a Slack channel and Neo starts a task, continuing the conversation as you reply. Neo in GitHub Mention @pulumi-neo in a pull request description, a top-level or inline review comment, or an issue. Neo sees the diff, the stacks linked to the repository, and their current state. Reviewers can ask Neo to walk through what a proposed change does, including resources that change in stacks the PR doesn't touch directly. Responses land in the same thread, so the analysis becomes part of the review record and any follow-up stays with it. Neo in Slack Mention @Neo in any channel where Neo has been added, and Neo starts a task in the thread. The reply lands in the same thread, and follow-up messages continue the conversation there. The rest of the channel can see what was asked and what Neo found. Neo has the same capabilities here as in the Pulumi Cloud console or the terminal: check stack state, investigate failures, walk through what a change will do, or carry out actions the team has approved. Integrations in action A teammate posts in #platform-engineering: "API latency p95 has been climbing for two days, nobody can figure out why." You reply: You: @Neo check the production API stack. Anything change in the last 72 hours? Neo starts a task in the thread, walks the stack history, and finds a configuration change to the load balancer's idle-timeout setting that landed Friday afternoon. It posts the change, who deployed it, and when. The rest of the channel sees the finding without you having to retell it. You: @Neo open a PR to revert idle-timeout to the previous value. Neo edits the stack's Pulumi program, runs pulumi preview to confirm the change touches only

## Neo Automations: Scheduled Tasks Shipped as Pull Requests

DevFeed: [Neo Automations: Scheduled Tasks Shipped as Pull Requests](<https://devfeed.tech/articles/neo-automations-scheduled-tasks-shipped-as-pull-requests-19013.md>)

Original publisher: [Read original article](<https://www.pulumi.com/blog/neo-automations/>)

Author: Pulumi Neo Team

Published: 2026-05-21T14:00:00Z

Content type: release

Language: en

Sources: [Pulumi](<https://devfeed.tech/sources/pulumi.md>)

Topics: [pulumi-neo](<https://devfeed.tech/topics/pulumi-neo.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [also](<https://devfeed.tech/tags/also.md>), [am](<https://devfeed.tech/tags/am.md>), [apply](<https://devfeed.tech/tags/apply.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [backup](<https://devfeed.tech/tags/backup.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [but](<https://devfeed.tech/tags/but.md>), [cadence](<https://devfeed.tech/tags/cadence.md>), [can](<https://devfeed.tech/tags/can.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [context](<https://devfeed.tech/tags/context.md>), [custom](<https://devfeed.tech/tags/custom.md>), [features](<https://devfeed.tech/tags/features.md>), [neo](<https://devfeed.tech/tags/neo.md>), [product](<https://devfeed.tech/tags/product.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [pulumi-neo](<https://devfeed.tech/tags/pulumi-neo.md>), [scheduled](<https://devfeed.tech/tags/scheduled.md>), [scheduled-tasks](<https://devfeed.tech/tags/scheduled-tasks.md>), [tasks](<https://devfeed.tech/tags/tasks.md>)

### AI overview

Pulumi Neo can run user-defined tasks on hourly, daily, weekday, or weekly schedules and open pull requests for proposed changes. In the example, a weekly run checks AWS, GCP, and Kubernetes provider versions, updates providers more than two minor versions behind, runs a preview, and opens a PR for each clean result. Four built-in templates cover provider freshness, encryption, backups, and activity digests; automations can also be edited, run on demand, or paused. Runs default to automatic approval between steps and read-only permissions, so they can propose changes through PRs but cannot apply them directly; either setting can be overridden. Scheduled tasks use Neo's organization and project instructions and integrations, and run with the scheduler's RBAC permissions as checked at execution time.

### Source excerpt

Recurring platform work slips: provider versions fall behind, drift accumulates between checks, and the quarterly audit keeps getting pushed back another month. Pulumi Neo can now run any task on a cadence you set, opening a pull request for each run. Automations in action Your platform team runs stacks across staging and production, and the AWS, GCP, and Kubernetes providers keep shipping new versions. Nobody has time to bump them stack by stack. You write one automation: Every Monday at 8 AM, check the infra/ project for stacks where the AWS, GCP, or Kubernetes provider is more than two minor versions behind. For each one, bump the out-of-date provider, run pulumi preview, and open a PR if the preview is clean. Monday morning, Neo runs the prompt. It finds three stacks behind on the AWS provider, edits each program, runs preview, and opens a PR for each clean run. You review the PRs like you would any other dependency bump, merge them, and Neo runs again next Monday. What automations are for The launch includes four built-in templates: a provider freshness check, an encryption audit, a backup audit, and an activity digest. You can also skip the templates and write your own prompt. Pick from hourly, daily, weekdays, or weekly cadences. Each automation gets its own page in the Automations tab, where you can edit the prompt, change the schedule, run it once on demand, or pause it. Safe by default Automations default to two settings that fit recurring work. Approval mode is auto, so a run doesn't wait for human confirmation between steps. Permission mode is read-only, so a run can read state and propose changes through pull requests but can't apply changes directly. You can override either default per automation. How automations fit with the rest of Neo A scheduled task uses the same context as an interactive Neo task. Custom Instructions at the organization and project level apply, so a scheduled run respects the same naming conventions, tagging policies, and archite