Deployment Architecture
Overview
Peridot is deployed using a hybrid architecture that separates the control plane from the data plane.
This design ensures that governance and control are centralized, while data processing remains within the customer’s environment.
Architecture Overview
Peridot consists of two primary components:
Control Plane (Peridot Cloud)
Policy management
Routing logic
Governance configuration
Metadata and audit logs
Data Plane (Customer Environment)
AI request processing
Model execution
Data handling
Integrations with internal systems
Why This Matters
This architecture ensures:
Sensitive data does not leave your environment
Governance is centralized and consistent
Deployment meets enterprise security requirements
How It Works
Request originates in customer system
Peridot control plane evaluates policies
Routing and enforcement decisions are made
Request is executed in customer data plane
Logs and metadata are recorded
BYOK (Bring Your Own Key)
Peridot supports BYOK for model providers:
API keys are managed by the customer
Model usage remains under customer control
No shared credentials
Cloud Support
AWS (primary)
Azure
Google Cloud
Deployment Options
Kubernetes (recommended)
Docker (development environments)
In Production
Data never leaves the customer environment
Policies are enforced centrally
Systems scale independently
All activity is auditable
Security Benefits
Data isolation
Controlled model access
Full auditability
Compliance-ready architecture
Next Steps
Configure your deployment
Review security and compliance details