Deployment Overview
NeMo Guardrails can be deployed in various environments depending on your requirements. This guide provides an overview of the available deployment options.Deployment Options
You can deploy NeMo Guardrails in the following ways:Local Server
The quickest way to get started is running the server locally on your development machine.The local server is ideal for development and testing but not recommended for production use.
Docker Container
Docker provides a consistent, isolated environment for deploying NeMo Guardrails. Benefits:- Consistent environment across development and production
- Easy dependency management
- Simplified deployment and scaling
- Isolation from host system
Production Deployment
For production workloads, you’ll need additional considerations:- Scalability: Load balancing and horizontal scaling
- Security: API authentication, TLS/SSL, secrets management
- Monitoring: Logging, metrics, and observability
- High Availability: Redundancy and failover mechanisms
Choosing a Deployment Method
Use this guide to select the appropriate deployment method:| Deployment Type | Use Case | Complexity |
|---|---|---|
| Local Server | Development, testing, demos | Low |
| Docker | Staging, consistent environments | Medium |
| Production | Production workloads, enterprise | High |
Server Configuration
The NeMo Guardrails server supports several configuration options:--config: Path to your guardrails configuration directory--port: Port to run the server on (default: 8000)--verbose: Enable verbose logging for debugging
API Endpoints
The server exposes the following main endpoints: Chat completions endpoint compatible with OpenAI API format. Retrieve the current rails configuration.Next Steps
Docker Deployment
Deploy using Docker containers
Production Deployment
Best practices for production