In development · waitlist open · not intended for production workloads

Environments with a kernel
boundary, not a namespace.

Orkastor Cloud runs each dev and test environment inside its own microVM, with its own guest kernel, on dedicated bare metal. The isolation is the hardware boundary — not a shared kernel with the sharp edges filed off.

Join the waitlist How the boundary works
The boundary

Every environment gets its own kernel.

Most platforms in this space put your code in a container next to everyone else's, sharing one host kernel. That is a namespace, and a namespace is a scheduling construct — it was never designed to hold against code that is actively trying to leave.

01Your process your image, unchanged
02Guest kernel — yours alone not shared with any other tenant
03microVM boundary hardware virtualisation
04Host kernel never reachable from 01
05Dedicated bare metal no hypervisor tenancy underneath

Everything else follows from that line. Your ephemeral Postgres is isolated by the same boundary as your web process — not by a second mechanism bolted on for databases.

What you run

A whole environment, not a container.

Multi-service, one hostname

Frontend, API and a real datastore together. Paths route to services on a single hostname, so your frontend calls /api relative — no CORS, no build-time URL, and the same image works in every environment.

Ephemeral datastores

Postgres, Redis and friends as first-class parts of the environment. Internal-only by default and reachable over a port-forward, because default-credential Postgres on the public internet is the classic incident.

A link you can post

Every environment gets an HTTPS URL, returned immediately so it can go on the pull request before the environment has finished starting. Unlisted and noindex by default.

# bring the image you already build in CI — we never run your build
$ orkastor up --image ghcr.io/acme/web:$GIT_SHA --port 8080

→ https://pr-482-acme-7f3a9c.orkastor.cloud
→ ttl 8h · standard · eu-north-1
What it is not for

The limits, before you hit them.

These are design decisions, not gaps waiting to be filled. Knowing them now is worth more than discovering them at the wrong moment.

Production traffic Environments are ephemeral and expire on a TTL. That is the product, not a limitation of it.
Regulated data Use synthetic or scrubbed fixtures. Nothing here is scoped for personal or regulated records.
Durable storage A microVM's memory is its state, and reclamation takes both. Anything you need to keep, keep elsewhere.
Custom domains & GPU Not in the first version. Environments live on orkastor.cloud subdomains.
Privileged or host access Refused at admission. It is the boundary the whole product rests on.
Status

Being built in the open, and not finished.

Orkastor Cloud is in development. There is no pricing on this page because the measurements the pricing depends on are not finished, and we would rather publish nothing than publish a number twice. There is no availability commitment because there is not yet a service to commit to.

Join the waitlist and we will get in touch when there is something real to try — with its limits stated as plainly as they are here.

Join the waitlist Orkastor