Skip to main content

Your first InferCrane request

In this guide you will start the complete control and request path, call a stable model endpoint, and inspect the durable state behind it. No GPU or cloud account is required.
The local stack uses GPU-free fake vLLM workers. It proves application and lifecycle behavior, not model quality, GPU performance, or real-provider compatibility.

See the complete safety loop first

From a repository checkout, one command runs the local product proof and cleans up its isolated Docker project:
It connects an existing endpoint, sends and inspects a request, creates an intentionally unready candidate without provisioning it, records a deterministic Release Guard rejection, verifies the active revision did not change, rejects the candidate, and removes all temporary state. The output is explicitly marked as fixture evidence; it does not claim GPU or provider qualification.

Prerequisites

  • Git
  • Docker with Compose v2
  • Port 18000 available
1

Clone InferCrane

2

Start the local stack

The stack includes PostgreSQL, InferCrane, two fake workers, and a development router. The development API key is infercrane; production mode rejects that default.
3

Send a request

Add --stream to the CLI request to print response text as chunks arrive.
4

Inspect what happened

These commands use the authenticated control-plane API. Public CLI workflows never connect directly to PostgreSQL.
5

Open the terminal operations view

The terminal workspace reads the same durable control API and can be closed without cancelling operations. The separately released browser console is currently in private preview; see Operations console for the local self-hosted boundary.
6

Stop the stack

This preserves PostgreSQL data. Add --volumes only when you intend to delete the local state.

Choose your next path

Deploy a real model

Plan provider and runtime choices before creating billable capacity.

Connect an endpoint

Observe an existing vLLM, LiteLLM, or OpenAI-compatible endpoint first.

Understand the model

Learn endpoints, environments, serving plans, deployments, and revisions.

Before creating real infrastructure

The Homebrew formula and release archives are prepared but not yet publicly released. Until the release package is published, build the CLI from source:
plan is side-effect free. A real deploy can create billable resources, so check provider setup and the capability matrix first. Adapter registration does not prove that an exact model, runtime, GPU, and provider combination has passed real-infrastructure qualification.