
# NR PEACH (Natural Resources Permitting Exchange)

British Columbia's open-source natural-resource permitting exchange application.

Canonical page: https://launchinyourcloud.com/directory/bcgov-nr-peach/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## NR PEACH (Natural Resources Permitting Exchange)

British Columbia's open-source natural-resource permitting exchange application.

- Listing: https://launchinyourcloud.com/directory/bcgov-nr-peach/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Terraform
- Architecture: Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/bcgov/nr-peach
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The repository establishes a government-operated Azure deployment. Reuse outside the originating organization requires replacing its identity, data-source and agency-specific integrations; public source does not make those institutional dependencies generally available.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- licensing-permits-management: British Columbia's open-source natural-resource permitting exchange application.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Terraform (azure): https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md
  Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform. The repository establishes a government-operated Azure deployment. Reuse outside the originating organization requires replacing its identity, data-source and agency-specific integrations; public source does not make those institutional dependencies generally available.
  Source type: institution-deployment; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jujaga, qhanson55, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/bcgov/nr-peach/graphs/contributors

- Upstream project: https://github.com/bcgov/nr-peach

### Sources

- Azure Terraform: https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md

- Apache-2.0: https://raw.githubusercontent.com/bcgov/nr-peach/main/LICENSE

- Commits: https://github.com/bcgov/nr-peach/commits

### Licensing sources

- https://raw.githubusercontent.com/bcgov/nr-peach/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The service implements OAuth bearer-token validation with OIDC discovery/JWKS. That confirms API access validation, not an end-user staff portal or browser SSO flow. Identify the consuming application and its login/mapping before asserting user federation for PEACH. Scope: NR PEACH API/service identity versus consuming-application user SSO. Source: https://github.com/bcgov/nr-peach/blob/main/src/middlewares/helpers/oauth.ts (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for Azure application services, PostgreSQL, Key Vault and monitoring provisioned by the project's Terraform. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Reviewed deployment source collection; application images and infrastructure components have separate versions. Source: https://raw.githubusercontent.com/bcgov/nr-peach/main/infra/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/bcgov/nr-peach/tree/main/infra. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The Azure Terraform separates shared platform and application instances and exposes deployment/environment-specific App Service SKU and scaling choices. These parameters do not establish a tested complete production CPU/RAM/storage baseline; database, traffic, logging, replicas and recovery require sizing. Scope: NR PEACH complete production workload sizing remains unconfirmed. Source: https://github.com/bcgov/nr-peach/blob/main/infra/core/variables.tf (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: NR PEACH (Natural Resources Permitting Exchange); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/bcgov/nr-peach/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






