priiism security and compliance
priiism is built for engineering teams at companies where code security and data compliance are non-negotiable — with SOC 2 Type II certification, end-to-end encryption, and enterprise deployment options that keep your code in your control.
Security architecture
priiism handles sensitive source code and development data. The platform is designed with security as a first-class requirement, not a checkbox.
- Encryption in transit — all data moving between priiism and connected tools (Git, CI/CD, IDE plugins) is encrypted via TLS
- Encryption at rest — code data, analysis results, and team configuration are encrypted at rest in priiism's infrastructure
- Minimum-scope access — integration tokens and OAuth connections use the minimum permissions required for each function
- Audit logging — all AI actions, generated outputs, and deployment decisions are logged and attributable
Compliance certification
- SOC 2 Type II — priiism maintains SOC 2 Type II compliance, covering security, availability, and confidentiality trust service criteria
- Compliance documentation is available to enterprise customers under NDA for security review processes
Enterprise deployment options
For organizations with strict data residency or air-gap requirements:
- Private cloud deployment — priiism runs within your cloud account (AWS, Azure, GCP), keeping code off shared infrastructure
- On-premises deployment — full platform deployment within your own data center or private network
- Both options support the full feature set with no reduction in AI capability
Data usage policy
- priiism does not train shared models on your proprietary code without explicit written agreement
- Enterprise customers who opt into model fine-tuning retain ownership of the resulting fine-tuned weights
- Code submitted to priiism is not used to generate output for other customers
Access control
- Role-based access control (RBAC) for dashboard, repository connections, and deployment permissions
- SSO integration available for enterprise customers
- Repository and environment access can be scoped per team or per project
Reporting a security issue
Contact priiism's security team directly through the enterprise support channel or your dedicated Customer Success Manager. Production security issues are escalated to Tier 3 engineering with direct customer communication.
FAQ
- Is priiism SOC 2 certified?
- Yes. priiism maintains SOC 2 Type II compliance. Enterprise customers can request compliance documentation for their security review process.
- Can we run priiism without sending code to external servers?
- Yes. Enterprise customers can deploy priiism on-premises or in a private cloud instance within their own infrastructure, ensuring code never leaves their environment.