Customer-Facing Surface Only

LATCH docs for customers, operators, and integrators.

This documentation set covers the supported self-hosted LATCH runtime surface: startup, deployment, the local HTTP API, and the Console. It intentionally excludes internal runtime modules, licensing internals, marketplace webhooks, and implementation-specific code paths.

Ubuntu GPU Quickstart RunPod Quickstart

Start Here

Choose the operator path you actually need.

If you are deploying LATCH for the first time, start with one of the getting-started guides. If you are integrating against the local runtime from code, go straight to the API reference. If you are operating through the browser UI, the Console reference is the right surface.

Getting Started

RunPod Deployment

Fulfillment, license token placement, pod settings, startup timing, and first validation steps for bringing up LATCH on RunPod.

Open guide

Getting Started

Ubuntu GPU Quickstart

Exact Docker and NVIDIA runtime commands for pulling the private image, starting the container, and verifying a working LATCH room on Ubuntu.

Open guide

Reference

Customer API Reference

Searchable public API docs for the supported local HTTP surface only. Generated from curated markdown inputs so internal modules and source pages are not published.

Open API docs

Reference

Console Documentation

Operator guide for the LATCH Console panels, runtime defaults, workspace flow, and portable bundle features.

HTML guide PDF download
Your Gumroad receipt is not the runtime credential. After purchase, use the CoDynamics fulfillment email or claim flow to get your private registry credentials and your CoDynamics-issued runtime token before attempting either the RunPod or Ubuntu deployment path.

Scope Guardrail

What is intentionally not published here.

No internal code browser

The public API docs do not publish source-browser pages or module-by-module implementation docs.

No licensing internals

Marketplace webhook handlers, token signing internals, and control-plane implementation details remain out of the customer docs surface.