QIOI runs persistent Codex, Claude Code, Hermes, and OpenClaw workspaces on isolated machines. Backups run at night. Everything is ready every morning.
Nightly backup
Completed · scope verified
Pre-update snapshot
Taken · rollback ready
Pinned update
Applied within channel
Health checks
All passed
Restore drill
Passed on disposable target
Example report · review build, not a live deployment
Each profile is a versioned, pinned installation on the same recoverable foundation. A profile is offered only when its full lifecycle passes review.
P-01
A persistent coding workspace with projects, Git access, and controlled lifecycle operations.
BoundaryYou connect a supported model account. Model usage is billed by the model provider, not bundled.
P-02
A managed development environment built on the same recoverable workspace foundation.
BoundaryIndependent managed hosting. No vendor partnership or endorsement is implied.
P-03
A persistent agent environment with bounded permissions, monitored services, and pinned updates.
BoundaryExternal actions require explicit permissions and product-specific controls.
P-04
A managed OpenClaw environment with pinned versions, persistent data, and a reviewed recovery path.
BoundaryPlugins, tools, and updates stay limited to supported configurations.
Pick a profile, capacity, and region. The brief records what QIOI would stand up — and what stays under your control.
This brief defines the environment you want. It does not place an order or create cloud resources — provisioning opens with private access.
QIOI is one operating service around your workspace — not an empty virtual private server. This is the system, drawn as it works.
One isolated machine per customer or organization. Every created resource is recorded.
Projects and supported configuration live on storage that survives restarts.
The customer boundary is one dedicated VM. Profile containers stay inside that boundary.
Restart, backup, restore, export, and verified deletion are product operations.
The boundary is the product. Stated plainly, on both sides.
You close the laptop.
The workspace stays on.
Backups, snapshots, pinned updates, health checks — they run in the dark so your morning starts at full speed.
No pagers on your side. It is our job.
Your projects and supported configuration copy to the encrypted backup scope.
The backup is checked against the stated scope. Stated, not implied.
A pre-update snapshot lands. Rolling back stays one operation, not a project.
Updates arrive only through the pinned channel you chose. Nothing surprise-upgrades your workspace.
Lifecycle state is watched all night. If something drifts, it is our pager, not yours.
One backup completed. One snapshot held. One pinned update applied. Zero surprises waiting in your inbox.
One repeatable Codex workspace deployment on one real provider, with backup, restore, export, verified deletion, and recorded cost.
Reviewed private access with Claude Code, Hermes, and OpenClaw profiles added through the same foundation.
Self-service ordering, billing, and workspace controls after operations pass review.
The first stable commercial release, offered only for profiles whose full lifecycle passed review.
Central Europe
First target region
Eastern Canada
Planned next
Provider provisioning, customer accounts, and payment are not connected in this review build. Nothing on this site is a live deployment, an order, or an invoice.