Solutions

What you can build on a Cube

Every workload below runs on the same thing: a Firecracker microVM with its own kernel and full root access. That is what makes it safe to run code you didn't write — and it still runs your site, your database and your game server.

Launch a Cube Explore the Cube

Cubes from $2.92/moNo credit card to sign up

Own kernel per Cube
Expose only what you want
Billed by the minute

01Isolation-native

When the code isn't yours

Agents, tenants and CI jobs all execute code somebody else wrote. Each of these gets its own kernel inside a per-cube sandbox, so one workload can never reach another.

Multi-tenant platforms

Run user & untrusted code

Give every end-user their own isolated Cube. Each one is a Firecracker microVM with its own kernel, so one tenant's code can never see or reach another's.

See how it works

Agents & code interpreters

Sandboxes for AI agents

Give every AI agent its own disposable computer with full root. Let it install packages, run shell commands, and browse a filesystem — all sealed inside an isolated Cube.

See how it works

GitHub Actions & CI

Self-hosted CI runners

Run GitHub Actions on a microVM you control. The runner only makes outbound connections, so no port is ever exposed — and Krova's own CI runs on one.

See how it works

Containers, done safely

Docker & container workloads

Run Docker and Compose inside a Cube that has its own kernel. Your containers get a full, isolated microVM to live in — not a slice of someone else's host.

See how it works

02Everyday workloads

Your site, your database, your game server

The same machine runs the ordinary things too — with its own kernel, RAM and disk reserved 1:1, and only the ports you open reachable from outside.

Bring your own stack

Self-managed web & app hosting

Run your own web server and stack on a Cube you fully control — full root access, its own kernel, custom domains and automatic HTTPS. This is the self-managed, do-it-yourself route: if you'd rather not administer a server at all, Nest is our managed web-hosting product.

CMS & publishing

WordPress hosting

Run a fast, isolated WordPress site on a Cube with full root. Its own kernel, reserved resources, custom domains, and automatic HTTPS.

JavaScript & TypeScript apps

Node.js & Next.js hosting

Deploy Node.js, Next.js, and other JS/TS apps on a Cube with full control. Any Node version, any process manager, your own domain with automatic HTTPS.

Low-latency multiplayer

Game servers

Run low-latency game servers on a Cube you fully control. Reserved resources, full root, and TCP/UDP ports you open exactly where you want them.

Postgres, MySQL & Redis

Databases

Run Postgres, MySQL, or Redis on an isolated Cube with reserved RAM and disk. Full root, its own kernel, and resources that are never oversold.

03Managed hosting

Just need a website, not a server?

Nest is our managed, cPanel-style web hosting — one-click WordPress, email, automatic SSL and backups, billed from the same wallet as your Cubes. It is a different product from a Cube: no server to administer and no root access, which for most website owners is the entire point.

Explore Nest

04Answers

Frequently asked questions

Is each of these a different product?

No — there is one Cube. Every workload on this page runs on the same Firecracker microVM with its own kernel and full root access. What changes is the size you pick and what you install on it.

Can one Cube run several of these at once?

Yes. You have full root, so a single Cube can run your app, its database and a background worker side by side. Splitting them across separate Cubes buys isolation instead: each one gets its own kernel, and its RAM and disk are reserved 1:1 rather than shared.

How do I know what size to create?

Start small and resize as you go. RAM and disk grow live with no downtime, and vCPU changes with a quick restart. Billing is by the minute, so running a bigger Cube for one afternoon costs you an afternoon.

Can I take my work elsewhere later?

Yes. A Cube is a standard Linux server you administer over SSH, so your stack is not written in anyone's config format. Export any Cube as a portable .cube archive and import it again — your environment is a file you hold.

Pick a workload and launch a Cube

Whatever you picked, it starts the same way — create a Cube, SSH in, and go. Claim $5 in free credit — one-time, per account, and nothing is charged for it.

Launch a Cube See Cube pricing