Make sure every new Lambda GPU instance is set up right
The moment a new GPU instance launches on Lambda, WebRun checks whether an SSH key is attached and persistent storage is mounted, logs the result to Airtable for every instance, and emails you only when the SSH key or storage is missing.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I make sure every new Lambda GPU instance has storage and SSH access configured?
WebRun checks every new Lambda GPU instance the moment it launches, confirming an SSH key is attached and persistent storage is mounted. It logs the result to Airtable for every instance and emails you only when the SSH key or storage is missing, so a training run never starts on an instance that will lose its work when terminated.
- Every new GPU instance gets an SSH key and storage check automatically
- A full setup record builds up in Airtable for every instance
- You get an email only when a real safeguard is missing
Built for ML engineering teams · AI startups · research teams · platform engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
cloud.lambdalabs.comin a real browser with your saved login - no setup, no API keys. -
1
Lambda - check SSH key and storage
WebRun opens Lambda to check SSH key and storage. - Open the new instance in the Lambda Cloud dashboard
- Check whether an SSH key is attached and persistent storage is mounted
- Record a pass or fail for each item
Done when The new instance has a checked status for SSH key and storage.
- 2
- 3
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it attach an SSH key or storage for me?
No. WebRun only checks and records the status. Attaching an SSH key or mounting persistent storage always stays a manual step in the Lambda Cloud dashboard.
Why does storage matter so much for a GPU instance?
Without persistent storage attached, anything saved on the instance is lost when it's terminated, so it's one of the two checks that actually protects your work.
Does it check every instance or just the largest ones?
Every instance. It runs the same checklist the moment any new GPU instance launches, regardless of its size.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.