
# PlanX (Open Digital Planning)

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

Canonical page: https://launchinyourcloud.com/directory/planx/
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.


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






