Feature map

Tenant boundary for teams, members, projects, API keys, traces, and billing state.

Workspace inside an organization; every API key and trace is scoped to one project.

Users can sign in with password auth or Google OAuth when provider secrets are configured.

Project-scoped ingest keys used by SDKs and raw HTTP clients; keys are shown once.

Published as theta-obsrv with context-manager tracing, steps, metadata, media, metrics, and integrations.

Published as @theta-lab/obsrv with TypeScript types, async context parenting, batching, and integrations.

SDK and HTTP pipeline that accepts complete agent runs and persists normalized trace records.

Run detail view showing input, output, ordered steps, messages, tool calls, metadata, latency, tokens, and cost.

Nested operation model for LLM calls, tools, retrieval, routing, custom spans, and errors.

Chat-style user, assistant, system, and tool messages with structured content parts.

Records tool name, arguments, result, latency, timestamps, and errors inside the trace timeline.

Arbitrary JSON metadata attached to traces and steps for release, customer, workflow, or experiment slicing.

Image, audio, video, file, and sensor artifacts uploaded to object storage and linked back to traces.

Groups related runs by conversation or workflow identifier so repeated user journeys can be reviewed together.

Observed or automated quality signals recorded against traces for pass/fail, score, and label tracking.

Threshold rules over trace signals such as latency, error rate, cost, or metric outcomes.

Groups similar failure patterns across traces so recurring issues are easier to identify.

Natural-language trace search that uses an LLM-backed tool flow to retrieve and summarize matching traces.

Adds model-generated diagnosis or context to trace detail and cluster workflows when AI provider secrets are configured.

Wrapper for OpenAI calls so model requests and responses become structured trace steps automatically.

Wrapper for Anthropic calls, including tool-use details, token usage, status, and response metadata.

Adapter for OpenResponses-compatible gateway calls with normalized event ingestion.

Raw HTTPS API for traces, events, imports, media, metrics, search, and clusters.

Custom deployment path for enterprise customers that need private VPC or dedicated infrastructure.