OpenPlan public lane

Open-source planning software that keeps maps, engagement, and delivery in one record.

OpenPlan is Apache-2.0 planning software for agencies, tribes, RTPAs, counties, and consulting teams. Nat Ford Planning supports it through managed hosting, onboarding, planning services, and custom implementation work.

Proof path for the Apache-2.0 claim:Source repository Apache-2.0 license text

Request access Review services Sign in to existing workspace

Core posture

Apache-2.0 core

OpenPlan is positioned as inspectable planning software, not a closed black-box SaaS dependency.

Public lane

Services-first access

Hosting, support, onboarding, implementation, and custom extensions are the commercial lanes around the open-source core.

Rollout status

Supervised release

OpenPlan is live with deliberate controls around managed hosting, billing, onboarding, and production use.

How work moves

A planning flow, not a feature collage

The public-facing entry points show how OpenPlan carries a team from intake to evidence, review, and delivery.

Flow

Move from corridor question to delivery packet

Corridor review, overlays, run history, and reporting stay tied together so the analysis does not get stranded in separate tools.

Flow

Keep project records, engagement, and reporting in one ledger

OpenPlan keeps project context visible while engagement campaigns and deliverables mature into report-ready material.

Flow

Publish a public lane without leaving the planning system

Share-token engagement pages let teams collect structured public input while preserving moderation and traceability.

Surface areas

Enter through the right lane

Each public route has a specific job and connects back to the broader planning record.

Evidence catalog

See a real screening run with its caveats

Nevada County 2026-03-24 screening runtime vs. Caltrans counts, gated as internal prototype only — caveats and validation metrics shown verbatim.

Analysis Studio access

Request the gated map and scenario workspace

Analysis Studio is a signed-in workspace area. Request a supervised review before using corridor maps, overlays, run history, and map-ready outputs.

Services lane

Review open-source, hosting, and implementation options

See how Apache-2.0 software, managed hosting, onboarding, support, planning services, and custom extensions fit together.

Access intake

Request a supervised workspace review

Submit agency context and a first workflow without triggering automatic provisioning or outbound messages.

Engagement workspace access

Request the gated engagement workspace

Public share links can be published, but campaign management stays in a signed-in workspace with moderation and human review.

Pilot boundary

What the current public release promises

The source-first posture is intentional: public agencies should be able to inspect the software behind their planning work.

Managed hosting and billing remain intentionally supervised because support obligations, data posture, and workspace ownership matter.

Public engagement portals preserve review and moderation before feedback enters formal reporting or summaries.

The platform is built for agencies and consulting teams that need traceable planning work, not another static status page.

Core lanes

Three surfaces that matter immediately

Map and analysis

Keep corridor questions, overlays, and run outputs visible inside a planning-grade workspace.

Public engagement

Collect structured public input with moderation, topic organization, and report-ready traceability.

Reporting

Carry evidence forward into deliverables without manually rebuilding context in a separate packet workflow.