Moat Roadmap
Single-node isolation, MCP integration, and production hardening ship today under the MIT License. Here is what is built and what comes next.
Shipped
v0
Isolation Engine
ShippedThe Firecracker + KVM control plane, proven on real microVMs.
- microVM lifecycle with
jailerconfinement, per-VM netns,/30IPAM, strictpolicy dropnftables, and cgroup v2 + disk/NIC rate limiters - Read-only rootfs + ephemeral ext4 overlayfs scratch disks (
read_only_root) or private sparse/reflink copies - PID 1 guest agent over vsock: streamed exec with PTY & timeouts, byte-exact file transfer, zombie reaper, overlayfs pivot, and post-restore clock resync
- Full & diff snapshots,
moat-uffduserfaultfd demand paging, per-template cold or snapshot-backed warm pools, TTL/idle reaper, and startup orphan reconciliation
M1
Self-Serve Agent Sandbox
ShippedInstall in one command and point any MCP coding agent at Moat safely.
- Ingress secret firewall using vendored Gitleaks rules (
409block by default, audited override, optional-secret-redact) moat-mcpstdio MCP server (Unix socket or HTTP/HTTPS) andSKILL.mdplaybookinstall.sh(system and--user),moat doctor,moat template importfor anylinux/amd64OCI image, andmoat uninstall
M2
Audit, Trust & Single-Node Hardening
ShippedTamper-evident accountability, supply-chain trust, and hardened transport.
- Hash-chained, metadata-only JSONL audit log,
moat audit {tail,query,report,verify}, per-sandbox reports, and async SIEM webhook sink - Deterministic, byte-reproducible rootfs builds (
make images-verifyin CI), CycloneDX SBOM, automated Cosign-signed releases, andimages.lockenforcement at startup - Native TLS 1.2+ / mTLS,
0660Unix domain sockets, per-token egress allow/deny policies, and strict HTTP body/header limits
Up Next
M2.5
Single-Node API & Density Polish
PlannedRemaining engine optimizations and API features from the original design.
- Northbound gRPC API & live snapshots: gRPC gateway alongside REST, plus
POST /v1/sandboxes/{id}/snapshotto checkpoint a running sandbox over the API - High-density memory & I/O:
virtio-balloonmemory reclaim for idle sandboxes, cgroup v2io.max, and per-sandbox RSS/vCPU Prometheus gauges - Outbound egress DLP & rate limits: optional credential scanning on outbound proxy traffic and per-sandbox egress request caps
- UFFD fuzzing & host tuning: continuous fuzzing of the
moat-uffdpage-fault path and automatedfs.file-max/ inotify checks inmoat doctor - Optional Rust guest agent:
<3 MiBstatic Rust PID 1 drop-in alternative speaking the sameagent.v1.Agentprotobuf contract
M3
Multi-Node Fleet & Platform Reach
FutureOperating Moat across clusters of bare-metal hosts and broader developer platforms.
- Multi-node fleet control plane (open-core): scheduling across bare-metal hosts, per-team SSO / RBAC, web console, and managed hosting
- GPU workloads: parallel VMM driver backend (Cloud Hypervisor with VFIO or gVisor) since Firecracker has no PCI passthrough
- Reach & SDKs:
arm64Linux support, downloadable template registry (moat template pull), official Python / TypeScript / Go SDKs, and macOS helper-VM / WSL2 guides
Licensing commitment
Moat is licensed under the MIT License. Single-node operation, the daemon, CLI, guest agent, MCP server, and every isolation and audit control are free forever — the security boundary is never paywalled.