LATCH RunPod Quickstart | CoDynamics Lab

Make sure you have the right credentials.

Your Gumroad license key is purchase evidence only. Do not use it as LATCH_LICENSE_TOKEN.

You need the CoDynamics fulfillment email or fulfillment page containing your private registry credentials and runtime token.

If CoDynamics sent you a RunPod account-setup link, complete that first before you create the pod.

Recommended GPU for first deployment: 1x H100 80GB.

Create the pod with the correct image and env vars.

Image Settings

Container image

Use the private CoDynamics registry image shown in your fulfillment email: codynamicslatch.azurecr.io/latch/self-hosted:stable.

Port

Expose port 8091

LATCH serves both the local API and the Console on port 8091.

Registry Credentials

Use the private ACR login

In RunPod's private-registry or image-pull credentials area, enter the short-lived CoDynamics ACR username and password from your fulfillment message so RunPod can pull the image.

Runtime Env

Set the startup token

Set the three LATCH env vars below exactly. This is the supported customer validation path.

RunPod env vars Copy these into the pod environment settings

LATCH_LICENSE_TOKEN=<your CoDynamics runtime token>
LATCH_LICENSE_VALIDATION_MODE=codynamics_online
LATCH_LICENSE_VALIDATION_URL=https://cdlac-demo-api.azurewebsites.net/api/license/startup_validate
LATCH_PRODUCT_AUTO_WARMUP=true

Wait through image pull and model warmup.

First image pull is large. Expect roughly 15 to 20 minutes the first time the host downloads the image.

After the pod is running, the runtime starts warmup automatically and still takes roughly 7 to 8 minutes before LATCH is ready.

When RunPod shows the pod as Ready, go to the pod Connect tab and click HTTP Service on port 8091 to open the LATCH Console.

If the pod stays in an image-download or initialization state for much longer than expected, verify the registry credentials first. If the image already pulled but the runtime is still loading, that usually means model warmup is still in progress rather than a failed deployment.

During the image-pull and container-start phase, RunPod's own Telemetry and Logs views are the best source of truth. Use the LATCH health endpoint and Console only after the port 8091 HTTP service is actually live.

You do not need to configure an SSH key pair for normal customer use. SSH is optional and only needed for shell access or low-level debugging inside the pod. The Console and the local API both work through the port 8091 HTTP service.

Verify the room before uploading documents.

Readiness check Use the pod HTTP endpoint once port 8091 is live

curl -s http://127.0.0.1:8091/health | jq '.status, .ready, .profile_id'

"ready"
true
"cdlac_latch_qwen14b_locked_20260317"

Use the proxied HTTP Service link on port 8091 to open the LATCH Console in the browser.

You can also call the same port directly as the local API surface once the room reports "ready".

Upload a document and wait for the compile success notification before you query.

For the supported request surface, use the customer API reference linked below.

Once the pod is live.

Reference

Customer API Reference

Use the local HTTP surface directly for health, compile, query, batch, and clear operations.

Open API docs