Overview

Cheetah is an automated quality inspection platform for advanced manufacturing. The same integrated cobot and 3D scanner handles dimensional, surface, weld, and electronic inspections — switch programs, not equipment. Built for the production floor, not the metrology lab. One operator, scan → analyze → report.

This page is a wayfinder. Pick the path that matches what you're trying to do.

I'm evaluating Cheetah

You want to understand what Cheetah is, what it can do, and whether it fits your problem.

• System architecture — the components and how they fit together
• Data model — core entities and their relationships
• Hardware platform — what we make and what it supports
• Application catalog — the operator UIs we ship

I'm an operator or end user

You'll be using one of the cheetah-ui applications day-to-day.

• Operator — main control interface
• Program Builder — design motion sequences
• System Configuration — set up robots, sensors, IO
• Cheetah Validation — QC workflows
• Aux File Manager — CAD and reference geometry
• LJS Navigator — 3D point cloud workflows

I'm building an integration

You're writing code against the Cheetah API or SDKs.

• API Quickstart — first successful API call in five minutes
• API Reference — every public endpoint
• Python SDK and TypeScript SDK
• Webhook event reference — payload schemas per event
• Versioning policy — what we guarantee, what we don't

I'm an AI agent

If you're a coding assistant (Claude, Cursor, Copilot, ChatGPT) integrating with Cheetah on someone's behalf, start with:

• AGENTS.md — canonical integration workflow
• llms.txt — full doc index

Append .md to any URL on this site to receive the raw Markdown source.

What's stable and what's alpha

The hardware platform and operator applications are stable. Cobot, scanners, the operator UIs that run inspections day-to-day — these are production-ready and in use on factory floors.

The developer integration surface is in early alpha. The HTTP API, Python and TypeScript SDKs, and webhook event payloads may change between releases without prior notice. If you're integrating Cheetah programmatically with other systems, pin to specific versions and read the versioning policy.

This split matters: an operator using Cheetah on the factory floor has a stable product. A developer building a custom integration is working against an evolving surface.