NR PEACH (Natural Resources Permitting Exchange)

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

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Terraform

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Azure Terraform ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodTerraform
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseApache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 2 documented · 2 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

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.

NR PEACH API/service identity versus consuming-application user SSO · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Reviewed deployment source collection; application images and infrastructure components have separate versions · Source ↗ · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-19

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

NR PEACH complete production workload sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

NR PEACH (Natural Resources Permitting Exchange); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

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.

Community & 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.

Category fit

Licensing & permits management
British Columbia's open-source natural-resource permitting exchange application.

Compare within Licensing & permits management

  • FormKiQ Licensing and Permits Management Directory PublisherManage the intake, review, approval, issuance, and lifecycle tracking of licenses, permits, and certifications.
    • AWS
    Customer-operated · Commercial Only
  • PlanX (Open Digital Planning)Open-source digital-planning application with an upstream AWS infrastructure deployment.
    • AWS
    Customer-operated · Open Source / Open Core

These products address related workflows; read their category-fit notes before comparing scope. See all of Licensing & permits management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Azure Terraform ↗ · Azure

      Institution deployment · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory