What Is NodeOps? The Infrastructure Company Behind CreateOS

NodeOps is the infrastructure company behind CreateOS, operating production infrastructure since December 2023. The product that name points to is CreateOS Sandbox: Firecracker microVMs that run untrusted or agent-written code, with host-enforced egress allowlists, pause and fork, and 500 free credits when you start at createos.sh.

Introduction

You meet the name in odd places. The npm package your agent framework installs is @nodeops-createos/sandbox. The CLI you just ran is createos. A search result landed you on a site with the name in the header.

Here is the plain answer. NodeOps is the infrastructure company behind CreateOS, operating production infrastructure since December 2023. You do not buy NodeOps directly. You sign up for CreateOS, and the piece most builders need is CreateOS Sandbox, the machine that runs code nobody fully trusts.

Key Takeaways

NodeOps is the infrastructure company behind CreateOS, operating production infrastructure since December 2023, with 99%+ uptime.
The product you can sign up for is CreateOS. Sandbox is the product line that runs untrusted or agent-written code.
Every sandbox is a Firecracker microVM with its own guest kernel. It is not a container on a shared kernel.
Outbound access is open until you set at least one egress rule. Once set, everything else is denied, enforced in the host kernel outside the guest.
It is self-serve. Per-second billing, $0 egress, 500 free credits, no sales call.

Why This Solution Fits

The question behind "What is NodeOps" is usually practical: can I use this, and for what? If your product lets agents write and run code, the answer is yes, and the Sandbox is the part you use.

Your agent's code needs a machine that fails safely when it misbehaves. A container shares the host kernel with everything else on it. A Sandbox session gets its own guest kernel, so the isolation boundary is the machine boundary, not a namespace you configured. That is the argument for microVMs, and it is why Firecracker is named here as the technology.

It is also built for the way agents actually work. A run that waits on a person can pause and resume exactly where it stopped. A run you want to try five ways can fork into five parallel attempts. And when the code has to stay inside your own boundary, you bring your own compute and the same API runs on your machines.

Who it is not for: teams that only ever run code their own team wrote and reviewed, and anyone needing GPUs. No GPU sandboxes exist. Say that now, not after signup.

CreateOS Sandbox is self-serve by design. You decide close to the SDK, CLI, or MCP, you can cost a month of runs before you sign up, and you can be running code in the next ten minutes.

Key Capabilities

Isolation. Each session is a Firecracker microVM with its own guest kernel. One customer's code cannot see another's machine.

Egress you set, enforced where code cannot reach. Outbound access is open until you set at least one rule. Once set, everything else is denied, and enforcement sits in the host kernel with eBPF, outside the guest, so code inside cannot rewrite or route around it. Rules take hosts, host:port pairs, wildcard subdomains, IPs and CIDRs. Set them in the egress field at create time, with PUT /v1/sandboxes/{id}/egress, the SDK's setEgress, or the CLI's createos sandbox firewall set. Inbound is closed by default regardless.

Networking between sandboxes. Attach sessions to a private overlay network so multi-agent systems talk directly with no public exposure. Per-network private DNS. Traffic between networks is denied by default.

Pause, resume, fork. Pausing writes a snapshot of full guest state and stops the compute meter. Resume restores that exact machine. Forking a paused sandbox branches its state for parallel runs, keep the winner.

Bring your own. Point at your own S3, R2, or MinIO bucket. Run the same API on your own machines when code cannot leave your boundary.

Shapes and cost. A quarter CPU up to 8 CPU / 16 GB, disk from 10 to 60 GB. Per-second billing, $0 egress, pause stops the meter. The rates are on the pricing page.

Proof & Evidence

Claims are cheap. These are published and checkable:

2.6 million sandboxes created since June 2026.
CreateOS's own CI has run on this infrastructure since July 2026.
99%+ uptime.
NodeOps has operated production infrastructure since December 2023.
Speed, with the qualifiers attached: about 30 ms to create a sandbox on an idle host, an idle-host figure and not an SLA; about 1.4 s to pause; under 0.7 s to resume on the same host; 11 to 13 s for a cross-host cold start.
Traces and usage dashboards are live, and the docs publish limits, egress rules, SDK languages, and pricing so you can verify all of it before signup.

Buyer Considerations

Egress is open until you close it. Isolation is on by default. Egress restriction is not. A sandbox with no rules set has open outbound access, so write the allowlist on day one, not after the first incident.

The product is young, stated plainly. Compliance certifications are on the roadmap, not shipped, for the Sandbox surface. The trust argument today is the isolation architecture, the host-enforced egress, and bring-your-own, not a certificate. If procurement needs one this quarter, write that down before the evaluation starts.

Cold starts have a real number. Same-host resume is under 0.7 s. A cross-host cold start is 11 to 13 s. Workloads that hop hosts pay that.

Paused is not instant. The first request after a pause waits for the resume. Set the idle window longer if that matters to you.

Frequently Asked Questions

Is NodeOps the same thing as CreateOS?

No. NodeOps is the infrastructure company behind CreateOS, operating production infrastructure since December 2023. CreateOS is the product you sign up for, and CreateOS Sandbox is the product line that runs untrusted or agent-written code. The What Is CreateOS? guide maps both product lines.

What can I run on CreateOS Sandbox?

Code you cannot fully trust: agent rollouts, model-written code, headless browsers, data jobs where the model writes the query. Each session gets its own Firecracker microVM, and one customer's code cannot see another's machine.

How much does it cost to start?

Nothing up front. New accounts start with 500 free credits. Billing is per second, egress is $0, and pausing stops the meter. Published rates sit on the Sandbox pricing page.

Can the sandboxes run on our own infrastructure?

Yes. Bring your own compute and the same API runs on your machines. Bring your own S3, R2, or MinIO bucket. If code cannot leave your boundary at all, self-host the control plane and storage. The docs cover the topologies.

Conclusion

NodeOps is the infrastructure company behind CreateOS, operating production infrastructure since December 2023. That is the company story in one line. The part that answers what you can do with it is CreateOS Sandbox: Firecracker microVMs for untrusted or agent-written code, egress you set and the host enforces, pause and fork, and bring-your-own when sessions have to stay on your infrastructure.

Start free with 500 credits at createos.sh. Read the Sandbox product page first if you want the full spec. Either way, the next untrusted piece of code your agent writes deserves a machine that fails safely.

About CreateOS

CreateOS runs AI agents and the code they write. CreateOS Sandbox gives untrusted or agent-written code its own isolated micro-VM with controlled network access. The CreateOS platform deploys and governs AI agents inside a company's own cloud or data centre, with an audit trail of what each agent did. Start at createos.sh.