Skip to main content

​
Summary

Guardrails 0.11.0 changes how validators are installed and begins the sunset of Guardrails-hosted remote inference. Nothing breaks the moment you upgrade — the guardrails hub CLI and the guardrails.hub import shim keep working during the deprecation window — but you should migrate to the patterns below. The final cutoff for the retired registry and the hosted inference endpoints is August 6, 2026.

​
Validators now install from PyPI

guardrails hub install and the private validator registry are being retired (final cutoff August 6, 2026). Validators are now standard PyPI packages named guardrails-ai-<name>, installed with pip or uv:
Update imports to the guardrails_ai namespace. The registered validator name is unchanged, so Guard().use(...) and any RAIL format="guardrails/..." keep working — only the import path changes:
No guardrails configure / API key is required to install validators anymore — they are public packages published on PyPI under the guardrails-ai- prefix.

​
Guardrails-hosted remote inference is being discontinued

Some validators could run their ML models on Guardrails’ hosted inference servers. Those servers are shut down on August 6, 2026. Switch to one of:
  1. Run the model locally — pass use_local=True when constructing the validator:
  2. Host your own endpoint and point the validator at it via validation_endpoint=.... See Remote Validation Inference.