# Firecracker

An open-source virtualization technology and VMM for securely running lightweight microVMs for container and serverless workloads.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Build an On-Call Team of AI Agents on DigitalOcean MicroVMs

DevFeed: [Build an On-Call Team of AI Agents on DigitalOcean MicroVMs](<https://devfeed.tech/articles/build-an-on-call-team-of-ai-agents-on-digitalocean-microvms-142019.md>)

Original publisher: [Read original article](<https://www.digitalocean.com/blog/ai-agents-incident-response-microvms>)

Author: Calin Lupa

Published: 2026-11-18T22:22:27Z

Content type: tutorial

Language: en

Sources: [DigitalOcean](<https://devfeed.tech/sources/digitalocean.md>)

Topics: [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alert](<https://devfeed.tech/tags/alert.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [code](<https://devfeed.tech/tags/code.md>), [commits](<https://devfeed.tech/tags/commits.md>), [compute](<https://devfeed.tech/tags/compute.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [containers](<https://devfeed.tech/tags/containers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [digitalocean](<https://devfeed.tech/tags/digitalocean.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [fast](<https://devfeed.tech/tags/fast.md>), [files](<https://devfeed.tech/tags/files.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

The guide describes an on-call team of AI agents running in separate DigitalOcean MicroVMs: agents investigate metrics, commits, and Droplet snapshots in parallel, then pause for human approval before rollback. Each MicroVM is isolated and holds no credentials beyond its assigned scope; while approval is pending, it can pause and incur storage-only billing. The excerpt frames MicroVMs as a middle ground between containers, which start quickly but share the host kernel, and regular VMs, which provide a hard boundary but bill while idle and start more slowly. It says each MicroVM runs a container image in a lightweight Firecracker VM with its own kernel. The excerpt introduces the guide's rationale and workflow but ends mid-description, so it does not establish further implementation details.

### Source excerpt

A deploy goes out, and checkout starts failing. Within minutes, three agents are investigating in parallel: one reading metrics, one reading commits, and one checking the Droplet's snapshots. Each works in its own MicroVM, none holding a credential for anything outside. Then the team does something most agent demos skip: it stops and asks a person to approve the rollback. While that person decides, every MicroVM the investigation used pauses and bills only for storage. We built this on-call team of AI agents on DigitalOcean MicroVMs. But the agents are only half of the story. What made the team safe to run, and cheap to leave waiting, was the infrastructure beneath it. This guide covers that first, then follows the incident from alert to verified fix. The code to run it yourself is at the end. Why agents break traditional cloud primitives Once an agent starts doing production work, it requires real infrastructure: Compute it can start in seconds and trust with generated code no human reviewed Storage that keeps its files and packages between turns A network that controls where it can reach and who can reach it Credentials scoped to its job When the work splits across subagents, each one needs all of these components, and fast. And because agents spend much of their time waiting, on a model's response or a person's approval, you don't want to pay for that idle time. Containers and regular VMs each force a tradeoff. A container starts fast but shares the host's kernel, which is more trust than you want to give to code an agent just wrote. A regular VM gives you a hard boundary but bills for every minute it waits and is slow to start one per subagent or task. You can close the gap yourself, but then you're running a virtualization platform rather than building your own agent. The infrastructure stack for AI agents on DigitalOcean MicroVMs close that gap. Each DigitalOcean MicroVM runs your container image in its own lightweight Firecracker VM with its own kernel, one p

## Sandboxing AI Agent Code Execution in Python: Containers, MicroVMs and Beyond

DevFeed: [Sandboxing AI Agent Code Execution in Python: Containers, MicroVMs and Beyond](<https://devfeed.tech/articles/sandboxing-ai-agent-code-execution-in-python-containers-microvms-and-beyond-129976.md>)

Original publisher: [Read original article](<https://machinelearningmastery.com/sandboxing-ai-agent-code-execution-in-python-containers-microvms-and-beyond/>)

Author: Shittu Olumide

Published: 2026-11-11T11:00:27Z

Content type: tutorial

Language: en

Sources: [MachineLearningMastery.com](<https://devfeed.tech/sources/machinelearningmastery-com.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Python](<https://devfeed.tech/topics/python.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [Process](<https://devfeed.tech/topics/process.md>), [runc](<https://devfeed.tech/topics/runc.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [all](<https://devfeed.tech/tags/all.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [containers](<https://devfeed.tech/tags/containers.md>), [execution](<https://devfeed.tech/tags/execution.md>), [need](<https://devfeed.tech/tags/need.md>), [python](<https://devfeed.tech/tags/python.md>), [sandboxing](<https://devfeed.tech/tags/sandboxing.md>)

### AI overview

The excerpt builds one `run_python` tool over three interchangeable Python sandbox backends. A limited subprocess is fastest but shares the host kernel and files; its test blocks four of six attacks, while a fork flood and fake-secret read succeed. A hardened Docker setup adds network isolation, a read-only filesystem, privilege removal, and CPU, memory, and process limits; the excerpt says it should block all six tests. An E2B Firecracker microVM gives each run its own kernel and is destroyed afterward; resource attacks remain bounded by the chosen VM, while host files and local services are absent. The benchmark warms up, then measures ten `print(1)` runs by median and slowest time, including VM startup. The excerpt recommends subprocesses for trusted code, containers for lower stakes on a controlled host, and microVMs for code from many users or touching secrets. It notes the subprocess process limit requires a dedicated user and containers still share the host kernel.

### Source excerpt

You need Python 3.

## Serverless ICYMI Q3 2026

DevFeed: [Serverless ICYMI Q3 2026](<https://devfeed.tech/articles/serverless-icymi-q3-2026-119355.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/serverless-icymi-q3-2026/>)

Author: Julian Wood

Published: 2026-11-05T13:50:18Z

Content type: news

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [icymi](<https://devfeed.tech/tags/icymi.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [q3](<https://devfeed.tech/tags/q3.md>), [recap](<https://devfeed.tech/tags/recap.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The excerpt reports Q3 2026 AWS serverless updates spanning event routing, compute, workflows, storage and AI tooling. EventBridge's relaunched custom bus supports cross-account subscribers, configurable retention, keyed ordering and Avro, Protocol Buffers or JSON; it runs alongside the classic bus. Lambda changes include scalable network bandwidth for larger functions, container-image SnapStart, SQS polling capacity up to 10,000 event pollers, and loading code from customers' S3 buckets. Lambda Managed Instances allow 90-minute invocations and support newer Graviton instances; durable functions add .NET support, bring-your-own SDKs and customer-managed KMS encryption. Lambda MicroVMs provide Firecracker-isolated environments lasting up to eight hours and are available in 10 Regions with PrivateLink. Other reported changes include Step Functions integrations, SNS messages up to 1 MiB, API Gateway backend mTLS, and S3 updates. AI additions include serverless agent-inspection tools, AgentCore features, and Strands harness and evaluation tools. The source is a quarterly recap excerpt with launch claims and links to related resources, not a detailed evaluation of each feature.

### Source excerpt

In this 34th quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q3 2026 that you might have missed.

## Perplexity Open-Sources SPACE, a Firecracker MicroVM Sandbox for AI Agents

DevFeed: [Perplexity Open-Sources SPACE, a Firecracker MicroVM Sandbox for AI Agents](<https://devfeed.tech/articles/perplexity-open-sources-space-a-firecracker-microvm-sandbox-for-ai-agents-88911.md>)

Original publisher: [Read original article](<https://www.marktechpost.com/2026/10/16/perplexity-open-sources-space-firecracker-microvm-sandbox-ai-agents/>)

Author: Asif Razzaq

Published: 2026-10-17T00:09:12Z

Content type: news

Language: en

Sources: [MarkTechPost](<https://devfeed.tech/sources/marktechpost.md>)

Topics: [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-shorts](<https://devfeed.tech/tags/ai-shorts.md>), [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [api](<https://devfeed.tech/tags/api.md>), [applications](<https://devfeed.tech/tags/applications.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [editors-pick](<https://devfeed.tech/tags/editors-pick.md>), [for-devs](<https://devfeed.tech/tags/for-devs.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [new-releases](<https://devfeed.tech/tags/new-releases.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [staff](<https://devfeed.tech/tags/staff.md>), [tech-news](<https://devfeed.tech/tags/tech-news.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

Perplexity open-sourced SPACE, a Rust sandbox platform that runs each agent task in its own Firecracker microVM. Its host-side gateway controls outbound traffic and credentials, while the HTTP API supports creating environments, running commands, and streaming output. The article describes its architecture, deployment requirements, performance claims, and red-team results, including initial partial-network policy bypasses that Perplexity says it addressed.

### Source excerpt

Perplexity has open-sourced SPACE, the sandbox platform behind every task in Perplexity Computer. The Perplexity SPACE sandbox gives each agent task its own Firecracker microVM. Credentials and outbound traffic are controlled from outside that VM. The code ships under Apache 2.0 on GitHub. For teams building coding or browsing agents, this is a production-tested isolation [...] The post Perplexity Open-Sources SPACE, a Firecracker MicroVM Sandbox for AI Agents appeared first on MarkTechPost.

## Get started with AWS Lambda SnapStart for container images

DevFeed: [Get started with AWS Lambda SnapStart for container images](<https://devfeed.tech/articles/get-started-with-aws-lambda-snapstart-for-container-images-65876.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/get-started-with-aws-lambda-snapstart-for-container-images/>)

Author: Sachin Saini

Published: 2026-10-06T16:59:51Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [distroless](<https://devfeed.tech/topics/distroless.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [latency](<https://devfeed.tech/tags/latency.md>)

### AI overview

AWS Lambda SnapStart now supports container image functions, restoring an initialized execution environment from a cached snapshot to reduce startup time. The tutorial explains how to enable it, handle state that may become stale or shared after restore, monitor restore duration, and account for limitations and pricing.

### Source excerpt

AWS Lambda SnapStart now supports container image functions, reducing startup times from several seconds to as low as sub-second. Learn how SnapStart for container images works, how to enable it on new or existing functions, and best practices for latency-sensitive workloads.

## Run Agentic Workloads Safely at Scale with CoreWeave Sandboxes

DevFeed: [Run Agentic Workloads Safely at Scale with CoreWeave Sandboxes](<https://devfeed.tech/articles/run-agentic-workloads-safely-at-scale-with-coreweave-sandboxes-78026.md>)

Original publisher: [Read original article](<https://wf.coreweave.com/blog/run-agentic-workloads-safely-at-scale-with-coreweave-sandboxes>)

Author: CoreWeave

Published: 2026-10-02T14:12:41Z

Content type: release

Language: en

Sources: [Coreweave Blog Posts](<https://devfeed.tech/sources/coreweave-blog-posts.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [ai-on-mobile](<https://devfeed.tech/topics/ai-on-mobile.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [compute](<https://devfeed.tech/tags/compute.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [container](<https://devfeed.tech/tags/container.md>), [content-type](<https://devfeed.tech/tags/content-type.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [coreweave](<https://devfeed.tech/tags/coreweave.md>), [coreweave-kubernetes-service](<https://devfeed.tech/tags/coreweave-kubernetes-service.md>), [coreweave-sandboxes](<https://devfeed.tech/tags/coreweave-sandboxes.md>), [costs](<https://devfeed.tech/tags/costs.md>), [development](<https://devfeed.tech/tags/development.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [execution](<https://devfeed.tech/tags/execution.md>), [model-evaluation](<https://devfeed.tech/tags/model-evaluation.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>)

### AI overview

CoreWeave has introduced Sandboxes, an execution layer for reinforcement learning, agent tool use, and model evaluation. It runs on customer-operated CoreWeave Kubernetes Service clusters or as a serverless runtime on CoreWeave-managed compute. The announcement describes per-sandbox isolation, run-linked debugging traces, and scheduling across available cluster capacity.

### Source excerpt

CoreWeave Sandboxes delivers isolated execution for RL, agent tool use, and model evaluation, on your clusters or as a serverless runtime.

## Adding custom domains to AWS Lambda MicroVMs with Application Load Balancer

DevFeed: [Adding custom domains to AWS Lambda MicroVMs with Application Load Balancer](<https://devfeed.tech/articles/adding-custom-domains-to-aws-lambda-microvms-with-application-load-balancer-58218.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/adding-custom-domains-to-aws-lambda-microvms-with-application-load-balancer/>)

Author: Frank Scarfo

Published: 2026-09-22T16:48:32Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Amazon Machine Learning](<https://devfeed.tech/topics/amazon-machine-learning.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cors](<https://devfeed.tech/tags/cors.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [development](<https://devfeed.tech/tags/development.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [networking](<https://devfeed.tech/tags/networking.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial presents a reusable networking pattern for exposing AWS Lambda MicroVMs through custom domains while supporting browser CORS without changing the MicroVM application. It uses an Application Load Balancer for TLS termination, host-header rewriting, CORS handling, and private forwarding over AWS PrivateLink, with deployment through the AWS CDK.

### Source excerpt

Many teams want to expose their AWS Lambda MicroVMs under a custom domain they own, and satisfy CORS for browser clients, without changing the application. This post shows how, using an Application Load Balancer that rewrites the Host header and forwards over AWS PrivateLink, deployed with the AWS CDK.

## Running self-hosted AI agent sandboxes with AWS Lambda MicroVMs

DevFeed: [Running self-hosted AI agent sandboxes with AWS Lambda MicroVMs](<https://devfeed.tech/articles/running-self-hosted-ai-agent-sandboxes-with-aws-lambda-microvms-55130.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/running-self-hosted-ai-agent-sandboxes-with-aws-lambda-microvms/>)

Author: Brian Krygsman

Published: 2026-09-18T15:10:33Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>)

### AI overview

This tutorial explains how to use AWS Lambda MicroVMs as self-hosted, VM-isolated sandboxes for AI agent tool calls. It describes per-session isolation for credentials, filesystems, and networking, with a control plane that keeps execution within an AWS account.

### Source excerpt

Learn how to run AI agent tool calls in secure, isolated sandboxes using AWS Lambda MicroVMs. This post shows how to architect a self-hosted control plane that launches a fresh, VM-isolated MicroVM for each agent session, keeping credentials, networking, and governance entirely within your own AWS account.

## Run Terminal-Bench and other Harbor evals on Vercel Sandbox

DevFeed: [Run Terminal-Bench and other Harbor evals on Vercel Sandbox](<https://devfeed.tech/articles/run-terminal-bench-and-other-harbor-evals-on-vercel-sandbox-42111.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/run-terminal-bench-and-other-harbor-evals-on-vercel-sandbox>)

Author: George Fahmy

Published: 2026-09-17T19:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [LLM evaluation / benchmarking](<https://devfeed.tech/topics/llm-evaluation-benchmarking.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Firewall](<https://devfeed.tech/topics/firewall.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gpt](<https://devfeed.tech/tags/gpt.md>), [harbor](<https://devfeed.tech/tags/harbor.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [openai](<https://devfeed.tech/tags/openai.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [terminal](<https://devfeed.tech/tags/terminal.md>)

### AI overview

Vercel Sandbox now supports running Harbor evaluations, including Terminal-Bench and other benchmarks. Each trial runs in an isolated Firecracker microVM, with network policies enforced by an external sandbox firewall and optional credential injection. AI Gateway enables benchmarking models from multiple providers using Harbor.

### Source excerpt

You can now run Harbor evals on Vercel Sandbox. Harbor is the open-source harness behind Terminal-Bench, whose registry includes many other benchmarks such as SWE-bench, tau3-bench and OSWorld. Pass --env vercel to harbor run and each trial executes in its own isolated Firecracker microVM, so you can parallelize far beyond what your local machine is capable of. A task's network policy is enforced at the sandbox firewall, outside the VM. Optional credential injection attaches secrets to matching outbound requests at that firewall, so they never enter the sandbox. Paired with AI Gateway, one AI_GATEWAY_API_KEY reaches hundreds of models from multiple providers, and benchmarking another model is the same command with a different --model: Swap --model to vercel_ai_gateway/openai/gpt-5.6-luna to run the same benchmark against an OpenAI model. Requires Harbor 0.22.0 or later. Follow the step-by-step guide for setup, configuration, and troubleshooting. Learn more in the Sandbox documentation. Read more

## Cursor Cloud Agents can now run in Vercel Sandbox

DevFeed: [Cursor Cloud Agents can now run in Vercel Sandbox](<https://devfeed.tech/articles/cursor-cloud-agents-can-now-run-in-vercel-sandbox-1075.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/run-cursor-cloud-agents-vercel-sandbox>)

Author: Allen Zhou

Published: 2026-09-03T15:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [cursor](<https://devfeed.tech/topics/cursor.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [guide](<https://devfeed.tech/tags/guide.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [scale](<https://devfeed.tech/tags/scale.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Cursor Cloud Agents can run in Vercel Sandbox, using isolated Firecracker microVMs as their execution environment. The architecture combines Cursor's agent harness and inference loop with Vercel Functions and Workflows for durable request handling, worker provisioning, monitoring, retries, cleanup, and short-lived user-scoped credentials.

### Source excerpt

Cursor Cloud Agents can now run in Vercel Sandbox instead of Cursor's hosted machines. Cursor manages the agent harness and inference loop. Its Self-Hosted Machines APIs let you supply the execution environment where agents clone repositories, edit files, and run commands and tests. Self-Hosted Machines requires a Cursor Enterprise plan. Vercel Sandbox provides that execution environment as an isolated Firecracker microVM for each agent request. Vercel Functions and Vercel Workflows form a durable control plane that claims queued agent requests, provisions workers, monitors sessions, and cleans up automatically. With this architecture, you get: A scale-to-zero worker pool without long-lived virtual machines A dedicated, isolated Sandbox for every agent request Durable retries when a worker or session fails Short-lived, user-scoped credentials inside each Sandbox Follow the step-by-step guide to deploy the reference implementation to your own Vercel account, or learn more in the Vercel Sandbox documentation. Read more

## $1 million hacker challenge for Vercel Sandbox

DevFeed: [$1 million hacker challenge for Vercel Sandbox](<https://devfeed.tech/articles/1-million-hacker-challenge-for-vercel-sandbox-769.md>)

Original publisher: [Read original article](<https://vercel.com/blog/one-million-dollar-hacker-challenge-for-vercel-sandbox>)

Author: Andy Riancho

Published: 2026-08-18T13:00:00Z

Content type: article

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Network](<https://devfeed.tech/topics/network.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [bounty](<https://devfeed.tech/tags/bounty.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network](<https://devfeed.tech/tags/network.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [security](<https://devfeed.tech/tags/security.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Vercel announces a two-week public HackerOne challenge offering up to $1 million in total payouts for researchers who can escape Vercel Sandbox isolation. The article explains that Sandbox uses Firecracker microVMs on bare-metal Amazon EC2 hosts, with host-side network controls forming part of the security boundary. Individual reports can receive up to $50,000 for vulnerabilities allowing access to another Vercel tenant's data.

### Source excerpt

Agents need to run untrusted code, and the microVM has become the standard way to do it: a dedicated guest kernel per workload, isolated from the host and from every other workload on the same machine. But recent security research and real-world incidents have revealed that agents running untrusted code do not need to cross a VM boundary to escape containment; they only need one network path the security model failed to account for, which we explained in our post A sandbox without a network boundary is only half a sandbox. Isolation only holds if both sides of it hold: the Firecracker microVM and the host-side network controls. Recently our CTO pointed an open-weight model with no safeguards at Vercel Sandbox. It did not escape, but it mapped the guest kernel, built a VM to reproduce its ideas, and wrote a fuzzer. Defenders have first-mover advantage, but it won't last forever, and the choice is when to test the boundaries (we strongly encourage building a scanning program, which you can do on any budget with an open-source tool like deepsec and AI Gateway). We are proactively choosing to test Vercel Sandbox on our own schedule, not an attacker's, and we are doing it in the open, with the best researchers in the world. So for two weeks, we are paying up to $1,000,000 USD to the researchers who can escape a Vercel Sandbox. The challenge Starting today, Vercel is running a two-week public HackerOne program focused on Vercel Sandbox isolation. Program: Public HackerOne program, open to all eligible researchers Window: Tuesday, August 18 to Tuesday, September 1, 2026, or earlier if the reward pool is exhausted Max per report: $50,000 USD, for a vulnerability that lets a threat actor read or modify another Vercel tenant's data Total pool: Up to $1,000,000 USD in total payouts Bounties are paid per report, scoped to a single root cause, and assigned by Vercel triage based on the maximum demonstrable impact. The full bounty table, detailed scope, and the list of known-dupl

## We rebuilt the Linux microVM stack on Apple Silicon

DevFeed: [We rebuilt the Linux microVM stack on Apple Silicon](<https://devfeed.tech/articles/we-rebuilt-the-linux-microvm-stack-on-apple-silicon-17799.md>)

Original publisher: [Read original article](<https://encore.dev/blog/firecracker-apple-silicon>)

Author: Ivan Cernja

Published: 2026-08-18T00:00:00Z

Content type: article

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>)

Tags: [docker](<https://devfeed.tech/tags/docker.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [go](<https://devfeed.tech/tags/go.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

Encore rebuilt its Linux microVM development stack to work on Apple Silicon. The article describes crackling, an API that uses Firecracker on Linux and Apple's hypervisor on macOS, along with the tooling needed to run the same build system on developer laptops and in production.

### Source excerpt

Maybe we should have just moved everyone to Linux.

## Easily Develop AWS Lambda MicroVM Sandbox Architectures

DevFeed: [Easily Develop AWS Lambda MicroVM Sandbox Architectures](<https://devfeed.tech/articles/easily-develop-aws-lambda-microvm-sandbox-architectures-14086.md>)

Original publisher: [Read original article](<https://www.serverless.com/blog/aws-lambda-microvms-sandboxes>)

Author: Serverless Team

Published: 2026-07-21T00:00:00Z

Content type: article

Language: en

Sources: [Serverless](<https://devfeed.tech/sources/serverless-blog.md>)

Topics: [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [code](<https://devfeed.tech/tags/code.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [faas](<https://devfeed.tech/tags/faas.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [framework](<https://devfeed.tech/tags/framework.md>), [function-as-a-service](<https://devfeed.tech/tags/function-as-a-service.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [local](<https://devfeed.tech/tags/local.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [news](<https://devfeed.tech/tags/news.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [serverless-architecture](<https://devfeed.tech/tags/serverless-architecture.md>), [serverless-framework](<https://devfeed.tech/tags/serverless-framework.md>), [test](<https://devfeed.tech/tags/test.md>), [virtual](<https://devfeed.tech/tags/virtual.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>)

### AI overview

AWS Lambda MicroVMs run untrusted or agent-generated code in isolated Firecracker virtual machines. The Serverless Framework exposes them as Sandboxes in `serverless.yml`, with one-command deployment and a local MicroVM emulator for building and testing before shipping.

### Source excerpt

AWS Lambda MicroVMs are a new compute primitive for running untrusted and agent-generated code in fully isolated Firecracker virtual machines. The Serverless Framework brings them into serverless.yml as Sandboxes, with one-command deploys and a full local MicroVMs emulator so you can build and test before you ship.

## Serverless ICYMI Q2 2026

DevFeed: [Serverless ICYMI Q2 2026](<https://devfeed.tech/articles/serverless-icymi-q2-2026-4672.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/serverless-icymi-q2-2026/>)

Author: Julian Wood

Published: 2026-07-20T16:40:00Z

Content type: article

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [mount](<https://devfeed.tech/topics/mount.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [latency](<https://devfeed.tech/tags/latency.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mount](<https://devfeed.tech/tags/mount.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

A Q2 2026 recap of AWS serverless launches and resources, focusing on AWS Lambda MicroVMs and Amazon S3 Files integration with Lambda.

### Source excerpt

In this 33rd quarterly recap post, discover the most impactful AWS serverless launches, features, and resources from Q2 2026 that you might have missed. Stay current with the latest serverless innovations that can improve your applications. In case you missed our last ICYMI, read about what happened in Q1 2026. AWS Lambda MicroVMs AWS Lambda [...]

## Daytona adds microVM sandboxes with pause, resume, and fork

DevFeed: [Daytona adds microVM sandboxes with pause, resume, and fork](<https://devfeed.tech/articles/vms-pause-fork-81714.md>)

Original publisher: [Read original article](<https://www.daytona.io/dotfiles/vms-pause-and-fork>)

Author: Juraj Štefanić Technical Content Engineer

Published: 2026-07-10T00:00:00Z

Content type: release

Language: en

Sources: [Dotfiles Insider](<https://devfeed.tech/sources/dotfiles-insider.md>)

Topics: [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Docker Sandboxes](<https://devfeed.tech/topics/docker-sandboxes.md>), [AI Sandbox](<https://devfeed.tech/topics/ai-sandbox.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>)

Tags: [ai-generated-code](<https://devfeed.tech/tags/ai-generated-code.md>), [ai-workflows](<https://devfeed.tech/tags/ai-workflows.md>), [browser-based-ide](<https://devfeed.tech/tags/browser-based-ide.md>), [browser-ide](<https://devfeed.tech/tags/browser-ide.md>), [cloud-coding](<https://devfeed.tech/tags/cloud-coding.md>), [cloud-dev-environment](<https://devfeed.tech/tags/cloud-dev-environment.md>), [cloud-development-environment](<https://devfeed.tech/tags/cloud-development-environment.md>), [cloud-editor](<https://devfeed.tech/tags/cloud-editor.md>), [cloud-ide](<https://devfeed.tech/tags/cloud-ide.md>), [cloud-programming](<https://devfeed.tech/tags/cloud-programming.md>), [code-in-cloud](<https://devfeed.tech/tags/code-in-cloud.md>), [code-on-web](<https://devfeed.tech/tags/code-on-web.md>), [coding-environment](<https://devfeed.tech/tags/coding-environment.md>), [containers](<https://devfeed.tech/tags/containers.md>), [daytona](<https://devfeed.tech/tags/daytona.md>), [ide-editor-online](<https://devfeed.tech/tags/ide-editor-online.md>), [ide-in-browser](<https://devfeed.tech/tags/ide-in-browser.md>), [ide-online](<https://devfeed.tech/tags/ide-online.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [long-running-agents](<https://devfeed.tech/tags/long-running-agents.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [online-code-editor](<https://devfeed.tech/tags/online-code-editor.md>), [online-ide](<https://devfeed.tech/tags/online-ide.md>), [online-programming](<https://devfeed.tech/tags/online-programming.md>), [online-web-dev-ide](<https://devfeed.tech/tags/online-web-dev-ide.md>), [online-web-development-ide](<https://devfeed.tech/tags/online-web-development-ide.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [sde](<https://devfeed.tech/tags/sde.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>), [snapshots](<https://devfeed.tech/tags/snapshots.md>), [standardised-development-environment](<https://devfeed.tech/tags/standardised-development-environment.md>), [stories-insights](<https://devfeed.tech/tags/stories-insights.md>), [vm](<https://devfeed.tech/tags/vm.md>), [web-based-coding](<https://devfeed.tech/tags/web-based-coding.md>), [web-ide](<https://devfeed.tech/tags/web-ide.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

Daytona sandboxes now run as microVMs with machine-level isolation. The release adds pause and resume that preserve machine state, plus VM forking to create independent copies for branching AI workflows.

### Source excerpt

Run Daytona sandboxes as microVMs with machine-level isolation, instant pause/resume, and VM forking for AI workflows.

## How Prisma Compute Keeps Time Accurate in Long-Running Applications

DevFeed: [How Prisma Compute Keeps Time Accurate in Long-Running Applications](<https://devfeed.tech/articles/how-prisma-compute-keeps-time-accurate-in-long-running-applications-47715.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/prisma-compute-time-synchronization>)

Author: Alexey Orlenko

Published: 2026-06-26T00:00:00Z

Content type: article

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [Prisma](<https://devfeed.tech/topics/prisma.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>)

Tags: [compute](<https://devfeed.tech/tags/compute.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [long-running](<https://devfeed.tech/tags/long-running.md>), [prisma](<https://devfeed.tech/tags/prisma.md>), [ptp](<https://devfeed.tech/tags/ptp.md>), [time-synchronization](<https://devfeed.tech/tags/time-synchronization.md>), [wall-clock-time](<https://devfeed.tech/tags/wall-clock-time.md>)

### AI overview

This article explains how Prisma Compute maintains wall-clock accuracy in long-running applications running in Firecracker microVMs. It discusses clock handling during snapshot restore, partial support for restore detection, and measured drift in VMs that remain awake.

### Source excerpt

How Prisma Compute keeps wall-clock time accurate in long-running Firecracker microVMs, using the host-paired KVM PTP clock instead of an in-guest NTP daemon.

## AWS debuts Lambda MicroVMs with up to 8 hours runtime

DevFeed: [AWS debuts Lambda MicroVMs with up to 8 hours runtime](<https://devfeed.tech/articles/aws-debuts-lambda-microvms-with-up-to-8-hours-runtime-47911.md>)

Original publisher: [Read original article](<https://www.devclass.com/devops/2026/06/24/aws-debuts-lambda-microvms-with-up-to-8-hours-runtime/5260139>)

Author: Tim Anderson

Published: 2026-06-24T12:04:00Z

Content type: news

Language: en

Sources: [DevClass.com](<https://devfeed.tech/sources/devclass-com.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [container](<https://devfeed.tech/topics/container.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>), [Bug Bounty](<https://devfeed.tech/topics/bugbounty.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [compute](<https://devfeed.tech/tags/compute.md>), [containers](<https://devfeed.tech/tags/containers.md>), [core](<https://devfeed.tech/tags/core.md>), [devops](<https://devfeed.tech/tags/devops.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [graviton](<https://devfeed.tech/tags/graviton.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [linux](<https://devfeed.tech/tags/linux.md>), [making](<https://devfeed.tech/tags/making.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [virtual](<https://devfeed.tech/tags/virtual.md>), [virtual-machine](<https://devfeed.tech/tags/virtual-machine.md>)

### AI overview

AWS introduced Lambda MicroVMs, built on Firecracker, to run isolated Linux containers for up to eight hours. The feature supports workloads such as code isolation, vulnerability scanning, CI/CD, and AI-agent execution, with suspend-and-resume behavior and consumption-based pricing.

### Source excerpt

AWS has introduced Lambda MicroVMs, built on its Firecracker virtual machine monitor, which can run ...

## Run Claude Managed Agents with Vercel Sandbox

DevFeed: [Run Claude Managed Agents with Vercel Sandbox](<https://devfeed.tech/articles/run-claude-managed-agents-with-vercel-sandbox-1074.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/run-claude-managed-agents-with-vercel-sandbox>)

Author: Allen Zhou

Published: 2026-05-18T23:01:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Claude](<https://devfeed.tech/topics/claude.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Security](<https://devfeed.tech/topics/security.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [claude](<https://devfeed.tech/tags/claude.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [security](<https://devfeed.tech/tags/security.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Sandbox now supports Claude Managed Agents, combining Anthropic's managed agent loop with self-hosted execution on Vercel infrastructure. Each session runs in an isolated Firecracker microVM with firewall-based credential brokering, deny-by-default egress, and low-latency access to private networks and cloud workloads.

### Source excerpt

You can now run Claude Managed Agents with Vercel Sandbox. Claude Managed Agents handles the model, harness, tools, and session state. Self-hosting lets you bring the execution environment, so an agent's tool calls run on your existing Vercel infrastructure with your private APIs, internal services, and customer data. Each agent session runs in its own isolated Firecracker microVM, using the same infrastructure that powers 1B+ Vercel deployments with enterprise-grade security, availability, and performance. What you get: A managed agent loop from Anthropic, including the model, harness, tools, and session state A Vercel function control plane that spawns a sandbox per session Firecracker microVM isolation per session, with millisecond startup Credential brokering at the firewall, so secrets never enter the sandbox Deny-by-default egress with a domain allowlist Low-latency connectivity to your private network and cloud workloads Follow the step-by-step guide for a reference implementation and learn more in the Vercel Sandbox docs. Read more

## Seven Years of Firecracker

DevFeed: [Seven Years of Firecracker](<https://devfeed.tech/articles/seven-years-of-firecracker-12577.md>)

Original publisher: [Read original article](<http://brooker.co.za/blog/2025/09/18/firecracker.html>)

Author: Marc Brooker

Published: 2025-09-18T00:00:00Z

Content type: article

Language: en

Sources: [Marc Brooker's](<https://devfeed.tech/sources/marc-brooker-s-blog.md>)

Topics: [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Multi-tenancy](<https://devfeed.tech/topics/multi-tenancy.md>)

Tags: [2018](<https://devfeed.tech/tags/2018.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [containers](<https://devfeed.tech/tags/containers.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [multitenancy](<https://devfeed.tech/tags/multitenancy.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-software](<https://devfeed.tech/tags/open-source-software.md>), [paper](<https://devfeed.tech/tags/paper.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

The article describes two AWS uses of Firecracker beyond Lambda. In Bedrock AgentCore Runtime, each agent session runs in its own MicroVM, which is destroyed when the session ends (up to eight hours), clearing session context; this session-based isolation suits agents' varied workloads. In Aurora DSQL, each transaction runs in a Query Processor with its own PostgreSQL copy. Firecracker snapshots let AWS restore prepared VMs much faster than booting and starting the software each time. Clones can share unchanged memory pages, reducing memory use while written pages remain private. For DSQL, VMs are terminated after a fixed period to clear accumulated memory, instead of Linux-style cold-page tracking; the approach works because connection handling, caching, and concurrency control sit outside the Query Processor. The text also notes that cloning requires additional handling for features such as random numbers.

### Source excerpt

Seven Years of Firecracker Time flies like an arrow. Fruit flies like a banana. Back at re:Invent 2018, we shared Firecracker with the world. Firecracker is open source software that makes it easy to create and manage small virtual machines. At the time, we talked about Firecracker as one of the key technologies behind AWS Lambda, including how it'd allowed us to make Lambda faster, more efficient, and more secure. A couple years later, we published Firecracker: Lightweight Virtualization for Serverless Applications (at NSDI'20). Here's me talking through the paper back then: The paper went into more detail into how we're using Firecracker in Lambda, how we think about the economics of multitenancy (more about that here), and how we chose virtualization over kernel-level isolation (containers) or language-level isolation for Lambda. Despite these challenges, virtualization provides many compelling benefits. From an isolation perspective, the most compelling benefit is that it moves the security-critical interface from the OS boundary to a boundary supported in hardware and comparatively simpler software. It removes the need to trade off between kernel features and security: the guest kernel can supply its full feature set with no change to the threat model. VMMs are much smaller than general-purpose OS kernels, exposing a small number of well-understood abstractions without compromising on software compatibility or requiring software to be modified. Firecracker has really taken off, in all three ways we hoped it would. First, we use it in many more places inside AWS, backing the infrastructure we offer to customers across multiple services. Second, folks use the open source version directly, building their own cool products and businesses on it. Third, it was the motivation for a wave of innovation in the VM space. In this post, I wanted to write a bit about two of the ways we're using Firecracker at AWS that weren't covered in the paper. Bedrock AgentCore Back in J

## Preview: Slice Up Bare-Metal with Slicer

DevFeed: [Preview: Slice Up Bare-Metal with Slicer](<https://devfeed.tech/articles/preview-slice-up-bare-metal-with-slicer-26646.md>)

Original publisher: [Read original article](<https://blog.alexellis.io/slicer-bare-metal-preview/>)

Author: Alex Ellis

Published: 2025-08-30T08:09:48Z

Content type: release

Language: en

Sources: [Alex Ellis' Blog](<https://devfeed.tech/sources/alex-ellis-blog.md>)

Topics: [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [OpenFaaS](<https://devfeed.tech/topics/openfaas.md>), [systemd](<https://devfeed.tech/topics/systemd.md>), [Arch Linux](<https://devfeed.tech/topics/archlinux.md>), [Arm](<https://devfeed.tech/topics/arm.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Ollama](<https://devfeed.tech/topics/ollama.md>)

Tags: [arm](<https://devfeed.tech/tags/arm.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [boot](<https://devfeed.tech/tags/boot.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [k3s](<https://devfeed.tech/tags/k3s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network](<https://devfeed.tech/tags/network.md>), [preview](<https://devfeed.tech/tags/preview.md>), [self-hosting](<https://devfeed.tech/tags/self-hosting.md>), [slicer](<https://devfeed.tech/tags/slicer.md>), [storage](<https://devfeed.tech/tags/storage.md>), [systemd](<https://devfeed.tech/tags/systemd.md>), [testing](<https://devfeed.tech/tags/testing.md>), [work](<https://devfeed.tech/tags/work.md>), [x86-64](<https://devfeed.tech/tags/x86-64.md>)

### AI overview

OpenFaaS Ltd is previewing Slicer, an internal tool that partitions bare-metal hosts into Firecracker microVMs. The article describes use cases including Kubernetes cluster scaling, customer simulations, chaos testing, production troubleshooting, Arm and x86_64 testing, persistent workloads, multi-host deployments, and GPU access for Ollama.

### Source excerpt

The easiest and best supported way to learn and deploy Firecracker and microVMs.

## Intel N100 Mini PC for R&D and Self-Hosting Compared with Raspberry Pi 5

DevFeed: [Intel N100 Mini PC for R&D and Self-Hosting Compared with Raspberry Pi 5](<https://devfeed.tech/articles/i-bought-an-n100-mini-pc-then-another-26645.md>)

Original publisher: [Read original article](<https://blog.alexellis.io/n100-mini-computer/>)

Author: Alex Ellis

Published: 2025-08-18T08:09:48Z

Content type: opinion

Language: en

Sources: [Alex Ellis' Blog](<https://devfeed.tech/sources/alex-ellis-blog.md>)

Topics: [pc](<https://devfeed.tech/topics/pc.md>), [intel](<https://devfeed.tech/topics/intel.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Raspberry Pi](<https://devfeed.tech/topics/raspberry-pi.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [k3s](<https://devfeed.tech/topics/k3s.md>), [OpenFaaS](<https://devfeed.tech/topics/openfaas.md>), [ddr5](<https://devfeed.tech/topics/ddr5.md>)

Tags: [ddr5](<https://devfeed.tech/tags/ddr5.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [intel](<https://devfeed.tech/tags/intel.md>), [k3s](<https://devfeed.tech/tags/k3s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [m-2-nvme](<https://devfeed.tech/tags/m-2-nvme.md>), [mini-pc](<https://devfeed.tech/tags/mini-pc.md>), [pc](<https://devfeed.tech/tags/pc.md>), [processor](<https://devfeed.tech/tags/processor.md>), [self-hosting](<https://devfeed.tech/tags/self-hosting.md>), [storage](<https://devfeed.tech/tags/storage.md>), [threads](<https://devfeed.tech/tags/threads.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The article evaluates the low-power Intel N100 Mini PC for R&D and self-hosting, comparing it with the Raspberry Pi 5. It discusses CPU, RAM, NVMe storage, Ethernet, virtualization, Kubernetes, Firecracker, and cost considerations.

### Source excerpt

Exploring the capabilities of the Intel N100 Mini PC for work and self-hosting as an alternative to public cloud.

## Decomposing Aurora DSQL

DevFeed: [Decomposing Aurora DSQL](<https://devfeed.tech/articles/decomposing-aurora-dsql-12571.md>)

Original publisher: [Read original article](<http://brooker.co.za/blog/2025/04/17/decomposing.html>)

Author: Marc Brooker

Published: 2025-04-17T00:00:00Z

Content type: article

Language: en

Sources: [Marc Brooker's](<https://devfeed.tech/sources/marc-brooker-s-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [availability](<https://devfeed.tech/tags/availability.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [replication](<https://devfeed.tech/tags/replication.md>), [systems](<https://devfeed.tech/tags/systems.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

The article explains Aurora DSQL by decomposing transaction processing into execution, ordering, validation, and persistence. It describes PostgreSQL-powered query processors isolated with Firecracker, parallel ordering and validation by adjudicators, and durable replication across availability zones or regions before changes are applied for read visibility.

### Source excerpt

Decomposing Aurora DSQL Riffing, I guess. Earlier today, Alex Miller wrote an excellent blog post titled Decomposing Transaction Systems. It's one of the best things I've read about transactions this year, maybe the best. You should read it now. In the post, Alex breaks transactions down like this: Every transactional system does four things: It executes transactions. It orders transactions. It validates transactions. It persists transactions. then describes how these steps map to traditional OCC and PCC systems, research designs like Calvin, and real-world systems like FoundationDB. How do these steps map to Aurora DSQL? An overview of DSQL's architecture may be useful if you haven't been following along so far: Now, an hour of video and 20 minutes of reading another post later, we're back. Let's dive in. Executing a transaction means evaluating the body of the transaction to produce the intended reads and writes. Aurora DSQL executes transactions on a horizontally scalable fleet of Firecracker-isolated, PostgreSQL-powered, query processors. At this stage there's no coordination at all. MVCC is used for reads during execution, and no writes escape the query processor running that particular transaction. See this post for more on this step. Ordering a transaction means assigning the transaction some notion of a time at which it occurred. Validating a transaction means enforcing concurrency control, or more rarely, domain-specific semantics. In DSQL, ordering and validating happen in parallel, done by the adjudicators involved in the transaction. Each adjudicator provides a range of possible orderings (not after, not before), and one final adjudicator makes the final ordering decision. Similarly, each involved adjudicator weighs in on validation, with one final adjudicator checking that everybody says yes. Strictly, the final-final order is chosen only after validation completes, but the ordering and validation protocols run in parallel. See this post for more. Persi

## How to run Firecracker without KVM on cloud VMs

DevFeed: [How to run Firecracker without KVM on cloud VMs](<https://devfeed.tech/articles/how-to-run-firecracker-without-kvm-on-cloud-vms-26643.md>)

Original publisher: [Read original article](<https://blog.alexellis.io/how-to-run-firecracker-without-kvm-on-regular-cloud-vms/>)

Author: Alex Ellis

Published: 2025-02-12T09:05:21Z

Content type: article

Language: en

Sources: [Alex Ellis' Blog](<https://devfeed.tech/sources/alex-ellis-blog.md>)

Topics: [Firecracker](<https://devfeed.tech/topics/firecracker.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [amd](<https://devfeed.tech/tags/amd.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-ec2](<https://devfeed.tech/tags/aws-ec2.md>), [azure](<https://devfeed.tech/tags/azure.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [digital-ocean](<https://devfeed.tech/tags/digital-ocean.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [geekbench](<https://devfeed.tech/tags/geekbench.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [hetzner](<https://devfeed.tech/tags/hetzner.md>), [intel](<https://devfeed.tech/tags/intel.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [kvm](<https://devfeed.tech/tags/kvm.md>), [linux](<https://devfeed.tech/tags/linux.md>), [nested](<https://devfeed.tech/tags/nested.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>), [virtualisation](<https://devfeed.tech/tags/virtualisation.md>)

### AI overview

The excerpt introduces PVM as a way to run Firecracker and other microVMs on x86_64 cloud VMs without KVM or nested virtualization. It frames PVM as an alternative for users whose cloud provider does not offer nested virtualization, or whose bare-metal options are too costly. The author says PVM works on any x86_64 cloud VM and is packaged for SlicerVM.com. As a cost comparison, the excerpt gives Hetzner server prices of about $100-$200 per month and an AWS M7i.metal-24xl on-demand price of $3,532 per month, excluding storage and bandwidth. The excerpt cuts off as the "Firecracker without KVM" section begins, so it does not provide the mechanism or setup steps.

### Source excerpt

MicroVMs need bare-metal or nested virtualisation with /dev/kvm. But what if that's not available? The PVM virtualisation framework may be the answer.

## DSQL Vignette: Reads and Compute

DevFeed: [DSQL Vignette: Reads and Compute](<https://devfeed.tech/articles/dsql-vignette-reads-and-compute-12564.md>)

Original publisher: [Read original article](<http://brooker.co.za/blog/2024/12/04/inside-dsql.html>)

Author: Marc Brooker

Published: 2024-12-04T00:00:00Z

Content type: article

Language: en

Sources: [Marc Brooker's](<https://devfeed.tech/sources/marc-brooker-s-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Database](<https://devfeed.tech/topics/database.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Firecracker](<https://devfeed.tech/topics/firecracker.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [database](<https://devfeed.tech/tags/database.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [firecracker](<https://devfeed.tech/tags/firecracker.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

This article examines the architecture behind Aurora DSQL, focusing on SQL execution and transactional reads. It explains how DSQL independently scales compute, read throughput, write throughput, and storage by disaggregating storage from compute, and describes its dynamically scalable SQL execution layer. The article also discusses lessons from AWS Lambda and the use of Firecracker MicroVMs running customized Postgres engines for transactions.

### Source excerpt

DSQL Vignette: Reads and Compute The easy half of a database system? In today's post, I'm going to look at half of what's under the covers of Aurora DSQL, our new scalable, active-active, SQL database. If you'd like to learn more about the product first, check out the official documentation, which is always a great place to go for the latest information on Aurora DSQL, and how to fit it into your architecture. Today, we're going to focus on running SQL and doing transactional reads. But first, let's talk scalability. One of the most interesting things in DSQL's architecture is that we can scale compute (SQL execution), read throughput, write throughput, and storage space independently. At a fundamental level, scaling compute in a database system requires disaggregation of storage and compute. If you stick storage and compute together, you end up needing to scale one to scale the other, which is either impossible or uneconomical. That's why, when we launched Aurora 10 years ago (nearly to the day!) we chose an architecture which separated compute and storage (from Amazon Aurora: Design Considerations for High Throughput Cloud-Native Relational Databases, SIGMOD'17): As the paper says: We use a novel service-oriented architecture (see Figure 1) with a multi-tenant scale-out storage service that abstracts a virtualized segmented redo log and is loosely coupled to a fleet of database instances. In DSQL, we took this pattern one step further: we changed the interface between the SQL executor and storage to remove the need for a large local cache1 right next to the SQL engine. With that out of the way, we could build a new scalable SQL execution layer which can dynamically scale to meet the needs of nearly any workload. Compute Scale: Lessons from Lambda Aurora wasn't the only big launch at re:Invent 2014. Another big one was AWS Lambda2. AWS Lambda brought a new compute scalability model: the ability to scale up efficiently in small units, each with a single well-defined

[Next page](<https://devfeed.tech/topics/firecracker.md?cursor=WyIyMDI0LTEyLTA0VDAwOjAwOjAwKzAwOjAwIiwgImQyMzQwZDYzLTgyNDItNDhjZi04MmQ3LTQyMDlmMjM3YWEwMCJd>)