Comfy

RemoteGPU lets you run a managed Comfy workspace directly from the console.

This path is designed for customers who want a hosted application experience instead of managing Kubernetes resources or making raw API calls.

Use this product when

Comfy is best when you want:

• a hosted Comfy workspace managed from the console
• the console to handle the runtime lifecycle
• to avoid managing Deployment, Service, or Ingress resources yourself

How access works

Comfy workspaces are managed from the signed-in console.

You do not need an API key to create or operate a workspace from the UI.

Before you create a workspace

Before you create a workspace:

• open Application / Comfy in the console
• confirm you still have workspace capacity
• choose the GPU size you want to launch with
• choose enough persistent storage for models, outputs, custom nodes, and user data

You can change GPU size later while the workspace is stopped. Persistent storage size is selected during creation.

Create a workspace

When you create a workspace, the console asks for:

Field	What it means
Name	Any workspace name up to 63 characters
GPU size	The compute profile for the workspace
Persistent storage	The durable workspace capacity for models, input, output, user data, and custom nodes
Release	Stable or Preview

Stable is the recommended default. Preview may include newer runtime or UI changes before they are promoted to the stable channel.

You choose the release channel during creation. Release channel changes are not available after creation.

You can also create a workspace by copying from an existing workspace. That copy starts the new workspace with the selected source contents, so the new workspace storage size should be large enough to hold the copied data.

Operate a workspace

Each workspace appears in the console list with:

• lifecycle status
• selected GPU size
• release channel
• runtime summary

From that list, you can:

• start a stopped workspace
• stop a running workspace
• open the edit flow
• launch Comfy when the workspace is ready

While a workspace is starting or stopping, the console refreshes its status automatically.

What you can change

Change	Supported behavior
Rename workspace	Supported through the edit flow
Change GPU size	Supported only while the workspace is stopped
Change persistent storage after creation	Not available after creation
Change release channel after creation	Not available after creation
Launch while stopped	Not supported until the workspace is started and ready

Data and lifecycle actions

The edit flow lets you update the workspace name. You can also change GPU size, but only while the workspace is stopped. It also supports copying data from another compatible workspace, which overwrites the current workspace contents.

Action	What it does
Copy from workspace	Replaces the current workspace contents with data from another compatible workspace
Reset workspace	Clears workspace data and leaves the workspace stopped
Delete workspace	Permanently removes the workspace

Use reset when you want a clean workspace without removing the workspace entry itself. Use delete when you want to free capacity or remove the workspace entirely.

What you see in the console

The Comfy page shows:

• workspace quota feedback
• current lifecycle and runtime state
• selected persistent storage profile
• release channel labels
• start, stop, edit, and launch actions

If you have more than one workspace, you can also sort the table from the column headers.

Read next

• Read Application overview to compare hosted applications with the other RemoteGPU product paths.
• Read API keys if you also need API or kubectl access outside the console.