PlanX (Open Digital Planning)

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

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

    Pulumi

  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
  • AWS: Customer cloud account · Customer-operated

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

    Pulumi AWS Infra ↗ · 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 methodPulumi
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseMozilla Public 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%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Moving upstream PlanX editor/application OIDC implementation · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

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

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.

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
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Moving upstream PlanX production component configuration, not whole-system HA capacity · Source ↗ · API resource consumption ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

PlanX (Open Digital Planning); 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 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.

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

Category fit

Licensing & permits management
Open-source digital-planning application with an upstream AWS infrastructure deployment.

Compare within Licensing & permits management

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.

    • Pulumi AWS Infra ↗ · AWS

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

      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.

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

Suggest a correction · Back to directory