OpsML: End-to-End AI Lifecycle Management

Docs · Feature Request

OpsML is an AI lifecycle management platform built for the governance of both traditional ML and agentic AI systems. Its central abstraction is the card — a versioned, encrypted, registry-tracked record that wraps data, models, experiments, prompts, agents, or services. Cards are created in Python or YAML, persisted to a Rust server, and visualized in a SvelteKit UI.

Teams use OpsML to bring structure and governance to AI systems: consistent versioning, artifact lineage, monitoring, and observability — from initial training through production deployment.

What OpsML Covers

• Traditional ML — version and track datasets, models, and experiments with full artifact lineage
• Agentic — manage and version prompts, create, register, and evaluate agents across providers (OpenAI, Anthropic, etc.) with spec drive prompts and agent definitions
• Agents — register, version, and govern agents with AgentCard; define specs in YAML and manage the full lifecycle via CLI
• Services — bundle cards (models + prompts + agents) into versioned ServiceCard deployments with a YAML spec + CLI lock/install workflow
• Monitoring — drift detection and data profiling via Scouter
• Observability(beta) — OpenTelemetry trace ingestion and span visualization for any instrumented service, not just agents
• Evaluations(beta) — offline and online GenAI evaluation tied to versioned prompt cards

Status

v3.0.0 is generally available and ready for use in existing ML workflows.

Stable components — no breaking changes planned:

Component	Status
DataCard	Stable
ModelCard	Stable
ExperimentCard	Stable

Anything ported from OpsML v2 is considered stable unless explicitly marked as beta. Let us know if you encounter any issues.

Beta components — breaking changes possible in versions before 3.1.0:

Component	Status
PromptCard	Beta
ServiceCard / AgentCard	Beta
Agent UI	Beta
Prompt UI	Beta
Observability UI	Beta

If you depend on beta components, pin to a specific version and review the changelog before upgrading to any release before 3.1.0.

Quick Start

pip install opsml

Start a local server and UI:

opsml ui start

Navigate to http://localhost:3000 in your browser. Use guest as both the username and password.

Then run the getting started example:

pip install scikit-learn
python py-opsml/examples/getting_started.py

Stop the server when done:

opsml ui stop

Traditional ML

fromopsmlimportSklearnModel, CardRegistry, TaskType, ModelCardfromsklearnimportensembleX, y= ... # your dataclassifier=ensemble.RandomForestClassifier(n_estimators=5)
classifier.fit(X, y)
model_interface=SklearnModel(model=classifier, sample_data=X[:10], task_type=TaskType.Classification)
model_interface.create_drift_profile(alias="drift", data=X)
card=ModelCard(interface=model_interface, space="my-team", name="classifier")
CardRegistry("model").register_card(card)
print(card.version) # e.g., "1.0.0"

GenAI — Prompts

fromopenaiimportOpenAIfromopsmlimportPromptCard, Prompt, CardRegistrycard=PromptCard(
space="my-team",
name="summary-prompt",
prompt=Prompt(
model="gpt-4o",
provider="openai",
messages="Summarize the following in one sentence: ${text}",
system_instructions="Be concise.",
),
)
client=OpenAI()
user_message=card.prompt.bind(text="OpsML manages AI artifacts...").messages[0]
response=client.chat.completions.create(
model=card.prompt.model,
messages=[card.prompt.system_instructions[0].model_dump(), user_message.model_dump()],
)
CardRegistry("prompt").register_card(card)

Agents

Agents are most commonly defined via an opsmlspec.yaml file and managed through the CLI. The YAML spec describes the agent's capabilities, skills, interfaces, and linked cards (prompts, models). The CLI resolves versions and installs artifacts.

# opsmlspec.yamlname: support-agentspace: platform-teamtype: Agentmetadata:
description: "Customer support agent for billing and account queries."tags: ["support", "billing"]service:
version: "1.0.0"write_dir: opsml_servicecards:
- alias: support-promptspace: platform-teamname: support-promptversion: "1.*"type: promptagent:
name: support-agentdescription: "Customer support agent for billing and account queries."version: "1.0.0"capabilities:
streaming: truesupported_interfaces:
- url: "https://agents.example.com/support/v1"protocol_binding: "HTTP+JSON"default_input_modes: ["text"]default_output_modes: ["text"]skills:
- id: billing-queryname: "Billing Query"description: "Handles billing questions and invoice lookups."tags: ["billing", "finance"]examples: ["What is my current balance?"]input_modes: ["text"]output_modes: ["text"]

opsml lock # resolves card versions, creates opsml.lock
opsml install service # downloads artifacts to ./opsml_service

Registered agents are visible in the OpsML UI, which provides a playground for live testing, an evaluations dashboard, and an observability view for trace data.

Architecture

OpsML is a polyglot system:

• Rust — all logic: server, client, SQL/storage backends, auth, encryption, versioning, and CLI (crates/)
• Python — top-level stubs only, exposed via PyO3/maturin. No client or server logic lives in Python.
• SvelteKit — UI compiled and embedded in the server binary

The Python package is a stub layer over the Rust core. Card creation, registry operations, storage, encryption, and the HTTP client are all implemented in Rust and called through PyO3 bindings. This means the full logic is testable in Rust without the Python layer, and the Python API gets the same correctness guarantees as the server.

Supported backends:

Layer	Options
Database	SQLite, PostgreSQL, MySQL
Storage	Local, S3, GCS, Azure Blob

Feature Comparison

Feature	OpsML	Others
Artifact-first approach (cards)	✅	❌
SemVer for all artifacts	✅	❌ (rare)
Multi-cloud storage	✅	✅
Multi-database support	✅	✅
Authentication	✅	✅
Artifact encryption at rest	✅	❌ (rare)
Artifact lineage	✅	❌ (uncommon)
Data profiling	✅	❌
Real-time model monitoring	✅	❌ (rare)
Observability (OpenTelemetry traces)	✅	❌ (rare)
Agent evaluation system (offline + online)	✅	❌ (rare)
Agent registry + governance	✅	❌
Agent UI (playground, evaluations, observability)	✅	❌
Isolated environments	✅	❌
Single Python dependency	✅	❌
Open source	✅	❌ (some)

Contributing

See the contributing guide. Outstanding items are tracked in the project backlog.

Thanks to these projects and people for the foundation we built on.