One CreateOS API key, stored once as an org-owned secret in Omnara.
The provider ships inside Omnara, so a team installs nothing to use it.
Written by NodeOps, reviewed and merged by Omnara into its open-source repository.
Every agent gets its own CreateOS machine, with its own kernel and network identity.
Bring Your Own Machines
Omnara handles the agent loop, execution and state. The machines the agents run on come from pool providers, and each team connects its own account with whichever provider it uses.
For CreateOS to be one of them, the provider had to live inside Omnara's code, so that a team could choose it from the same pool dialog as every other provider, with nothing extra to install.
From API Key to Running Agent
- Create a CreateOS API key. In the CreateOS dashboard, under Profile Settings and API Keys. Omnara stores it as an org-owned secret, not on anyone's laptop.
- Choose a shape and a root filesystem. The shape sets each machine's CPU and memory, for example s-2vcpu-4gb. devbox:1 already carries Python, Node.js, Bun, Go, Rust and Docker; a team with its own toolchain builds a template from a Dockerfile once and uses that instead.
- Create the pool. On Omnara's Machines page, New pool, then CreateOS: the credential, shape, root filesystem and capacity limits.
From then on Omnara provisions machines through the CreateOS API as its agents need them. With sleep turned on through Omnara's API, an idle machine pauses as a snapshot of its memory, processes and disk, and resumes in place when an agent needs it again, with no cold boot and no setup to run twice.
One API key. Machines, New pool, CreateOS.
The whole integration, as the joint launch put it.
Shipped Into Omnara's Own Code
NodeOps wrote the CreateOS provider and opened it against Omnara's open-source repository in September 2026. Omnara's team reviewed it and merged it on October 6, and Omnara's changelog announced CreateOS as a new sandbox provider the next day, with its own setup page in Omnara's docs.
The two teams launched the integration together on October 27, on X and LinkedIn. The CreateOS docs carry the same setup from our side, with the pool fields, environment limits and a demo of an agent running on a CreateOS machine.
Highlights
- CreateOS is a built-in machine pool provider in Omnara, the open-source platform for running managed agents.
- Setup is one API key: store it in Omnara as an org secret, then Machines, New pool, CreateOS.
- NodeOps wrote the provider and Omnara merged it into its own repository on October 6, 2026. Omnara's changelog announced it the next day.
- Each agent runs on its own CreateOS machine with its own kernel, booted from devbox:1 or a team's own template.
About Omnara
Omnara is an open-source platform for running managed agents. It handles execution and state, and teams choose the models, tools and machines. It is Apache-2.0 licensed and runs self-hosted or as Omnara Cloud.
Machines come from pool providers that a team connects with its own account. CreateOS joined that list in October 2026, alongside providers such as Daytona, Modal and Unikraft Cloud.
