What Control Plane does
Why Control Plane
Agent development breaks standard CI/CD. A unit test can pass while the agent produces worse answers. A deploy can succeed while latency doubles. Control Plane adds the agent-specific checks (LLM evaluation, trace comparison, cost budgets) as first-class pipeline steps.Key features
GitOps-native: Yourlangship.yaml lives in the repo. Pipelines, eval configs, and deployment targets are all version-controlled.
Trace-first observability: Every agent run produces an OpenTelemetry-compatible trace with LLM call details (model, tokens, latency, cost), tool calls, memory reads, and final outputs.
Eval-in-CI: Define evaluators (LLM-as-judge, exact match, semantic similarity, custom Python) and run them on every push. Block merges when quality drops.
Dataset versioning: Store prompt templates, test cases, and expected outputs in Control Plane’s dataset store. Pin evals to specific dataset versions so results are reproducible.
Multi-environment deployments: Promote agent versions from dev → staging → production with environment-specific configs and automatic rollback on eval failure.
Architecture overview
Control Plane has three components:- Control Plane Server: Receives traces, stores datasets, runs evals, manages deployments. Self-hosted via Docker or Kubernetes.
- Control Plane CLI:
langshipcommand for local development, running evals, and triggering deploys. - Control Plane SDK: Lightweight instrumentation library (
pip install langship) that adds trace collection to any LangChain, LlamaIndex, or raw OpenAI agent.
Where to go next
- Quickstart: running Control Plane Server and tracing your first agent in 10 minutes
- How It Works: pipeline architecture and core data model
- Deployment: Docker Compose, Kubernetes, and scaling
- GitHub Actions: integrating Control Plane evals into your PR workflow