
# Licensing & permits management

Applications, approvals, issuance, renewals and supporting documents.

Canonical page: https://launchinyourcloud.com/categories/licensing-permits-management/
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.


Applications, approvals, issuance, renewals and supporting documents.

3 listings.


## FormKiQ Licensing and Permits Management

Manage the intake, review, approval, issuance, and lifecycle tracking of licenses, permits, and certifications.

- Listing: https://launchinyourcloud.com/directory/formkiq-licensing-permits-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/licensing-permits-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- licensing-permits-management: Applications, approvals, issuance, renewals and supporting documents.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Licensing and Permits Management solution: https://formkiq.com/solutions/licensing-permits-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/licensing-permits-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 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.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Licensing and Permits Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/licensing-permits-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The overview describes controlled review access and audit history for permit records; approval and external registry actions require an agreed workflow. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Licensing and Permits Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/licensing-permits-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Licensing and Permits Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/licensing-permits-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Licensing and Permits Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/licensing-permits-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Advanced or Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Licensing and Permits Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/licensing-permits-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## 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.







## PlanX (Open Digital Planning)

Open-source digital-planning application with an upstream AWS infrastructure deployment.

- Listing: https://launchinyourcloud.com/directory/planx/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Pulumi
- Architecture: Pulumi-managed application services, PostgreSQL, object storage and networking in customer AWS.
- 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://editor.planx.uk
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application's planning and external data integrations need local configuration. Infrastructure-state credentials, institutional identity and geographic-data services are separate from a generic turnkey installation.

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

Pulumi-managed application services, PostgreSQL, object storage and networking in customer AWS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- licensing-permits-management: Open-source digital-planning application with an upstream AWS infrastructure deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/theopensystemslab/planx-new/main/infrastructure/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- Pulumi AWS Infra (aws): https://raw.githubusercontent.com/theopensystemslab/planx-new/main/infrastructure/README.md
  Pulumi-managed application services, PostgreSQL, object storage and networking in customer AWS. The application's planning and external data integrations need local configuration. Infrastructure-state credentials, institutional identity and geographic-data services are separate from a generic turnkey installation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes DafyddLlyr, jessicamcinchak, johnrees, 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/theopensystemslab/planx-new/graphs/contributors

- Upstream project: https://github.com/theopensystemslab/planx-new

### Sources

- Pulumi AWS Infra: https://raw.githubusercontent.com/theopensystemslab/planx-new/main/infrastructure/README.md

- MPL-2.0: https://raw.githubusercontent.com/theopensystemslab/planx-new/main/LICENSE.md

- Commits: https://github.com/theopensystemslab/planx-new/commits

### Licensing sources

- https://raw.githubusercontent.com/theopensystemslab/planx-new/main/LICENSE.md

### Infrastructure sources

- https://raw.githubusercontent.com/theopensystemslab/planx-new/main/infrastructure/README.md


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 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: Documented. The application implements Microsoft OIDC with configured client/callback, ID-token validation, nonce checking and mapped user/JWT creation. Configure tenant/client and editor permissions for the chosen deployment; council editor login is distinct from the public citizen journey. Scope: Moving upstream PlanX editor/application OIDC implementation. Source: https://github.com/theopensystemslab/planx-new/blob/main/apps/api.planx.uk/modules/auth/strategy/microsoft-oidc.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 Pulumi-managed application services, PostgreSQL, object storage and networking in customer AWS. 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/theopensystemslab/planx-new/main/infrastructure/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/theopensystemslab/planx-new/tree/main/infrastructure. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The upstream production Pulumi configuration sets API container CPU/memory to 4096 units/8192 MiB and Hasura to 2048/4096, consumed by the service definitions. These are specific component allocations from the operator deployment, not a complete host minimum; database, other services, scaling, backups and workload remain additional. Scope: Moving upstream PlanX production component configuration, not whole-system HA capacity. Source: https://github.com/theopensystemslab/planx-new/blob/main/infrastructure/application/Pulumi.production.yaml (reviewed 2026-11-21). Supporting source: API resource consumption — https://github.com/theopensystemslab/planx-new/blob/main/infrastructure/application/services/api.ts.

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: PlanX (Open Digital Planning); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/theopensystemslab/planx-new/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






