Skip to content

How it works

Three open kits share one data model, the City Pack. Each step feeds the next, and real trips feed back into planning.

01

Plan with open data

The Planner builds a hexagon grid (H3) over the study area and fills it with American Community Survey (ACS) demographics, Longitudinal Employer-Household Dynamics (LEHD) commute flows, existing transit from General Transit Feed Specification (GTFS) feeds, and points of interest from OpenStreetMap. It computes access to jobs, a transparent transit gap index, and a simple, documented demand model, then suggests one to three candidate on-demand zones anchored to rail and bus hubs. Scenarios compare cost per trip, passengers per vehicle-revenue-hour and who is served. Planning is free for everyone.

Go
02

Write it down as a City Pack

A City Pack is a folder of plain files: city.yaml (service patterns, hours, fares, fleet, costs, autonomy rules, targets), funding.yaml (the split and every funding source with its caps and restrictions), planning.yaml, zones.geojson and stops.geojson. Adding a city is one command, with no code changes.

Go
03

Launch: full platform or City OS

Full platform: a rider app, a driver app, dispatch that pools shared rides within wait and detour limits, and an agency console. City OS: for a city that already has an operator, OpenTransit reads the operator's GTFS Realtime or Mobility Data Specification (MDS) feed and provides dashboards, incident tracking, autonomy rule checks and reports.

Go
04

Fund every trip transparently

Each trip's cost is split across rider fares, foundations, sponsors and the city according to the City Pack, honoring caps, eligible costs, rider groups, zones, hours and match requirements. A double-entry ledger balances to the cent, and any trip can be explained line by line. OpenTransit charges a flat monthly fee for larger deployments and never a per-ride commission.

Go
05

Measure, publish, re-plan

Key performance indicators are tracked against targets. Open data goes out as GTFS with the GTFS-Flex extension, GTFS Realtime vehicle positions, a National Transit Database (NTD)-style monthly summary and anonymized trip files the agency owns. Actual trips return to the Planner's calibration view.

Go