DRM API Server Deployment Architecture

Seclore API Server acts as a secure middleware component between:

To know more about Seclore Policy Server, click here

Deployment support:

Network Architecture

DRM API Server Architecture DRM API Server Network Architecture Component placement and network zone segregation • Two Policy Server deployment options 🏢 CUSTOMER ENVIRONMENT INTERNAL NETWORK ⚙️ 1. Integrating Application CCP / ERP / DLP / PLM / Custom Application 👤 Customer-owned ☁️ On-premises or Customer Cloud HTTPS REST Upload • Protect • Download 🔥 FIREWALL DMZ / INTEGRATION ZONE S API 2. Seclore API Server REST / HTTPS • Port 443 👤 Customer-owned ☁️ Hosted in customer environment (On-premises or Customer Cloud) DATA STORES (CUSTOMER CONTROLLED) Application Database Tokens, PS details, File metadata File Storage Disk / S3 / DB 🔒 HTTPS REST (Port 443) SECLORE POLICY SERVER PLATFORM Policy Server — Two Deployment Options OPTION A — Seclore-Managed (AWS) S 3. Seclore Policy Server Managed by Seclore on AWS ☁️ Seclore-owned aws Seclore AWS Cloud OPTION B — Customer Environment S 3. Seclore Policy Server Deployed in customer environment 👤 Customer-owned ☁️ Customer Cloud (AWS / Azure) 🏢 Customer On-Premises (Data Center) ⚙️ Integrating Application S API Seclore API Server S Seclore Policy Server Database / Storage 🔥 Firewall 🔒 Secure Connection (HTTPS REST 443) Seclore Platform Customer Env * Internal / database connections are shown with grey dashed lines. Secure connections between environments use HTTPS over port 443.