Security & Compliance
This page covers controls implemented in the application and deployment responsibilities. Encryption algorithms, retention, residency, testing cadence, and certifications are deployment or commercial commitments and must be verified for the specific Pragence environment.
Data protection
| Area | Current contract |
|---|---|
| In transit | Configure TLS at the ingress, load balancer, or hosting provider |
| At rest | Configure database, object storage, and backup encryption in the deployment |
| Backups | Deployment-specific backup and retention policy |
Access control
- Application-level: organization and project role-based access control (see Roles & Permissions).
- Database-level: RLS safeguards are present for tenant-scoped access; verify the database role and migration configuration in each deployment.
- API: JWT tokens or organization API keys, with endpoint-specific authentication and authorization dependencies.
- Additional controls: MFA, IP allowlisting, API-key scopes, audit logging, and rate limiting are implemented where enabled by the deployment.
Compliance posture
The repository includes audit logging and operational runbooks. Access reviews, vendor assessments, penetration testing, DPAs, and certifications are organizational or commercial controls, not guarantees made by application code. SOC 2 certification timing is not established by the repository.
Data residency
Data residency is determined by the selected deployment and infrastructure:
| Deployment | Availability |
|---|---|
| Managed cloud | Region and retention are provider-specific |
| Self-hosted or BYOC | Customer-selected infrastructure and region |
Self-hosted deployments
The repository includes Docker Compose and a starter Helm chart for self-hosted deployment. Your infrastructure team configures encryption, backups, network access and updates. Billing routes and provider integrations depend on deployment configuration.
See Deployment for setup instructions.