GPU spend check
Tom Reilly, ML lead at BigCo, asked which GPU instances were running and their hourly price. Memtro listed each with its type, region and price. He spotted an idle one from last week and asked the team about it.
Lambda Cloud + Memtro
Which Lambda GPU instances are running, and what do they cost per hour?
Lambda Cloud connects Memtro to your GPU cloud account. It reads running instances with type, GPUs, region, hourly price and status, and instance types with prices and which regions have capacity now. It also reads images, persistent filesystems, support tickets and the account's audit log. When asked and granted, it can launch, restart, terminate, rename or retag instances, create or delete filesystems, and open, comment on or close support tickets. Lambda can also tell Memtro when a support ticket is created, changes status or is solved, and a job can start on it. Lambda support must set those events up.
In Memtro
What you can do with Lambda Cloud in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Lambda Cloud tool, reads what it needs, and answers with the source cited.
What it does
- 01Running instances with name, status, type, GPUs, region, IPs, hourly price, image, filesystems and tags.
- 02Instance types with GPU, memory, storage, hourly price and the regions with capacity right now, plus machine images.
- 03Persistent filesystems, support tickets with status, severity and priority, and the account's audit log.
- 04When asked and granted, launches an instance, which starts hourly billing, or restarts, terminates, renames or retags instances.
- 05When asked and granted, creates or deletes a filesystem, and opens, comments on, re-prioritises or closes a support ticket. Lambda's support staff see what is sent.
- 06With events on, a support ticket created, its status changing or it being solved can start a job.
Acts when asked
When you ask it to
These tools change something in Lambda Cloud. 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.
- 01Launch a GPU instance (billed per hour)
- 02Restart instances
- 03Terminate instances
- 04Rename or retag an instance
- 05Create a persistent filesystem
- 06Delete a filesystem
- 07Open a support ticket with Lambda
- 08Comment on, re-prioritise or close a support ticket
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Lambda Cloud, choosing the same kinds; the tab shows Lambda Cloud's own steps. Each event can start a job, with the event as its input. Lambda Cloud sends a secret with every delivery, and one without it is refused.
Events and webhooks- 01A support ticket was created
- 02A support ticket's status changed and it is still open
- 03A support ticket was solved or closed
In practice
Ask it like you would a colleague
Once Lambda Cloud 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.
Lambda Cloud + Memtro
Which instances are running, and what do they cost per hour?
Which instance types can be launched right now, and in which regions?
Which support tickets with Lambda are still open?
Which instances were launched or terminated this week, according to the audit log?
Restart the training-02 instance.
Ticket solved, job runs
When Lambda marked Northwind's support ticket about an unhealthy host solved, Lambda told Memtro and a job started. It read the ticket and the instance it named, then reported the instance's current status to Maya Okafor, the infrastructure engineer.
Teams
Where it fits
The teams that lean on Lambda Cloud most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in Lambda Cloud 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.
- Work managementLambda Cloud with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementLambda Cloud with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementLambda Cloud with LinearIssues, projects and teams, synced hourly into memory.
- SupportLambda Cloud with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportLambda Cloud with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportLambda Cloud with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisLambda Cloud with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisLambda Cloud with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisLambda Cloud with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withAPI key
- 1
In Lambda Cloud, open API keys and generate an API key. It carries the roles of whoever created it and is shown once.
- 2
In Memtro, open Connections → Lambda Cloud and paste the API key.
- 3
An administrator grants the actions by name, such as Terminate instances, to the teams that may use them. Events are turned on from the connection's Events tab, then Lambda support is asked to send ticket webhooks to the address.
- 4
Ask "Which instances are running, and what do they cost per hour?"
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Lambda Cloud tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Lambda Cloud?+
Only when you ask, and only what it has been granted: launch a GPU instance (billed per hour); restart instances; terminate instances; rename or retag an instance; create a persistent filesystem; delete a filesystem; open a support ticket with Lambda; comment on, re-prioritise or close a support ticket. 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.
Who can use a Lambda Cloud connection?+
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.
Does Memtro store my Lambda Cloud data?+
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.
How do I connect Lambda Cloud?+
API key. In Lambda Cloud, open API keys and generate an API key. It carries the roles of whoever created it and is shown once.
Can Lambda Cloud start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Lambda Cloud, choosing the same kinds; the tab shows Lambda Cloud's own steps. 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.
Connect Lambda Cloud in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.