# microvm — RSS Amplifier Recent posts from the 2 feeds in the RSS Amplifier directory that cover microvm. Page: Feed: --- ## [dvito.cloud: AI Lab](https://aaqa.dev/projects/dvito-cloud/) _2026-08-12 · Unknown · Aaqa Ishtyaq_ dvito.cloud is an AI lab for building practical products around AI infrastructure, agents, and developer tooling. The lab owns and builds zei.sh , an ephemeral microVM sandbox platform for AI agent execution. More products are in development. ## [zei.sh: MicroVM Sandbox Platform](https://aaqa.dev/projects/zei-sh/) _2026-08-06 · Unknown · Aaqa Ishtyaq_ zei.sh is a cloud platform providing ephemeral microVM sandboxes (Firecracker and Cloud Hypervisor) for AI agent execution. Clone, branch, and snapshot environments, built for reproducible agent runs, untrusted code execution, and evals. Currently in public beta (v0.1), with a TypeScript SDK, an HTTP API, SSH/WebSSH terminal access, and real-time metrics and logs dashboards. Highlights: 124ms… ## [Baking a Fast Lambda MicroVM: Lessons Learned in the Trenches](https://edjgeek.com/blog/baking-fast-microvm/) _2026-07-14 · edjgeek_ A fresh MicroVM took ~26 seconds from run-hook to a mounted home directory. Getting it to a few seconds taught me that on snapshot-booted compute, cold start is mostly first-touch disk I/O, and the platform's /validate hook is the fix. ## [Lambda MicroVMs + S3 Files: My Claude Code Sandbox for iPad](https://edjgeek.com/blog/claude-code-sandbox-for-ipad/) _2026-07-14 · edjgeek_ A walkthrough of building a browser-based Claude Code shell that runs in an AWS Lambda MicroVM with a persistent S3 Files home. Signed in with Cognito, deployed with SAM. ## [From 9 Tiles to 900: Scaling Computer Vision Pipelines](https://edjgeek.com/blog/9-tiles-to-900-cv-pipelines/) _2026-06-04 · edjgeek_ Computer vision pipelines are scale problems disguised as orchestration problems. You can solve both with a single function. ## [Deploy FastAPI to AWS in 60 Seconds](https://edjgeek.com/blog/deploy-fastapi-aws-60-seconds/) _2026-06-03 · edjgeek_ Deploy a standard FastAPI app to AWS Lambda serverlessly in two commands using Lambda Web Adapter. No Docker. No handler code. No code changes. ## [200,000 MCP Servers Are Exposed. Here's Why Serverless Is Safer.](https://edjgeek.com/blog/mcp-serverless-security/) _2026-04-27 · edjgeek_ MCP's most popular transport has no authentication. AWS serverless removes the conditions that make that dangerous. ## [Cold Starts Are Dead](https://edjgeek.com/blog/lambda-cold-starts-dead/) _2026-04-23 · edjgeek_ Lambda cold starts in 2026 are 200-400ms for Python, sub-100ms for Go and Rust, and 90-140ms for Java with SnapStart. The data says the argument is over. ## [Lambda Managed Instances: A Working Demo and the Math Behind It](https://edjgeek.com/blog/lambda-managed-instances/) _2026-04-20 · edjgeek_ Lambda Managed Instances let multiple invocations share the same CPU while waiting on network calls. Here's a working demo, the cost math, and when LMI actually saves you money. ## [What AI Infrastructure Actually Needs from MicroVMs](https://aaqa.dev/notes/what-ai-infrastructure-needs-from-microvms/) _2026-04-12 · Unknown · Aaqa Ishtyaq_ I have been thinking about AI infrastructure from the compute side more than the model side. There is a lot of noise around AI infrastructure right now. Most of it is about models. The part I care about is everything around the model: where work runs, how fast sandboxes start, how isolated they are, how they reach private tools, how you measure usage, and how you keep the whole thing… ## [AI QA that opens fix PRs (Sponsored)](https://crawlproof.com/a/GcJUxlhcaNX1) _2026-04-11 · **Sponsored**_ Run a browser QA from plain-English instructions; get GitHub issues and optional fix PRs. ## [Scheduling Dense Compute Without Lying to Yourself](https://aaqa.dev/notes/scheduling-dense-compute-without-lying-to-yourself/) _2026-04-11 · Unknown · Aaqa Ishtyaq_ I have been thinking a lot about scheduling lately, especially once warm starts and reservations enter the picture. Schedulers are easy to make impressive in a slide deck. They are much harder to make honest. You can pack nodes aggressively, overcommit a little, and brag about utilization. Then a few bad placement calls land on the wrong hosts and the whole thing feels brittle. That is why I care… ## [My Brother Doesn't Code. Now He Ships Features.](https://edjgeek.com/blog/pipelayer-agent/) _2026-04-11 · edjgeek_ How I built a Telegram bot with Amazon Bedrock AgentCore and Claude that lets a non-developer iterate on a production PWA using plain English. ## [Observability for a MicroVM Platform](https://aaqa.dev/notes/observability-for-a-microvm-platform/) _2026-04-10 · Unknown · Aaqa Ishtyaq_ I love logs, but logs alone have not been enough for the kind of machine lifecycle work I have been doing. You do not really know a platform until something slow or broken happens. That is when the nice diagrams stop helping. A request takes five seconds instead of two hundred milliseconds. A machine gets stuck during startup. A route exists, but traffic still fails. A node looks healthy until you… ## [Lambda Just Got a File System. I Put AI Agents on It.](https://edjgeek.com/blog/s3-files-lambda-agents/) _2026-04-10 · edjgeek_ S3 Files mounts your S3 bucket as a local file system in Lambda. I built AI code review agents that share a workspace through it, orchestrated by a durable function. ## [Host Reconciliation with a Host Agent](https://aaqa.dev/notes/host-reconciliation-with-a-host-agent/) _2026-04-09 · Unknown · Aaqa Ishtyaq_ I actually like SSH. It is useful, fast, and hard to avoid when you are building infrastructure. Still, there is a point in every infrastructure project where SSH becomes a bad habit. At first it feels fast. Jump into a box. Edit a file. Restart a service. Fix the thing. Then the fleet grows, and you realize your operating model is just "hope the last person remembers what changed." That is not a… ## [Why We Built Our Own Machine Proxy](https://aaqa.dev/notes/why-we-built-our-own-machine-proxy/) _2026-04-08 · Unknown · Aaqa Ishtyaq_ When I started thinking about exposing services from machines, one plain question kept showing up: How does traffic reach a machine? That question sounds smaller than it is. Public ingress is not just HTTP. It is TLS, SNI, raw TCP, SSH, WebSSH, machine ownership, and route cleanup when the guest disappears in the middle of the day. That is a lot of stuff to hand-wave. In this post, I want to… ## [Making Internal DNS Boring for Private Machines](https://aaqa.dev/notes/making-internal-dns-boring/) _2026-04-07 · Unknown · Aaqa Ishtyaq_ Once private networking starts to work, DNS becomes the next obvious problem. If private networking is the road system, DNS is the street sign. And like street signs, you only notice it when it is wrong. Nothing makes a platform feel flaky faster than this: the machine is up the network path works the name still does not resolve That gap is small on paper and painful in real use. I have run into… ## [Private Networking for MicroVM Fleets with WireGuard and IPv6](https://aaqa.dev/notes/private-networking-for-microvms-wireguard-ipv6/) _2026-04-06 · Unknown · Aaqa Ishtyaq_ After getting machines to boot reliably, networking was the next thing that forced me to slow down and think properly. Private networking sounds simple when you say it quickly. "Just let the machines talk to each other." Then you try to do it across hosts, across regions, across reboots, without handing every guest a pile of custom firewall rules and mystery routing. That is where the clean model… ## [Fast Starts: Snapshots, Clones, and Warm Slots for MicroVMs](https://aaqa.dev/notes/fast-starts-snapshots-clones-and-warm-slots/) _2026-04-05 · Unknown · Aaqa Ishtyaq_ One of the things I care about most in a compute platform is startup time. People say they want fast machine starts. What they usually mean is they do not want to wait while your platform does cold work right in front of them. That distinction matters a lot. If you create a machine from scratch on demand, you are paying for a bunch of slow steps in public: prepare a root filesystem create overlays… ## [Stateless Regional Control Planes and Replicated State](https://aaqa.dev/notes/stateless-regional-control-plane-with-gossip-state/) _2026-04-04 · Unknown · Aaqa Ishtyaq_ I like control planes that can die without drama. If a regional API process restarts, I do not want a rescue mission. I want it to come back, rebuild what it needs, and keep serving traffic. That pushes you toward a simple rule: The control plane should not own more durable state than it has to. I ran into this while thinking through the regional control plane. The more state I wanted to push into… ## [Open coordination for humans & AI (Sponsored)](https://crawlproof.com/a/JCJzC3NAt9mC) _2026-04-03 · **Sponsored**_ Shared schemas and CLI tooling to validate, route, and audit human-agent workflows. ## [How a Worker Node Runs a MicroVM](https://aaqa.dev/notes/how-a-worker-node-runs-a-microvm/) _2026-04-03 · Unknown · Aaqa Ishtyaq_ After removing the earlier draft for this slot, I still wanted a post here that explains one of the most important parts of the platform: what actually happens on the worker node when a machine gets created. This part matters because a lot of the rest of the system only makes sense once you know what the worker is responsible for. The control plane can pick a node. The proxy can expose traffic.… ## [Why a MicroVM Platform Needs a Crash-Resistant Machine FSM](https://aaqa.dev/notes/crash-resistant-machine-fsms/) _2026-04-02 · Unknown · Aaqa Ishtyaq_ While working on the worker side of the platform, one thing became obvious pretty quickly: machine lifecycle code looks easy only when you test happy paths. Create a machine. Start it. Stop it. Delete it. That idea falls apart the first time a host reboots halfway through startup. Now you have harder questions: Was the VM process created? Did networking finish? Did the root filesystem get… ## [Building a MicroVM Control Plane in Public](https://aaqa.dev/notes/building-a-microvm-control-plane/) _2026-04-01 · Unknown · Aaqa Ishtyaq_ Over the past couple of years, I have been spending a lot of time with Firecracker, microVMs, and a distributed compute platform I have been building. It started with a simple goal: run Firecracker on a machine I control and understand every moving part. That sounds small, but it really is not. The first few steps are easy enough to explain. Boot a VM. Get KVM working. Start Firecracker. Launch a… ## [Hey, I'm edjgeek](https://edjgeek.com/blog/hello-world/) _2026-04-01 · edjgeek_ A little about me, what I work on, and what you'll find on this blog.