Hardware isolation
One microVM per run, its own kernel, nothing shared.
01$ Sandboxed execution for untrusted code
$ onyx777 --init
MicroVM isolation with a narrow syscall surface and a clock that cannot be read.
# install npx onyx777 init --policy default ✓ connected · 9 ms warm start ✓ first run recorded
Overview
Runs
Policies
Traces
Settings
Sandboxedlive
41kagent snippets, zero escapes
9 mswarm start
Hardware isolationok
Egress deny by defaultok
9 ms warm startok
Teams shipping with Onyx777
NorthwindKestrelRuangPolarTokoLumenBakauVela
Inside the product
One screen, the whole picture.
Overview
Runs
Policies
Traces
Settings
Sandboxedlive
41kagent snippets, zero escapes
9 mswarm start
Hardware isolationok
Egress deny by defaultok
9 ms warm startok
What you get
Three things Onyx777 does properly.
Egress deny by default
A run talks to nothing until you say what it may reach.
029 ms warm start
A pool keeps the cold path off your critical path.
0341kagent snippets, zero escapes
9 mswarm start
120 mscold start
“We run code we did not write, from a model we do not control. This is the only reason we sleep.”
Raka A. — founder, Jakarta
Pricing
Start free. Pay when it earns it.
Questions
The things people ask first.
Which languages?+
Any OCI image. Python, Node and Go images are prebuilt.
How do you prevent escapes?+
MicroVM boundary plus seccomp; the network is off unless allowed.
Can I keep state?+
Per-run disk is ephemeral by default; snapshots are opt-in.
Onyx777 is open for design partners.
Small team, direct access to the people who build it. Bring a real workload.
Request access