Resources — Explainer

What is software as a service?

SaaS is the SaaS model applied to transit fare payments — a shared platform, subscription-priced, continuously updated, that agencies configure for their network rather than build from scratch.

Definition

SaaS in plain language

Fare payments as a service (SaaS) is the delivery of transit fare payment capabilities — mobile ticketing, ABT, open payments, validation, back office — as a cloud-based subscription service. Instead of procuring and building a custom fare system, agencies subscribe to an established platform, configure it for their network, and receive continuous improvements without procurement cycles or upgrade projects. The commercial model is typically per-trip, aligning the vendor’s revenue to ridership outcomes.

SaaS vs custom build

Why agencies choose SaaS over custom development

Traditional custom-built fare system

  • Large upfront capital cost
  • Years of development before go-live
  • Agency owns the maintenance burden
  • Upgrade cycles every 5–7 years
  • R&D investment borne by one agency
  • Vendor lock-in at every layer

Fare payments as a service

  • Per-trip subscription — no large upfront capital
  • Configure and go live in months, not years
  • Platform maintained and updated by vendor
  • 3,000+ updates per year — no upgrade projects
  • R&D shared across 125+ agency network
  • Open APIs — no lock-in at any layer

Common questions

SaaS FAQ

No — agencies configure their own fare rules, products, concessions, and branding in Justride Hub. The SaaS model handles infrastructure; you control fare policy.

Your data is yours. Masabi provides full DataMart API access so you can export and analyse your data in any tool. Data residency options are available for agencies with regulatory requirements.

You pay a fee per trip processed through Justride. Pricing scales with ridership — so costs grow proportionally as your network grows, with no large fixed costs.