AiloyGitHub

Try to buildwith Ailoy

Agent SDK, built around a sandbox.
Open source, for Python, Node.js and Rust.

Read the docs

Trusted by

  • AWS
  • Gyeonggido Business & Science Accelerator (GBSA)
  • AWS
  • Gyeonggido Business & Science Accelerator (GBSA)
  • AWS
  • Gyeonggido Business & Science Accelerator (GBSA)
  • AWS
  • Gyeonggido Business & Science Accelerator (GBSA)
isolation
microVM
Its own kernel, not a container.
image
Any OCI
Or build one with Recipe steps.
gpu
Vulkan · Metal
Passed through into the VM.
host
Linux · macOS · Windows
Windows natively, no WSL.
daemon
None
No Docker, no background service.

01 · Run

Ask once.It works on its own machine.

One real run of the SAM3 example: it tracked a baby through 99 frames on the GPU, hit an error, fixed it and handed back two files.

/examples/sam3 →
bg-removerLinux microVMGPU · Vulkan/artifacts mounteddone

Remove background baby-turns-around.gif · 99 frames

  1. Read the SAM3 skill /skills/sam3
  2. Opened the GIF 508×640 · 99 frames
  3. Tracked “baby” on the GPU 97/97 frames · 406.6 s
  4. export.py: FileNotFoundError …/obj1/00097.png
  5. Patched it: a frame with no mask gets an empty one
  6. Ran export.py again

Background removed; animation preserved.

baby-no-background.gif3.1 MBbaby-no-background.webp5.2 MB

inside its VM · /artifacts/baby-no-background.webp

waiting for frames…
A replay of a real run, sped up. Tracking took 406.6 s.More examples: CAD, OpenTTD, issue routing →

02 · How it works

The agent runs on your computer.Its work runs in a microVM.

Only what it writes to /artifacts comes back.

/docs →
console = await (    ConsoleClient.builder()    .image(        Recipe("python:3.12-slim-trixie")        .step("… mesa-vulkan-drivers from trixie-backports …")        .step("pip install … ncnn")    )    .mount_readonly("data/ncnn", "/models")    .mount_readonly(skill, "/skills/sam3")    .mount_readonly("context", "/context")    .mount("artifacts", "/artifacts")    .network(True)    .gpu(True)    .build()) agent = await (    ailoy.AgentBuilder("openai/gpt-6-astra")    .instruction(INSTRUCTION)    .system_tools()    .console(console)    .skill("/skills/sam3")    .build()) async with console:    async for output in agent.run("Remove background"):        print(output["message"])
examples/sam3/python/main.py · trimmed →
The agent runs on your computer and calls the model API; its work runs in a microVM with its own Linux kernel; only /artifacts comes back to your disk. model APIopenai, anthropic, …your computer · Linux · macOS · Windowsagentmodel · tools · skill: sam3your own processmodel callsshell · files · imgreadmicroVM · its own Linux kernelpython:3.12-slim-trixie+ mesa-vulkan · ncnn/models · read-only/artifactsGPU · Vulkan, passed throughnothing else on your disk is visible in here./artifacts on your diskbaby-no-background.gif · .webp

The microVM comes from virtx, our open-source runtime: disposable Linux VMs created from code, with no Docker or daemon.

03 · Why a VM

Five ways to run an agent’s work,and where each draws the line.

Compared by category, from each category’s public docs. Where a whole category cannot be pinned down, the cell says so.

Host processOS sandboxContainerHosted sandbox APIAiloy
e.g.an SDK’s local runnerSeatbelt- or Landlock-based toolsDocker, PodmanE2B, Daytona, Modal
Where the work runsyour computeryour computeryour computerthe provider’s cloudyour computer
Boundarynone, or file rules onlypolicy on the host kernelnamespaces on the shared host kernelvaries by providerits own Linux kernel (microVM)
GPU inside the boundaryno boundaryvariespossible, with setupvariesVulkan · Metal, passed through
Host OSanyplatform-specificLinux; a VM on macOS and Windowsany (it is remote)Linux · macOS · Windows
Background servicenonenonea container daemonan API and an accountnone
Fine-grained policynonepolicy language, deny by defaultvariesvariesmounts, network on or off

Read 2026-10-20.↑ another category is ahead here

04 · Roadmap

Local today.The same machine goes further later.

Each step keeps the agent and its machine as one thing you ship.

  1. 1 now

    Local runtime

    Your agent runs in its own microVM on your machine.

  2. 2 planned

    Self-hosted fleet

    The same machine runs on your servers, many at once.

  3. 3 planned

    Managed cloud

    Every agent gets a computer on demand, run by BrekkyLab.

05 · Start

Start with one agentand its machine.