
A workload for every user.
Ready in 60 to 90 seconds.
Your team picks a template your admins set up, clicks Launch, and gets a running workload in the browser, with or without a GPU. There’s no YAML to write and no ticket to file.


From catalog to connected, in the browser.
Pick a template, launch it, connect, and share. Every step happens in a tab on your own domain.





Desktops, Jupyter, web IDEs, coding agents, and Windows VMs, on CPU or GPU. Your admins set them up once.
Pick a template and click Launch. Your admin already sized it, so there’s no ticket.
This clip runs faster than real time. A real launch takes 60 to 90 seconds with a pre-pulled image.
Every session in one table, with Connect one click away.
Teammates watch your session live, and you can hand them the controls.





Desktops, Jupyter, web IDEs, coding agents, and Windows VMs, on CPU or GPU. Your admins set them up once.
Pick a template and click Launch. Your admin already sized it, so there’s no ticket.
This clip runs faster than real time. A real launch takes 60 to 90 seconds.
Every session in one table, with Connect one click away.
Teammates watch your session live, and you can hand them the controls.





Desktops, Jupyter, web IDEs, coding agents, and Windows VMs, on CPU or GPU. Your admins set them up once.
Pick a template and click Launch. Your admin already sized it, so there’s no ticket.
This clip runs faster than real time. A real launch takes 60 to 90 seconds.
Every session in one table, with Connect one click away.
Teammates watch your session live, and you can hand them the controls.
Stop waiting hours for compute.
One catalog, every workload
Desktops, Jupyter, web IDEs, coding agents, and Windows VMs, with or without a GPU, all launched the same way.
One catalog, every workload
Desktops, Jupyter, web IDEs, coding agents, and Windows VMs, with or without a GPU, all launched the same way.
One catalog, every workload
Desktops, Jupyter, web IDEs, coding agents, and Windows VMs, with or without a GPU, all launched the same way.
More sessions per GPU
Time-slicing shares one GPU across several container sessions. It needs no MIG partitioning and no vGPU license, so you pack more work onto the cards you already have.
More sessions per GPU
Time-slicing shares one GPU across several container sessions. It needs no MIG partitioning and no vGPU license, so you pack more work onto the cards you already have.
More sessions per GPU
Time-slicing shares one GPU across several container sessions. It needs no MIG partitioning and no vGPU license, so you pack more work onto the cards you already have.
Collaborate live
Invite teammates into a running session. They watch your screen live, and you can hand the controls to anyone you choose, like pulling a chair up to the same desk.
Collaborate live
Invite teammates into a running session. They watch your screen live, and you can hand the controls to anyone you choose, like pulling a chair up to the same desk.
Collaborate live
Invite teammates into a running session. They watch your screen live, and you can hand the controls to anyone you choose, like pulling a chair up to the same desk.
Idle options
Idle workloads can hibernate, which stops them and hands their compute back, or shut down on a timer. Your admins choose which.
Idle options
Idle workloads can hibernate, which stops them and hands their compute back, or shut down on a timer. Your admins choose which.
Idle options
Idle workloads can hibernate, which stops them and hands their compute back, or shut down on a timer. Your admins choose which.
Any connection
Desktops over Selkies or DCV, plus license servers, game servers, and anything else on HTTP, TCP, or UDP.
Any connection
Desktops over Selkies or DCV, plus license servers, game servers, and anything else on HTTP, TCP, or UDP.
Any connection
Desktops over Selkies or DCV, plus license servers, game servers, and anything else on HTTP, TCP, or UDP.
Your files, owned by you
Every workload runs as your own POSIX UID and GID, with your mounts.
Your files, owned by you
Every workload runs as your own POSIX UID and GID, with your mounts.
Your files, owned by you
Every workload runs as your own POSIX UID and GID, with your mounts.
“The agent Kindwell built doesn’t just save us time, it changed what’s actually possible for our team in a given week.”
TETIANA KUDRIA · UNDERSUN PREMIUM SUPPLIERS, BUILT BY KINDWELL ON ORION
<4 min
to provision an environment, down from 2 to 3 days · Undersun via Kindwell
9 days
full engagement, down from an estimated 15 to 18 · Undersun via Kindwell
Questions users ask
Do I need a GPU?
+
Do I need a GPU?
No. Plenty of templates run on CPU only. Your admins decide which templates get a GPU and how much of one.
Do I need a GPU?
+
Do I need a GPU?
No. Plenty of templates run on CPU only. Your admins decide which templates get a GPU and how much of one.
Do I need a GPU?
+
Do I need a GPU?
No. Plenty of templates run on CPU only. Your admins decide which templates get a GPU and how much of one.
How fast is a workload ready?
+
How fast is a workload ready?
60 to 90 seconds with a cached image. A first launch that pulls a new image takes a few minutes.
How fast is a workload ready?
+
How fast is a workload ready?
60 to 90 seconds with a cached image. A first launch that pulls a new image takes a few minutes.
How fast is a workload ready?
+
How fast is a workload ready?
60 to 90 seconds with a cached image. A first launch that pulls a new image takes a few minutes.
Can two people work in one session?
+
Can two people work in one session?
Yes. Invite a teammate to watch or take control from the workloads table.
Can two people work in one session?
+
Can two people work in one session?
Yes. Invite a teammate to watch or take control from the workloads table.
Can two people work in one session?
+
Can two people work in one session?
Yes. Invite a teammate to watch or take control from the workloads table.
What happens when I walk away?
+
What happens when I walk away?
Idle workloads can hibernate or shut down on a timer your admin sets, and you get a warning first. Hibernating stops the workload and frees its compute. Whether its state is kept depends on how your cluster is configured.
What happens when I walk away?
+
What happens when I walk away?
Idle workloads can hibernate or shut down on a timer your admin sets, and you get a warning first. Hibernating stops the workload and frees its compute. Whether its state is kept depends on how your cluster is configured.
What happens when I walk away?
+
What happens when I walk away?
Idle workloads can hibernate or shut down on a timer your admin sets, and you get a warning first. Hibernating stops the workload and frees its compute. Whether its state is kept depends on how your cluster is configured.
Do my files stay?
+
Do my files stay?
Yes. Your mounts stay, owned by your own UID and GID.
Do my files stay?
+
Do my files stay?
Yes. Your mounts stay, owned by your own UID and GID.
Do my files stay?
+
Do my files stay?
Yes. Your mounts stay, owned by your own UID and GID.
KEEP GOING

Give your team self-serve compute today.
Book a 30-minute demo with an engineer, or install Community Edition and read the docs.

Give your team self-serve compute today.
Book a 30-minute demo with an engineer, or install Community Edition and read the docs.

Give your team self-serve compute today.
Book a 30-minute demo with an engineer, or install Community Edition and read the docs.