pick northflank for a managed kubernetes sandbox platform, gpu workloads, and self-serve byoc. [1][3] pick microsandbox for a runtime that starts on a developer machine and embeds in your application.
northflank is a managed platform for sandbox workloads on its cloud or on a connected customer cluster. [1][3] it supplies the surrounding orchestration, placement, networking, storage, and operations that a kubernetes platform team would otherwise assemble.
its isolation model is specific, not generic container hosting. northflank documents kata containers with cloud hypervisor when nested virtualization is available, and gvisor where it is not. [2] its customer-cloud path also documents microvm-enabled node pools and self-serve cluster integration. [3]
microsandbox begins at the application boundary instead. the runtime embeds in your process and starts locally without a cluster. choose northflank when you want the managed platform. choose microsandbox when the same sandbox runtime must begin on the laptop. private beta. access is by request.
microsandbox
local + cloud
northflank
managed sandbox platform on kubernetes [1]
product shape
embeddable local runtime · private beta. access is by request.
managed kubernetes platform with sandbox apis [1]
isolation
hardware-isolated microvm · its own kernel
kata with cloud hypervisor; gvisor where virtualization is unavailable [2]
bring your own cloud
contact us to evaluate running microsandbox inside your own environment.
documented self-serve deployment into supported customer clusters [3]
gpu workloads
gpu sandboxes are not offered today
gpu sandboxes are documented [1]
platform operations
your application owns runtime placement and operations
managed orchestration, placement, networking, storage, and observability [1]
developer laptop
local runtime · no cloud account required
sandboxes run on northflank cloud or a connected customer cluster [3]
license
apache 2.0
managed platform; isolation stack includes kata and gvisor [2]
pick northflank
choose northflank when
you want a managed kubernetes platform around the sandbox api. [1]
you need gpu sandboxes in the same platform. [1]
you want self-serve deployment into a supported customer cloud cluster. [3]
managed placement, networking, storage, and observability are part of the purchase. [1]
pick microsandbox
choose microsandbox when
developers need the real runtime locally without a cluster or account.
your application should embed and own the sandbox lifecycle.
you want the same sdk before choosing a managed deployment path.
one sdk. one api. local or cloud is a config change, not a rewrite.
01
moving from northflank
moving the command loop is straightforward. moving the platform responsibilities is not. northflank supplies kubernetes orchestration, customer-cloud integration, gpu options, storage, and operations around the sandbox. [1][3] list each dependency before replacing the service call with an embedded runtime.
the move fits best when local execution and application-owned lifecycle are the goal. keep northflank where self-serve byoc, gpu capacity, or managed cluster operations are load-bearing.
common questions
is microsandbox a northflank alternative?
yes for applications that need isolated code execution, but the product shape differs. northflank is a managed kubernetes platform. [1] microsandbox is an embeddable, local-first runtime.
does northflank use kata containers or gvisor?
northflank documents kata containers with cloud hypervisor where nested virtualization is available, and gvisor where it is not. [2]
can northflank run in my cloud?
yes. northflank documents a byoc path with sandboxed node pools in supported customer clusters. [3] that is a genuine advantage when self-serve cluster integration is the requirement.
does northflank support gpu sandboxes?
yes. northflank documents gpu sandbox resources. [1] microsandbox does not offer gpu sandboxes today.
which one runs on a developer laptop?
microsandbox runs the actual microvm runtime locally. northflank sandboxes run on its cloud or a connected customer cluster. [1][3]