Spare vs. Trapeze: A Modern Demand Response Platform Built for What Comes Next
Evaluating transit technology is one of the most consequential decisions an agency can make. This page is designed to help you compare Spare and Trapeze for demand response software side by side, using publicly available information, verified performance data, and questions to ask any vendor before you sign.
How we built this comparison
This comparison is based on publicly available information: procurement documents, agency RFP responses, vendor webinars, and verified performance data from live deployments. Where agencies have reported operational challenges directly, those are noted. Spare's capabilities are drawn from its own platform documentation and confirmed deployment outcomes. Trapeze's capabilities reflect publicly available materials and agency-reported experiences. We've aimed to represent both platforms accurately — if something is incorrect, contact us.
Best for / summary
Spare is best for
Agencies modernizing demand-response operations who want real-time optimization instead of batch scheduling, dispatchers and planners who can configure zones, policies, and service rules themselves, and teams that need NTD-ready reporting, commingled paratransit and microtransit, and open integrations on a cloud-native platform. A strong fit for agencies under board, audit, or OTP pressure that need to move quickly without waiting on vendor tickets or multi-month upgrade cycles.
Trapeze is best for
Agencies that value an established incumbent with a long track record in public transit and a large installed base, and teams that prefer a high degree of batch scheduling and manual dispatcher control. May suit agencies that want an on-premise deployment option and are comfortable with a module-based, vendor-managed configuration model where updates and reporting typically rely on dedicated vendor support.
Comparison table
| Capability | Spare | Trapeze |
|---|---|---|
| Dispatcher control & operations | ||
| Real-time schedule optimization | ✓Spare Engine continuously re-optimizes as bookings, cancellations, and disruptions occur — no batch window | ✕PASS uses batch scheduling; trips are locked between runs, typically re-optimized every 15 minutes to 2 hours per agency reports |
| Manual dispatcher override & trip reassignment | ✓Override optimization, lock trips, and reassign as needed | ✓Manual controls including trip flip/reverse and manual reassignment |
| Configurable scheduling parameters | ✓Boarding time, on-board-time limits, and detour tolerances configured directly | ✓Supported, though changes typically require vendor support or specialist users |
| Live traffic integration | ✓Routing natively integrated with Google live traffic; ETAs and sequencing reflect current road conditions | ✕PASS routes on static road data and historical speed factors, requiring manual dispatcher adjustments or time-padding |
| Auto-rematch on vehicle breakdown | ✓Affected trips auto-rematched to other vehicles in under a minute | ✕Rematching a broken-down vehicle's trips is a manual dispatcher process |
| Self-service configuration | ✓Service rules, zones, fare logic, and schedules modified without vendor intervention | Agencies report configuration is difficult and error-prone, typically requiring vendor support or paid professional services |
| Exception-based dispatcher workflow | ✓Dispatchers intervene only on flagged exceptions; routine matching and sequencing are automated | ✕Dispatchers manage the board through constant manual intervention and correction |
| At-risk trips surfaced | ✓Watch List proactively surfaces at-risk trips before they fail | Dispatchers must manually monitor the board to catch at-risk trips |
| Activity log "time travel" | ✓Full activity log and manifest history reconstruct exactly what happened, for investigations and disputes | ✕No equivalent investigation view for reconstructing past manifest states |
| Real-time KPI dashboard & reporting | ✓Live self-serve dashboards (OTP, PPVH, cost per trip), NTD-ready reporting, and Scout AI copilot — no SQL or vendor tickets | ✕Reporting requires offline exports or vendor support; advanced analytics spans ViewPoint, the Microsoft BI stack, and a third-party analytics partner |
| Staff training (time to train) | ✓Weeks — new staff typically reach self-sufficiency quickly on a modern web UI | Months, per agency reports |
| Capability | Spare | Trapeze |
|---|---|---|
| Paratransit depth & compliance | ||
| Integrated ADA eligibility case management | ✓Spare Eligibility runs natively on the same platform; eligibility status flows directly into booking | ✓Eligibility is a separate module, running in the same database |
| Automated eligibility enforcement at booking | ✓Rules enforced automatically across every booking channel | ✓Eligibility status available in PASS, tied to a given rider |
| Eligibility tracking | ✓Tracks certification expiry with automated renewal reminders, deadline tracking, and workflows | ✕Stores only minimal eligibility data, with no renewal automation |
| Self-service rider eligibility portal | ✓Riders start and manage eligibility applications online | A portal exists but requires an upgrade to the full OneMobility system |
| Commingling (paratransit + microtransit, shared fleet) | ✓Paratransit and microtransit commingled on a shared fleet within one dispatch environment | Without a rider app supporting same-day bookings, commingling does not happen in practice |
| Compliance | ✓SOC 2 Type II; supports HIPAA requirements | SOC 2 reported in progress as of 2024; cloud compliance posture less publicly documented |
| NTD & ADA reporting (built-in) | ✓NTD-ready and ADA compliance reporting built into the platform and self-serve | Agencies report NTD and FTA data is hard to extract and needs manual cleanup; new reports carry development fees and lead time |
| No-show / late cancellation automation | ✓Configurable no-show and suspension policies enforced automatically | ✓Service Infractions module manages no-shows and late cancellations |
| Group trips | ✓Multi-rider group trips supported within standard scheduling | Supported through a heavily manual process, often requiring day-of dispatcher intervention |
| Deadhead tracking | ✓Deadhead miles and hours tracked automatically for accurate cost and productivity reporting | Agencies report deadhead and revenue figures cannot be calculated accurately and are often estimated |
| Capability | Spare | Trapeze |
|---|---|---|
| Rider experience & fleet integration | ||
| Rider trip booking (app and web) | ✓Consumer-grade iOS/Android app and web portal with self-serve booking, live tracking, notifications, and rider–driver contact | ✓Rider app and web portal available; agencies report the app is hard to set up and use, lacking features like rider–driver calling |
| Real-time vehicle tracking for riders | ✓Real-time vehicle location and accurate ETAs in the app | Offered, but reviews cite reliability tied to local connectivity |
| AI bookings, cancellations & ETA calls | ✓Spare AI Voice books, cancels, and answers status calls conversationally | ✕Legacy IVR products, not a conversational AI agent |
| Rider notifications (IVR, SMS, email) | ✓Voice, SMS, and email notifications included in the subscription | Delivered through a separately licensed module, adding a line item beyond the core product |
| Rider self-service | ✓Book, change, and cancel across web, app, and AI channels without calling | Limited; agencies report legacy web portals drive low self-serve adoption |
| Step-by-step walking directions to pickup | ✓Walking directions to the pickup point for curb-to-curb and microtransit trips | ✕No walking-directions guidance to pickup |
| Driver app with live-traffic turn-by-turn navigation | ✓Google Live Traffic powers turn-by-turn navigation; routes and ETAs adjust in real time | DriverMate displays traffic, but scheduling routes on static road data per agency reports, so sequencing is not continuously traffic-optimized |
| TNC brokering | ✓Open Fleets orchestrates TNC, taxi, and dedicated fleets in one environment — 3M+ brokered trips | TripBroker exists, but agencies report integration is complex and slow, sometimes requiring dedicated staff |
| Multi-provider orchestration (5+ providers, unified) | ✓Multiple dedicated and non-dedicated providers managed from one unified dispatch view | Agencies report managing multiple providers manually or by email across separate systems |
| Unified rider app across paratransit + microtransit | ✓One rider app and profile spans paratransit and microtransit, with a single wallet | ✕Separate logins across portals and apps; no single rider tool supports both pre-booked paratransit and same-day microtransit |
| Capability | Spare | Trapeze |
|---|---|---|
| Technology & AI | ||
| Cloud-native SaaS | ✓Cloud-native SaaS with no on-premise servers or VPN to maintain | Historically on-premise and Windows-based; moving legacy customers to the cloud via an expensive OneMobility option |
| Automatic software updates | ✓Updates ship automatically as SaaS — no upgrade projects, downtime, wait lists, or version drift | ✕Upgrades can sit on multi-month project wait lists and can carry hidden fees, with training billed separately |
| AI-powered continuous scheduling engine | ✓Spare Engine runs continuous AI optimization across the fleet | ✕OneMobility is marketed as dynamic, but the underlying PASS engine remains event-driven and batch-oriented |
| AI analytics, plain-language reports | ✓Scout answers plain-language questions and generates reports without SQL | ✕No equivalent AI analytics copilot |
| Open API / integration-friendly architecture | ✓Open, documented APIs for integrating with existing systems | Agencies report a proprietary architecture; integrations quoted as paid line items with license and maintenance fees |
| Service-boundary & map management | ✓Staff manage service boundaries directly, with user-friendly polygon and shapefile imports | Map and boundary changes handled as funded special projects, with agencies submitting GPS data for import |
| Map data & updates | ✓Continuous map data included in the subscription — no separate per-update charge | Static licensed map data; agencies report paying for each map update as a funded project |
| Transit data standards | ✓Ingests and exchanges standard transit data formats including GTFS | ✓Supports GTFS and other ITS data-exchange standards (SIRI, NeTEx, VDV, ITxPT) |
| GTFS-Flex builder | ✓Publishes flexible and demand-response service to trip planners | ✕No native GTFS-Flex builder |
| Uptime / stability | ✓High availability with uptime documented on a public dashboard | Agency reports cite crashes and memory leaks requiring periodic restarts on legacy deployments |
| Multimodal trip planning | ✓Spare One plans across fixed route, microtransit, and paratransit | ✕No unified multimodal trip planner |
| Rate of product innovation | ✓New capabilities ship continuously as SaaS, with frequent releases | ✕Agencies report slow delivery, with promised features arriving years later or left unfinished |
| Capability | Spare | Trapeze |
|---|---|---|
| Commercial & architecture | ||
| Single platform: paratransit + micro + fixed route + asset management | ✓Paratransit, microtransit, and fixed route on one platform and one data model | Different service types typically require separate modules or products (PASS, OPS, FX, EAM) |
| Modern SaaS pricing model | ✓Transparent per-vehicle pricing that folds in updates and configuration changes | Custom, quote-based pricing with module add-ons, paid development, and unpredictable annual maintenance increases |
| Proven migration methodology | ✓A documented, repeatable Trapeze-to-Spare migration methodology, proven across multiple transitions with rapid go-lives | ✕Not applicable |
| Responsive support model | ✓Partner support model with published, live SLA performance rather than an anonymous ticket queue | ✕A ticket queue; agencies report slow response and limited proactive outreach |
| On-site go-live support | ✓On-site launch-day support during go-live | Not a consistent part of the model |
| EAM (enterprise asset management) | ✓Native EAM on the same platform as Demand Response and Fixed Route, with AI-powered predictive maintenance live at many agencies | ✓A mature, separately sold product with a large install base, added through acquisition rather than native |
| Workforce management (rostering, bidding, timekeeping) | Spare offers limited workforce-management functionality | ✓OPS is deeply embedded for bidding, timekeeping, payroll, and employee self-service |
| Fixed-route operations | ✓Native Fixed Route on the same platform, improving operational visibility across a multimodal network | ✓Long-established FX module; CAD/AVL available through sister company Vontas at extensive additional cost |
Evaluation questions
Questions worth asking any transit software vendor — including us.
Can your dispatchers adapt in real time, or are trips locked by a batch run?
Trapeze PASS is built on batch scheduling: optimization runs execute periodically — per agency reports, every 15 minutes to two hours at most sites — and trips are effectively locked between runs. When a vehicle breaks down, a rider cancels, or traffic shifts, dispatchers rework manifests by hand. Trapeze markets continuous dynamic optimization in OneMobility, but the legacy PASS engine still powers it in the background.
Questions to ask Trapeze:
- How frequently does the optimizer actually re-run in our live configuration, and can it re-optimize the moment a trip is cancelled or a vehicle goes down?
- When a vehicle breaks down mid-shift, how long does it take to rematch its trips, and is that automatic or manual?
- Does live traffic feed the scheduling engine's routing decisions, or do dispatchers pad time manually?
How much manual cleanup does it take to trust your NTD and FTA numbers?
Agencies report that much of their operational data sits in a proprietary, table-heavy structure that is hard to extract. Advanced reporting runs through ViewPoint on the Microsoft BI stack, plus a separate analytics partner — so a reporting need can span three vendors, adding handoffs and finger-pointing when numbers do not reconcile. The result is repeated manual validation before agencies trust their own compliance metrics.
Questions to ask Trapeze:
- When leadership asks for a new KPI or a different view, can our team build that report themselves without SQL or a vendor ticket?
- Is reporting included, or does it depend on separately licensed analytics with per-report development fees?
- How many separate reports — and how many vendors — does it take to assemble one NTD submission today?
What does it really cost to change something, and what happens at upgrade time?
Trapeze pricing is custom and quote-based, built from module licences, paid custom development, and annual maintenance with escalators. Agencies report being asked to fund development for features they were told the product could do, expensive map-update projects, and painful upgrade cycles.
Questions to ask Trapeze:
- What is the total cost of ownership over the term, including implementation, module add-ons, custom development, and maintenance escalators?
- When we need a new integration or a service change, is that included or billed as a project?
- What is the current upgrade wait list, how long will a mid-size upgrade take, and is training included?
How long until a new dispatcher is actually productive?
Trapeze is widely described as powerful but complex, with an information-dense admin UI and workflows that require many clicks. Agencies report long ramp times for new staff and heavy dependence on one or two "Trapeze experts" — when those people leave or retire, service continuity is at risk. Agencies also report upgrades arriving with no training on new features, or training billed separately.
Questions to ask Trapeze:
- How long does it take a brand-new dispatcher or scheduler to become self-sufficient on the system?
- How many of our daily tasks depend on one or two power users, and what happens if they leave?
- When an upgrade introduces new features, is training on those features included, or billed separately?
Is your rider and payment experience one account, or many?
Agencies report that Trapeze's rider tools are dated, that self-service booking is limited, and that payment and account linking across services frequently fails. Some agencies report funding a joint account across book-ahead paratransit and same-day service, and more than a year later riders still needed two separate accounts and payment methods.
Questions to ask Trapeze:
- Can a rider use one account and one wallet across every service type we operate?
- Does the rider app support push notifications and rider–driver communication today?
- Can riders self-serve book, change, and cancel across web and app without calling us?
How many systems are you stitching together around Trapeze?
Trapeze grew largely through acquisition and has since split into separate vertical business units. Agencies report a fragmented ecosystem: PASS, OPS, FX, EAM, and add-on modules that do not always talk to each other, with manual handoffs and finger-pointing across separate sales, support, and success teams.
Questions to ask Trapeze:
- Which of our workflows require exports, spreadsheets, or re-keying to move data between modules?
- Who is our single point of accountability for sales, support, and success?
- Do eligibility, operations, and reporting share one data model, or separate systems?
When something breaks, how fast does the vendor respond?
Agencies repeatedly report slow support and limited vendor outreach, worsened since the reorganization into vertical business units. Stability issues on legacy deployments — crashes and memory leaks requiring periodic restarts — compound the impact when support is slow.
Questions to ask Trapeze:
- What are your published response and resolution SLAs, and can you show live performance against them?
- Since the reorganization, who owns a cross-module issue end-to-end?
- What is your current known-issue list for the version we would run, and what availability are we contractually guaranteed?
Results from live deployments
The following results are drawn from verified live Spare deployments. Performance data is published in linked case studies and cross-referenced against agency reports.
On-time performance after leaving Trapeze
CapMetro — the largest automated ADA paratransit operation in North America — replaced a 20-year Trapeze deployment across roughly 200 vehicles and 40,000 monthly trips. OTP rose from around 89% on Trapeze to over 95% in the first week on Spare, and unmatched trips at the start of day dropped from roughly 300 to 30 per day. Citibus in Lubbock migrated off Trapeze PASS in 30 days, improving OTP from 75% to 94% within a month of go-live while expanding service to cover 100% of city limits.
Pre-scheduled paratransit at scale
A frequent legacy-era assumption is that modern platforms only handle same-day, dynamic trips. These are live pre-scheduled ADA paratransit deployments, not simulations: 99% of CapMetro's ~40,000 monthly trips are pre-scheduled at 95% OTP, and Citibus runs 2,600+ pre-scheduled trips per month at 90%+ OTP.
Ready to see it for yourself? Book a 30-minute demo and see how Spare performs in a live environment.
Book a Demo