The most revealing thing about RideCo is that its product keeps changing its mind. Every 20 seconds, its routing engine looks again: new booking, late van, traffic jam, wheelchair space, driver break, somebody who must reach a train. Then it redraws the trip without casually breaking the pickup and arrival promises already made. A conventional timetable is printed confidence. RideCo is organized doubt, sold as software.
That is a useful distinction because “Uber for buses” is both irresistible and wrong. RideCo does not primarily summon cars for consumers. It sells a cloud operating system to transit agencies, municipalities and fleet operators. The passenger gets an app or web portal. The driver gets a live itinerary. Dispatchers get an operations center. Managers get reports. The agency keeps the fare, eligibility rules and public obligations. Underneath sits Solver, the patented optimization engine trying to pack compatible trips into productive shared rides.
The company began in Waterloo, Ontario, in 2013. Co-founders Prem Gururajan, Matthew Monteyne and Darren Maki had watched family members struggle through long walks, waits and transfers just to reach work or school. They spent the early years building and testing. When they finally went to market, Gururajan later admitted, the market was not ready. Transit buyers were wary of transportation that depended on an app. The software existed before the appetite did.
The bus route that refuses to sit still
RideCo fits the awkward middle of public transportation. Dense corridors can fill trains and frequent buses. A single passenger can hail a taxi. Between them sit low-density neighborhoods, first-last mile gaps, overnight service and paratransit trips whose origins, destinations and accessibility needs scatter across a city. Running a large bus around an empty loop is costly. Giving every rider a private car is costly in a different direction. RideCo pools the demand.
A promise enters. A route comes out.
The product stack makes that logic usable. Passenger App handles reservations and tracking. Driver App supplies navigation and manifests. Operations Center lets dispatchers watch service and manage exceptions. Profile Manager stores preferences, contacts and standing orders. Data Insights turns the exhaust into performance reporting. Flex Fleets can broker eligible overflow trips to taxis or transportation network companies. An AI Agent handles routine bookings, cancellations and the eternal call-center question: “Where’s my ride?”
RideCo’s real specialty is not drawing the shortest line on a map. It is optimizing inside institutional rules. Paratransit may require eligibility checks, wheelchair capacity, subscription trips, arrive-before windows and human reservationists. A driver needs a meal break. A rider needs a guaranteed connection. A fleet operator needs a sane end to the shift. Solver keeps revisiting all of it, while “Time Snapping” can align a flexible trip with a fixed-route departure.
The app is the visible inch. The product is the pile of promises underneath it.YesPress analysis
What changed the buyer's mind
Proof arrived around the end of 2018, when larger cities began signing. San Antonio became the case that could fit in a budget presentation: in a low-density service area, VIA’s on-demand program reduced cost per passenger by 36 percent, according to RideCo’s case study. The lesson was not that dynamic vans should replace every bus. It was that the right van, in the right zone, could stop pretending a sparse neighborhood was a busy corridor.
Other deployments widened the pitch. Houston METRO reported 67 percent more passengers per vehicle hour in its curb2curb service, with 58 percent of rides shared and an average 4.8-star trip rating. Kansas City reported a 16 percent decrease in cost per passenger and $2.64 million in annualized savings across its modernization. SEPTA’s Philadelphia paratransit case study put annual savings above $8.8 million. These are company-reported case-study results, not universal constants, but they speak the language transit boards understand.
The market’s change of mind also changed RideCo’s financing. After years without institutional capital, it raised CAD $20 million in February 2022 - about US$15.8 million then - in a Series A led by Eclipse Ventures. The money was earmarked for engineering, customer support, sales and marketing. By 2024, RideCo appeared again on Deloitte Canada’s Technology Fast 50 with 1,276 percent revenue growth over four years. It says its technology has powered more than 80 services.
The $71.95 million timetable
RideCo now sells enterprise SaaS with the manners of public infrastructure. Agencies typically provide their own fleet or contract an operator; RideCo supplies software, implementation, training and support. Contracts can last years because replacing scheduling and dispatch is less like downloading an app than changing an airport’s control tower while aircraft are moving.
New York makes that literal. In August 2025, New York City Transit awarded RideCo an estimated $71.95 million Access-A-Ride technology contract. The base allows up to 18 months for implementation and seven years of operation and maintenance, plus a possible extension. During negotiations, daily scheduling capacity rose from 35,000 to 50,000 trips. Access-A-Ride already delivers nearly one million rides each month with more than 1,100 dedicated vehicles and thousands of taxis and for-hire providers. The rollout is phased across 2026 and 2027.
This is the payoff and the danger. Winning New York validates RideCo’s claim that it can operate at metropolitan scale. It also makes the company accountable to riders for whom “move fast and break things” is not cheeky startup folklore. Missing a paratransit trip can mean missing dialysis, work or the last safe journey home.
Las Vegas failed in public
Southern Nevada’s RTC launched new RideCo paratransit software in March 2026. Hundreds of riders were stranded or left waiting for hours, according to local reporting. RTC’s CEO called the first weeks “terrible”; board members called the results “abysmal.” RideCo CEO Prem Gururajan appeared before the board and said the service was improving. Whatever the technical causes, the first failure was the only metric riders could feel: on-time performance.
Atlanta offers a more encouraging counterpoint. MARTA phased in RideCo for paratransit reservations, scheduling and dispatching in June 2026, after app testing had exposed login and access problems in April. The rollout included rider assistance, operational training and a new app with booking, cancellation and vehicle tracking. The contrast is instructive. Migration is part of the product. Training is part of the product. A fallback phone line is part of the product.
What to steal - and when to leave it alone
RideCo’s differentiator against Via, Spare, legacy Trapeze systems and agency-built tools is continuous optimization married to the messy details of transit operations. Its Uber integration adds an escape valve: an agency can send eligible overflow or after-hours trips to a non-dedicated fleet under its own rules. That can absorb peaks without buying enough vans for the worst hour of the year.
Sell the operating metric, not the algorithm. Passengers per vehicle hour is easier to defend than “AI-powered routing.”
Guarantee the rider outcome first. Optimize around arrival windows instead of offering a clever route with a vague promise.
Design the zone before deploying the software. Density, trip purpose and transfer points determine whether pooling has a chance.
Treat launch support as product work. Test accounts, train dispatchers, preserve phone booking and rehearse the ugly exceptions.
There are conditions where the model will not work. Demand may be too thin to share rides but too broad to cover cheaply. Demand may be so dense that a frequent bus or train moves more people with less street traffic. A service zone can be drawn for political neatness instead of actual trips. Temporary grant money can hide a subsidy that local budgets will not sustain. Poor curb access, weak cellular coverage or a smartphone-only experience can exclude the riders the program exists to serve.
And software cannot repair a transit network starved of vehicles, drivers or operating funds. Microtransit can complement strong fixed routes; used as a blanket replacement, it risks turning public transportation into a small-vehicle queue. The economic crossover must be measured repeatedly, because success itself changes the math. When enough riders want the same journey, the flexible route has discovered a bus line.
RideCo’s story, then, is not a tidy conquest of the timetable. It is a company learning where flexibility belongs. The early market needed San Antonio’s savings before it trusted the app. New York now needs a careful migration more than it needs a flashy demo. Between those moments sits the company’s durable idea: public transit can change its mind in real time, as long as it keeps its word.