Skip to content
A2LABS // EXPERIMENTAL COMPUTINGLabs 0.9 Preview

The part of the platform allowed to be unfinished.

A2Labs is where ideas live before they earn a product title. Instant browser-based sandboxes, gVisor-isolated container runners, and developer tools that ship before they are polished.

Ephemeral sandboxesgVisor kernel boundaryZero cleanup required
a2labs runtime
bash
a2labs CLI sandbox launchlive telemetry
ACTIVE SANDBOXES

24

Disposable developer containers

SPIN-UP LATENCY

840ms

Pre-warmed cold start time

DEFAULT EXPIRATION

45 min

Auto-purged on inactivity

SANDBOX RUNTIME

gVisor

Hard multi-tenant isolation

ENVIRONMENTS & TOOLS

Pre-configured developer sandboxes

Pick a runtime template, launch it in one click, and receive a browser IDE, root shell, and an outbound HTTPS tunnel.

Instant launch

Runtime

Ephemeral Web Shell

Instant browser terminal with root shell, git, curl, and modern CLI toolchains pre-installed.

Alpine 3.20Launch
Live preview

Fullstack

Node & Next.js Sandbox

Isolated dev container with Node 22, pnpm, and automatic public URL port-forwarding on save.

Node.js 22 LTSLaunch
GPU optional

Data & AI

Python & ML Playground

Zero-install Python runtime with uv, NumPy, FastAPI, and PyTorch ready for quick notebook exploration.

Python 3.12Launch
Isolated daemon

Containers

Disposable Docker Pod

Rootless Docker-in-Docker environment for testing multi-container docker-compose stacks without host risk.

Docker 27Launch
Encrypted tunnel

Networking

Edge Ingress Tunnel

Expose local developer ports to the edge through Cloudflare Anycast tunnels with built-in TLS inspection.

A2Edge ProxyLaunch
Security scan

Security

A2Recon Port Inspector

Reconnaissance and asset discovery sandbox for testing infrastructure exposure on owned IP ranges.

A2Recon 0.4Launch

LIFECYCLE PIPELINE

The lifecycle of an ephemeral sandbox

Four automated phases from provision to teardown — keeping your system clean.

01 // SPAWN

Trigger Sandbox

Request an environment from the panel or CLI with desired CPU & memory specs.

02 // ISOLATE

gVisor Container

Allocated on an in-bom or in-del node with hardened userspace kernel sandbox.

03 // ATTACH

Ingress & Shell

Real-time WebSocket shell is attached, and port 3000 is tunneled to a temp domain.

04 // PURGE

Auto Destruction

When TTL hits zero, the container is destroyed, scratch storage is scrubbed.

THE LABS COVENANT

Explicit rules for experimental software

Being completely transparent about stability trade-offs is fundamental. Here is what you should know before building on A2Labs.

01

Shorter lifetimes by default

Sandboxes expire automatically after 45 minutes unless renewed. Persistence is something you deliberately opt into, not an abandoned machine quietly billing your card.

02

No stability guarantee

Tools here are experiments, not frozen enterprise APIs. Interfaces will evolve, breaking changes ship frequently, and unviable prototypes are decommissioned cleanly.

03

Built & shared in the open

Whenever possible, lab projects and runtimes are published on GitHub so you can audit the container definitions, syscall filters, and networking code before running them.

GET STARTED IN SECONDS

Ready to test an experiment in A2Labs?

Launch an isolated sandbox, run a throwaway workload, and close the browser. No credit card required for standard sandboxes.