Authentication

RemoteGPU uses two authentication models:

• a signed-in browser session for console workflows
• API keys for programmatic workflows

The right model depends on which product surface you are using.

Choose the authentication path

Product path	Typical user	Interface	Authentication model
Application	Non-professional or low-ops user	Console	Signed-in browser session
Inference API	Developer or backend integrator	HTTP API	API key
Kubernetes	Kubernetes-literate operator	Console and kubectl	Browser session for the console, API key for kubectl

Access model details

Use your normal sign-in flow at console.remotegpu.ai when you are:

• managing Comfy workspaces
• creating or reviewing Kubernetes namespaces in the console
• reviewing Kubernetes deployments, services, and ingresses in the console
• managing account settings and API keys

In these flows, you do not send an API key manually.

Which key should you create

Scope	Use it when	Typical caller
Inference	You need to call inference endpoints only	App server, script, backend worker
Kubernetes exec	You need namespace access through kubectl	Local shell, CI job, platform operator
All	One automation needs both inference and Kubernetes access	Admin automation

Read API keys for scope details and examples.

Typical workflows

Console-only workflow

If you only use the console, sign in with your normal account. No API key is required.

Inference API workflow

1. Create an inference-enabled API key.
2. Pass it in the x-api-key header.
3. Continue with Image inference.

This path is usually the right fit for semi-professional users, developers, and integrators who want a programmable API without operating Kubernetes directly.

Kubernetes workflow

1. Create a Kubernetes exec API key.
2. Download the namespace kubeconfig from the console.
3. Export REMOTEGPU_API_KEY before running kubectl.
4. Continue with Kubernetes overview.

This path is designed for professional users who are comfortable with native Kubernetes resources such as Deployment, Service, and Ingress.

Read next

• Read API keys to choose the right scope.
• Read Image inference if you want to call the inference API.
• Read Kubernetes overview if you want namespace access and kubectl.