TravelTime

Name: TravelTime
Brand: TravelTime

Imagine the possibilities with TravelTime.

Est 2010|Valuation $32.4M|Raised $10.8M|7 Ref Customers

LinkedIn 4K|Web traffic 110K|FTEs 56|HQ London, England, GB

- TravelTime vs Mapbox: TravelTime positions itself as an alternative to transactional Matrix API usage and provides a migration guide claiming larger matrices and public transit support. Mapbox offers broader platform capabilities and extensive documentation. - TravelTime vs Google: TravelTime states it does not use Google travel data at runtime; it benchmarks against Google drive times. Google remains a common benchmark for routing but can be costly at scale and has contractual limitations. - TravelTime vs HERE/TomTom: HERE and TomTom are established in automotive/logistics with strong traffic data; TravelTime’s differentiation is focused on large-scale time-based filtering/search and predictable pricing as stated by the vendor.

01Competitive Landscape

Narrative analysis

TravelTime vs Mapbox: TravelTime positions itself as an alternative to transactional Matrix API usage and provides a migration guide claiming larger matrices and public transit support. Mapbox offers broader platform capabilities and extensive documentation.
TravelTime vs Google: TravelTime states it does not use Google travel data at runtime; it benchmarks against Google drive times. Google remains a common benchmark for routing but can be costly at scale and has contractual limitations.
TravelTime vs HERE/TomTom: HERE and TomTom are established in automotive/logistics with strong traffic data; TravelTime’s differentiation is focused on large-scale time-based filtering/search and predictable pricing as stated by the vendor.

Market adoption signals (limited)

Vendor and third-party sources cite customers in real estate, job boards, and public sector use cases. These adoption signals should be validated via up-to-date references.

	TravelTime	Mapbox	Google Maps Platform
Starting Price	Not publicly listed (sales-quoted fixed fee)	Public, transactional pricing pages exist (varies by API; plus support tiers)	Public transactional pricing (varies by API; typically pay-per-use)
Best Suited For	High-volume, time-based search/matching + predictable billing	Developers wanting a broad mapping platform + strong docs + transactional scaling	Broad coverage and a large ecosystem; traffic-aware routing
Key Strength	Fixed-fee positioning; support for large matrices (vendor-stated); caching allowances	Full platform breadth (maps, navigation, search); mature tooling	Coverage and routing quality often treated as a benchmark by others
Key Weakness	Limited public pricing transparency; rate-limit complaints; unclear public security certifications	Costs can rise with usage; some features gated; licensing constraints on storing results	Can get expensive at scale; caching/terms constraints; vendor lock-in risk

TravelTime

01Competitive Landscape

Narrative analysis

Market adoption signals (limited)

02Market Map

01Competitive Landscape

Narrative analysis

Market adoption signals (limited)

02Market Map