Fides Architecture Overview

The Fides platform is released as Docker images designed to be deployed as services to any modern container orchestration platform. This guide provides an overview of the Fides architecture, its components, and external dependencies for production deployments.

The architecture shows how different users interact with Fides components: Admins access the Fides webservers (fides.example.com) for configuration and data subject request management, while Users interact with the Privacy Center (privacy.example.com) to submit privacy requests or manage consent preferences. End users also interact with FidesJS embedded on business websites (example.com) for consent management and privacy controls. All public access flows through a CDN and load balancer for performance and security. Behind the scenes, horizontally scalable Fides Workers process privacy requests and consent workflows using managed PostgreSQL and Redis services, with object storage handling downloadable reports and attachments.

Fides Services

The core Fides application consists of stateless, horizontally scalable services:

All images use version tags (e.g., ethyca/fidesplus:2.68.0, ethyca/fides-privacy-center:2.68.0). For deployment-specific configuration, see Kubernetes, Terraform, or Docker guides.

External Dependencies

For production deployments, we recommend externally managed services for databases, load balancing, caching, etc.