A screen in a lobby that says the next three departures from the stop outside, and how long it takes to reach downtown from there, is a small feature with a large integration problem behind it: every transit agency publishes differently, and a network of buildings spans dozens of them. We solve that half. The display, the layout and the brand stay yours.
Solutions
For digital signage
Real-time departures and live travel times for any stop in the country, ready to build into your own displays.
Trusted by

What we help with
One API instead of one per agency
Scheduled and live departures for stops across the United States and beyond, from feeds we already aggregate and keep current. Adding a building in a new city is a query, not an integration project.
Built into your own system
We are the data layer, not the product. Signage vendors take the departures feed and render it inside their own player, CMS and templates, alongside everything else on the screen.
Live ETAs to the places people are going
"12 min to Downtown" is a routing question, not a departures one. Our routing answers it for the destinations that matter at that site, multi-modal and aware of the time of day, so a screen shows travel time rather than only the next bus.
Scale that behaves
Fleets of screens refreshing together make a distinctive request pattern. Metered plans, volume pricing and a public status dashboard, so a rollout across hundreds of sites is a known quantity.
What it runs on
Transitland APIs
REST and GraphQL for departures, stops, routes and service alerts. The REST departures endpoint is what a screen calls for the next few departures.
Interline Routing Platform
Transit and street routing behind one API, for the travel times to the destinations a given site cares about.
Two calls are enough for a complete display: one for what is leaving the stops nearby, one for how long those journeys take.
Getting real-time right
Three write-ups on the real-time side, which is the part that decides whether a screen is trustworthy:
- Built with Transitland: a digital departures screen . A ferry departure ticker someone built from the same API a signage platform would call, which is the shortest demonstration of what the data supports.
- Inspecting GTFS Realtime through the website or the API . What an agency's live feed actually contains, and how to check it before you put it on a wall.
- Validating real-time feed quality . The research project behind the validation-error list Caltrans adopted, which is why we know where live data goes wrong.
Putting transit on a screen?
Tell us roughly how many sites and where, and we will size it.
