Ask who last updated the production stack in Pulumi, and what changed.
Connect Pulumi with an access token and Memtro reads stacks by organisation, project and tag, each stack's tags and any running operation, its update history, and the organisation audit log. Stack configuration, environment variables, resource properties and ESC secrets are never read. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can add, change or remove stack tags, create or delete an empty stack, and start a Pulumi Deployments run, which can change or permanently destroy real cloud infrastructure, or cancel, pause and resume runs.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Pulumi tool, reads what it needs, and answers with the source cited.
These tools change something in Pulumi. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Pulumi for you. Each event can start a job, with the event as its input. Pulumi signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Pulumi is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who last updated the production stack, and did it succeed?
When was the payments stack last deployed?
Which stack updates failed this week?
Run a drift check on the acme-api production stack
Add a tag owner with value platform-team to the acme-api production stack
The platform lead asks what happened to the Acme production stack overnight. Memtro reads its update history: Priya Nair ran an update at 23:10 that changed 14 resources and succeeded, and a refresh at 02:00 failed with a timeout message.
While the Northwind database is being repaired, Dan Fletcher asks Memtro to stop any deployments starting on the billing stack. Memtro pauses its Pulumi Deployments, so runs already executing finish and new ones wait in the queue, and reminds him that resuming will start everything queued.
The teams that lean on Pulumi most, a question each of them asks, and what they connect beside it.
A record in Pulumi is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn app.pulumi.com open your avatar → Personal access tokens, create a token named Memtro with an expiry and copy it. A personal token can do what you can do, and an organisation or team token works where your plan offers them
In Memtro open Connections → Pulumi, paste the Access token, add the Organisation name from app.pulumi.com/<organisation> if the token belongs to more than one, and connect
Audit logs need a Pulumi plan that includes them (Business Critical or Enterprise). Only the managed Pulumi Cloud is supported, not self-hosted
Ask who last updated the production stack, and whether it succeeded
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Pulumi tools are the same everywhere.
Only when you ask, and only what it has been granted: add a tag (name and value) to a stack; change the value of an existing stack tag; remove a tag from a stack; create a new empty stack in a project (and the project if absent); delete a stack that no longer manages any resources; start a Pulumi Deployments run on a stack: update, preview, refresh, destroy, drift detection or remediation; cancel a queued or running deployment; pause a stack's deployments so queued runs wait; resume a stack's paused deployments so queued runs start. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Access token. In app.pulumi.com open your avatar → Personal access tokens, create a token named Memtro with an expiry and copy it. A personal token can do what you can do, and an organisation or team token works where your plan offers them.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Pulumi for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
