MacOS MicroVM Studio for Lambda MicroVM
By Fabio Douek
Human-led, AI-assisted. Research and implementation done with AI tools, led, tested and edited by me. How posts are labeled
Jump to section
Explain (TLDR) like I am...
Imagine you have lots of little glass playrooms, and each one is a safe place for a robot helper to play without touching your own toys. This new app is a remote control that opens any playroom with one click, and the helper already has its crayons and drawings inside.
My dad made it, and he wants you to try it and tell him what is confusing. You can use it for free, and the robot helpers did the building while he drew the plan.
This is a free desktop application, distributed under the author's licence agreement with the source code not public. It runs MicroVMs inside the user's own AWS account, so the cloud charges and the data stay with that account, and the licence says the app comes with no warranty.
Before adopting it, note that code inside a MicroVM can use the credentials of the role attached to it, and that Claude tokens and API keys cannot be made short-lived. The author states the app collects nothing and sends nothing to him.
The presenting problem is that a MicroVM from AWS comes without a comfortable way to work inside it for hours. The proposed treatment is a Mac app that opens a terminal per MicroVM, keeps the session across disconnects, and brings repos and sign-ins along.
The evidence base is thin: it is the author's own tool, at version 0.4, and the post does not report an independent evaluation. Known side effects are the AWS bill, which the app only estimates for compute, and a hard 8-hour cap per MicroVM.
There is a particular tiredness in setting up the same environment again and again before you can start the real work. This app tries to take that off your plate: you describe the workspace once, and it is waiting for you each time.
The author is also being open about where he is: the app is new, the App Store submission is still in progress, and he is asking for feedback rather than claiming it is finished. That is an invitation to a conversation, not a launch.
Think of a workspace as a saved preset on a synth. You press one button and the sound is already dialled in: the repos cloned and Claude Code signed in, and with EFS set up, the files where you left them. You skip soundcheck and go straight to playing.
The tmux sessions are the sustain pedal. If the connection drops or the MicroVM suspends, the note keeps ringing and you pick up where you stopped, instead of starting the phrase over.
The story is time-to-first-prompt. A workspace turns an empty cloud VM into a ready place to work: repos cloned, agent signed in, and optionally persistent files on EFS. The app is free, and the author says so up front.
The positioning is narrow and honest: a Mac client for people already running agents in AWS Lambda MicroVMs, who want each session isolated from their laptop. The call to action is feedback, while the App Store submission is still being sorted out.

Designed by humans, built by robots. I designed MicroVM Studio, and AI coding agents built it. It’s a free Mac app that opens a terminal into an AWS Lambda MicroVM, and I’d like your feedback on it.
Overview
AWS Lambda MicroVMs give you an isolated virtual machine in your own AWS account that starts in seconds and suspends when idle. What AWS ships on top is a bare primitive, with no exec API, so working inside one for a few hours means building your own plumbing. I wanted to run Claude Code and Codex in MicroVMs instead of on my laptop, many of them at once, across several regions and AWS accounts, each fully isolated. So I built the plumbing as a Mac app.
That app is MicroVM Studio, and I’ve been working on it since early November. It needs macOS 15 or later, runs on Apple silicon and Intel, and is free to use; the source isn’t public, and the licence says the AWS charges are yours. I’m working on getting it into the Mac App Store, and until it’s approved you can download it from the MicroVM Studio site.
I’ve written about Lambda MicroVMs before:
- The full sandbox lifecycle
- Egress credential injection with iron-proxy
- Self-service sandboxes
- The pricing, explained
This app builds on that work.
Watch It
Two short walkthroughs, which are also on the guide pages. First the quick start, about three and a half minutes, narrated:
Then the persistent /workspace on EFS, under three minutes:
How It Works
Workspaces
A workspace says how to start a MicroVM and what to put in it: the image, GitHub repos, sign-ins, secrets, setup commands and time limits. Launch it with one click, and the app runs the setup in order (mount storage, copy files, add credentials, clone repos, run setup commands) and then opens the terminal. Secret values stay in your Mac’s Keychain, not in the workspace.
Many profiles, many regions
The app works with any number of AWS profiles and keeps separate settings for each. A workspace pins one profile and one region, and you can add more regions per profile. That lets you run several MicroVMs in different regions and accounts side by side, each in its own VM, listed in one sidebar.
Claude Code, Codex and GitHub
GitHub sign-in hands each MicroVM a token that lasts at most 8 hours and reaches only the repos you installed the GitHub App on. Claude Code signs in with a claude setup-token token, an Anthropic API key, or Amazon Bedrock through the workspace’s AWS role. Codex signs in with an OpenAI API key or ChatGPT. The starter image, which takes about five minutes to build in your account, has git, the GitHub CLI, tmux, Node.js, Python, the AWS CLI, Claude Code and Codex.
Terminals that survive
Every MicroVM opens in a terminal in the main window, with split panes. With the default “Keep session” setting, sessions are kept in tmux, so a dropped connection reconnects to the same session with everything still running. By default a MicroVM suspends after 5 minutes with no terminal connected, whatever is running inside, and resumes when you reconnect. AWS caps every MicroVM at 8 hours, and time suspended counts toward it.
Files in and out, and a persistent /workspace
Upload and Download copy files between your Mac and the MicroVM, up to 100 MB per file and no folders (zip them first). For files that should outlive the MicroVM, a workspace can mount a per-workspace folder of an Amazon EFS file system as /workspace. That needs a VPC with private subnets and a NAT gateway, which the app doesn’t create for you.
Guardrails
A menu bar icon shows how many MicroVMs are running and roughly what they cost per hour, compute only. The smallest size, 1 vCPU and 2 GB, is about $0.13 an hour at AWS list rates (I get $0.1261 from the published per-second prices for us-east-1 on ARM). EFS, NAT gateways, snapshot storage and data transfer are on top. The app also warns 30 and 5 minutes before a MicroVM stops, and Save Work pushes uncommitted changes to a wip/ branch on your repo.
What I’m missing is you. It is version 0.4 and the App Store submission is still in progress, so I don’t know yet what breaks on other people’s accounts and regions. If something confuses you, fails, or is missing, open an issue or tell me. It’s free, and feedback is very welcome.