Production & Governance

Use when Gateway, observability and guardrails as one managed deployment.

Skip when You want to adopt the pieces independently.

Use when Managed training runs with sweeps and artifact tracking wired up.

Skip when You want training infrastructure you run yourself.

Use when Constraining conversational flow with programmable rails.

Skip when You need deep semantic moderation — it is not a classifier.

Use when Validators that check output against a schema you define.

Skip when You need free-form moderation rather than structural checks.

Use when One classifier covering both prompt and response moderation.

Skip when You need domain-specific policy enforcement.

Use when Detecting and anonymising PII in text and images.

Skip when Your data is already pseudonymised at source.

Use when Prompt-injection and jailbreak detection at the gateway.

Skip when Requests cannot leave your network.

Use when Probing your own system for known vulnerability classes.

Skip when You have no remediation path for whatever it finds.

Use when Generating and scoring attack prompts systematically.

Skip when You are not authorised to test the target.

Use when Guardrails as code, enforced inline in the call path.

Skip when Self-hosting is a hard requirement.

Use when Prompt regression tests and side-by-side comparison.

Skip when You need self-hosting.

Use when Teams already deep in LangChain needing tracing and datasets.

Skip when Traces cannot leave your infrastructure.

Use when Making evaluation, rather than tracing, the primary workflow.

Skip when You need open formats and self-hosting.

Use when OpenTelemetry-native evaluation you can run yourself.

Skip when You want a vendor support contract behind it.

Use when Self-hostable tracing, prompts and evals in one place.

Skip when You want a fully managed product with a support contract.

Use when Declarative red-teaming and regression tests that run in CI.

Skip when You need a managed UI rather than a test runner.

Use when pytest-style evaluation you can run next to your unit tests.

Skip when You need a platform rather than a library.

Use when Gateway-level observability with per-request cost and latency.

Skip when You need eval primitives more than traffic logs.

Use when Experiment tracking and a model registry, with eval surfaces on top.

Skip when You need an open, exportable format.

Use when A vendor-neutral standard for emitting traces and metrics.

Skip when You want a product with a user interface.

Use when Prompt and eval work with a visual debugger for chains.

Skip when Self-hosting or reproducibility is a requirement.

Use when Open-source tracing and dashboards for LLM applications.

Skip when You want eval depth more than traffic visibility.

Use when Open-source observability and evaluation you run yourself.

Skip when You need enterprise support behind it.

Use when One evaluation model for both classical ML and LLM systems.

Skip when You only need LLM-specific tracing.

Use when Carefully explained model and method write-ups — though the publication is now archived.

Skip when You need recent work; the archive stopped years ago.