Warning
Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Environments
Patria Investments uses three environments across all platforms: Development, Staging, and Production.
Overview
| Environment | Purpose | Access level | Change process |
|---|---|---|---|
| Development | Feature development and local/cloud sandbox testing | All engineers | No approval required |
| Staging | Integration, QA, and pre-production validation | Engineers + QA | PR review required |
| Production | Live business workloads | Restricted | Change request + approval |
Development
- Engineers have broad permissions to create, modify, and delete resources
- Data in this environment is synthetic or anonymised — never use real customer data
- Resources are subject to automated cleanup after 7 days of inactivity (cost control)
- Azure subscription:
patria-dev| GCP project:patria-data-dev
Staging
- Mirror of production configuration; used to validate before each release
- Access to staging data requires justification — contains masked production data
- Deployments to staging are triggered automatically by the CI/CD pipeline on merge to
main - Azure subscription:
patria-staging| GCP project:patria-data-staging
Production
Danger
Production access: Any change to production resources must follow the change management process.
Direct access is restricted to on-call engineers and the Infra & Cloud Squad.
- Azure subscription:
patria-production| GCP project:patria-data-prod - All access is logged and audited via Entra ID sign-in logs and GCP Audit Logs
- Deployments require an approved change request in ServiceNow
Escalation
Owner: Infra & Cloud Squad — see Contacts