Imagry

Name: Imagry
Brand: Imagry

Vision-based autonomous driving solutions without HD maps, LiDAR, or the Cloud | HW-Agnostic | Location-Independent.

Est 2015|Valuation $99M|Raised $46M

LinkedIn 19K|Web traffic 9K|FTEs 149|HQ San Jose, California, US

Published Oct 7, 2026

01Common complaints

- The procurement requires an immediately available, standardized enterprise security/compliance package (for example, a publicly available SOC 2 Type II report). - The procurement process requires published third-party validated safety metrics (disengagement, collision-avoidance performance, defined ODD boundaries). - The buyer prefers an operator model (robotaxi/shuttle as-a-service) rather than integrating and operating autonomy internally. - The deployment environment is highly unstructured or extreme (heavy snow/ice, very poor lane markings, unusual signage) unless vendor performance is validated in that exact ODD. - The buyer needs precise HD-map behaviors and deterministic geo-fenced operations today; map-based vendors may be more suitable in those scenarios.

Deal disqualifiers (poor fit)

Buyer requires a turnkey, fully driverless service in the immediate short term
Buyer cannot support sustained integration and testing efforts
Buyer requires publicly available SOC 2/ISO certifications as a gating procurement requirement prior to engagement
Buyer requires transparent, independently validated safety and performance benchmarks before any pilot

Known limitations acknowledged publicly

Imagry's public materials emphasize capabilities; explicit limitations are not prominently published.

Limitations implied by available evidence

Validation transparency: limited public independent benchmarking and quantitative safety data.
Review ecosystem: limited presence on major B2B review platforms, which can complicate reference checking.
Organizational and process risks: employee reviews suggest potential management and coordination issues that could influence delivery timelines.

Roadmap signals

Public announcements reference multi-year roadmaps (for example, planned implementation stages in 2027 for certain projects), implying a phased approach to maturity.

02Why they buy

Vendor-claimed differentiators (require validation)

- Imagry promotes a mapless, camera-first approach that it asserts reduces reliance on HD maps and LiDAR; these are vendor claims and should be validated through pilots and technical due diligence. - Partnership announcements (for example, with a Tier-1 supplier) and transit pilots indicate some level of system integration and testing activity. - Public profiles reference support for multiple traffic regimes (right-hand and left-hand traffic); buyers should verify technical scope for their markets.

Areas where competitors have advantages

More extensive published safety case studies (some competitors)
Greater OEM penetration and supply-chain scale (some competitors)
More complete platform and fleet operations tooling narratives (some competitors)

03Field reports

Important context on review availability

Imagry is an automotive autonomy supplier rather than a standard B2B SaaS product. As a result:

There are few or no listings on typical SaaS review sites (G2, Capterra) for the product itself.
The most available signals are employee reviews (Glassdoor) and community sightings/discussions (forums, Reddit).

Community/social signals (Reddit / enthusiast communities)

A public forum thread includes an anecdotal report from an observer who reported seeing Imagry vehicles and described a braking behavior of concern. This is anecdotal and not a controlled evaluation, but it indicates the system has been tested on public roads and attracted observer attention.

Employee sentiment (Glassdoor) — mixed

Glassdoor reviews reflect mixed employee sentiment: - Positive themes: collegial teams, product-focused development work, interesting technical challenges. - Negative themes: coordination challenges between sites, management and communications complaints, perceived workload and limited career progression in some reviews. Interpretation: while not customer satisfaction data, employee sentiment can affect program delivery timelines and responsiveness during integration-heavy projects.

Why customers choose Imagry (inferred from positioning and announcements)

Likely decision drivers based on Imagry's public messaging and partnerships:

Reduced emphasis on HD map creation/maintenance and geofencing constraints
Reduced dependence on LiDAR (lower sensor BOM cost in principle)
Claims of hardware-agnostic integration
Transit use cases where operator economics (driver shortage, operating cost reduction) can justify pilots

Why customers might avoid or churn (inferred)

Based on public sources and general market risks, likely reasons to avoid or reduce engagement include:

Program delays due to safety and regulatory validation
Performance limitations in complex edge cases
Integration complexity and vehicle platform constraints
Vendor maturity concerns compared with larger incumbents (Mobileye, Tier-1 suppliers)

Public bus pilot: Israel (vendor-published)

Imagry reports operating a public bus pilot on a defined route in Israel.

Strength: a specific route and use case are identified.
Limitations: public sources do not provide disengagement rates, safety-driver intervention counts, operating hours, passenger volumes, weather performance, or independent audit outcomes.

Shuttle: institutional medical campus (vendor-published)

Imagry reports an autonomous shuttle operation at a large medical campus.

Strength: deployment in an institutional environment where operational constraints can be defined.
Limitations: campus or medical-center ODDs can be less challenging than dense urban environments; public materials did not fully disclose safety-operator requirements or operational constraints.

Tier-1 supplier integration for automated parking (press release)

Imagry announced that a Tier-1 supplier would integrate part of Imagry's technology to support automated parking in the supplier's AD platform.

Strength: partnership with a Tier-1 supplier indicates some level of technical integration capability.
Limitations: public announcements did not specify module boundaries, performance metrics, or production timelines. Partnership announcements do not guarantee production volume.

Roboshuttle project in Latvia — vendor + local media

Imagry and a local mobility operator announced a roboshuttle plan with a proposed route between an airport and the city center, and a stated implementation target in the forward-looking timeframe.

Strength: independent reporting corroborates route intent.
Limitations: the plan is forward-looking and its success depends on regulatory approvals, operational readiness, and verified technical performance over time.

04Best fit

Company sizes

Best fit tends to be mid-to-large organizations capable of funding and managing complex pilots:

Public transit operators: city or regional PTOs, typically large operations
Bus OEMs and integrators: mid-to-large manufacturers
Automakers and Tier-1 suppliers: enterprise-scale organizations

Industries/verticals

Public transportation (buses, shuttles)
Automotive OEM/Tier-1 autonomy and ADAS programs
Airports, campuses, or controlled corridors for staged rollouts

Roles and personas

VP/Director of Autonomous Systems, ADAS, or Innovation
Fleet operations leadership (transit operators)
Safety/compliance leads (functional safety, cybersecurity)
Systems engineering and integration leads

Pain points addressed

Driver shortages and operating cost pressures
Potential to reduce mapping and high sensor-stack costs
Desire for camera-centric autonomy options that may reduce infrastructure requirements

Qualification criteria (good fit)

Buyer can fund multi-year pilots and integration efforts
Buyer has access to vehicles with drive-by-wire capability and robust sensor mounting
Buyer has a clear ODD and a staged rollout plan
Buyer can support local regulatory engagement and safety-operator staffing during pilots

05The pitch

What the product does (core value proposition)

Imagry is a B2B autonomous driving (AD) software provider focused on camera/vision-based, HD-mapless autonomy for passenger vehicles and public transit (buses/shuttles). The company describes its stack as: - Mapless (does not require HD maps / pre-mapped routes) - LiDAR-free (positions the approach as not relying on LiDAR) - On-vehicle (the system performs primary processing on the vehicle) Imagry refers to its core software as Imagry Cortex / "AI Driver," consisting of two major components: - Perception stack: multi-camera perception producing a top-down environmental representation. - Motion planning stack: a deep neural network (imitation-learning style) that plans driving behavior. Buyer takeaway: Imagry provides an AD software stack intended for OEMs, Tier-1 suppliers, and public transit operators seeking camera-first approaches to L3/L4 autonomy; procurement and technical teams should validate vendor claims through pilots and technical due diligence.

Target market and positioning

Imagry's public messaging emphasizes deployments focused on practical autonomy for: - Public transit operators (autonomous buses, shuttles, and planned shuttle services) - Automakers/OEMs and Tier-1 suppliers (L3 autonomy and features such as automated parking) Imagry positions its approach to differentiate from strategies that rely on: - LiDAR-heavy sensor stacks - HD map pipelines - Geo-fenced ODDs tightly bound to pre-mapped areas

Get a comprehensive analysis of Imagry including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 7, 2026

01Common complaints

The procurement requires an immediately available, standardized enterprise security/compliance package (for example, a publicly available SOC 2 Type II report).
The procurement process requires published third-party validated safety metrics (disengagement, collision-avoidance performance, defined ODD boundaries).
The buyer prefers an operator model (robotaxi/shuttle as-a-service) rather than integrating and operating autonomy internally.
The deployment environment is highly unstructured or extreme (heavy snow/ice, very poor lane markings, unusual signage) unless vendor performance is validated in that exact ODD.
The buyer needs precise HD-map behaviors and deterministic geo-fenced operations today; map-based vendors may be more suitable in those scenarios.

Deal disqualifiers (poor fit)

Buyer requires a turnkey, fully driverless service in the immediate short term
Buyer cannot support sustained integration and testing efforts
Buyer requires publicly available SOC 2/ISO certifications as a gating procurement requirement prior to engagement
Buyer requires transparent, independently validated safety and performance benchmarks before any pilot

Known limitations acknowledged publicly

Imagry's public materials emphasize capabilities; explicit limitations are not prominently published.

Limitations implied by available evidence

Validation transparency: limited public independent benchmarking and quantitative safety data.
Review ecosystem: limited presence on major B2B review platforms, which can complicate reference checking.
Organizational and process risks: employee reviews suggest potential management and coordination issues that could influence delivery timelines.

Roadmap signals

Public announcements reference multi-year roadmaps (for example, planned implementation stages in 2027 for certain projects), implying a phased approach to maturity.

02Why they buy

Vendor-claimed differentiators (require validation)

Imagry promotes a mapless, camera-first approach that it asserts reduces reliance on HD maps and LiDAR; these are vendor claims and should be validated through pilots and technical due diligence.
Partnership announcements (for example, with a Tier-1 supplier) and transit pilots indicate some level of system integration and testing activity.
Public profiles reference support for multiple traffic regimes (right-hand and left-hand traffic); buyers should verify technical scope for their markets.

Areas where competitors have advantages

More extensive published safety case studies (some competitors)
Greater OEM penetration and supply-chain scale (some competitors)
More complete platform and fleet operations tooling narratives (some competitors)

03Field reports

Important context on review availability

Imagry is an automotive autonomy supplier rather than a standard B2B SaaS product. As a result:

There are few or no listings on typical SaaS review sites (G2, Capterra) for the product itself.
The most available signals are employee reviews (Glassdoor) and community sightings/discussions (forums, Reddit).

Community/social signals (Reddit / enthusiast communities)

Employee sentiment (Glassdoor) — mixed

Glassdoor reviews reflect mixed employee sentiment:

Positive themes: collegial teams, product-focused development work, interesting technical challenges.
Negative themes: coordination challenges between sites, management and communications complaints, perceived workload and limited career progression in some reviews.

Interpretation: while not customer satisfaction data, employee sentiment can affect program delivery timelines and responsiveness during integration-heavy projects.

Why customers choose Imagry (inferred from positioning and announcements)

Likely decision drivers based on Imagry's public messaging and partnerships:

Reduced emphasis on HD map creation/maintenance and geofencing constraints
Reduced dependence on LiDAR (lower sensor BOM cost in principle)
Claims of hardware-agnostic integration
Transit use cases where operator economics (driver shortage, operating cost reduction) can justify pilots

Why customers might avoid or churn (inferred)

Based on public sources and general market risks, likely reasons to avoid or reduce engagement include:

Program delays due to safety and regulatory validation
Performance limitations in complex edge cases
Integration complexity and vehicle platform constraints
Vendor maturity concerns compared with larger incumbents (Mobileye, Tier-1 suppliers)

Public bus pilot: Israel (vendor-published)

Imagry reports operating a public bus pilot on a defined route in Israel.

Strength: a specific route and use case are identified.
Limitations: public sources do not provide disengagement rates, safety-driver intervention counts, operating hours, passenger volumes, weather performance, or independent audit outcomes.

Shuttle: institutional medical campus (vendor-published)

Imagry reports an autonomous shuttle operation at a large medical campus.

Strength: deployment in an institutional environment where operational constraints can be defined.
Limitations: campus or medical-center ODDs can be less challenging than dense urban environments; public materials did not fully disclose safety-operator requirements or operational constraints.

Tier-1 supplier integration for automated parking (press release)

Imagry announced that a Tier-1 supplier would integrate part of Imagry's technology to support automated parking in the supplier's AD platform.

Strength: partnership with a Tier-1 supplier indicates some level of technical integration capability.
Limitations: public announcements did not specify module boundaries, performance metrics, or production timelines. Partnership announcements do not guarantee production volume.

Roboshuttle project in Latvia — vendor + local media

Imagry and a local mobility operator announced a roboshuttle plan with a proposed route between an airport and the city center, and a stated implementation target in the forward-looking timeframe.

Strength: independent reporting corroborates route intent.
Limitations: the plan is forward-looking and its success depends on regulatory approvals, operational readiness, and verified technical performance over time.

04Best fit

Company sizes

Best fit tends to be mid-to-large organizations capable of funding and managing complex pilots:

Public transit operators: city or regional PTOs, typically large operations
Bus OEMs and integrators: mid-to-large manufacturers
Automakers and Tier-1 suppliers: enterprise-scale organizations

Industries/verticals

Public transportation (buses, shuttles)
Automotive OEM/Tier-1 autonomy and ADAS programs
Airports, campuses, or controlled corridors for staged rollouts

Roles and personas

VP/Director of Autonomous Systems, ADAS, or Innovation
Fleet operations leadership (transit operators)
Safety/compliance leads (functional safety, cybersecurity)
Systems engineering and integration leads

Pain points addressed

Driver shortages and operating cost pressures
Potential to reduce mapping and high sensor-stack costs
Desire for camera-centric autonomy options that may reduce infrastructure requirements

Qualification criteria (good fit)

Buyer can fund multi-year pilots and integration efforts
Buyer has access to vehicles with drive-by-wire capability and robust sensor mounting
Buyer has a clear ODD and a staged rollout plan
Buyer can support local regulatory engagement and safety-operator staffing during pilots

05The pitch

What the product does (core value proposition)

Mapless (does not require HD maps / pre-mapped routes)
LiDAR-free (positions the approach as not relying on LiDAR)
On-vehicle (the system performs primary processing on the vehicle)

Imagry refers to its core software as Imagry Cortex / "AI Driver," consisting of two major components:

Perception stack: multi-camera perception producing a top-down environmental representation.
Motion planning stack: a deep neural network (imitation-learning style) that plans driving behavior.

Buyer takeaway: Imagry provides an AD software stack intended for OEMs, Tier-1 suppliers, and public transit operators seeking camera-first approaches to L3/L4 autonomy; procurement and technical teams should validate vendor claims through pilots and technical due diligence.

Target market and positioning

Imagry's public messaging emphasizes deployments focused on practical autonomy for:

Public transit operators (autonomous buses, shuttles, and planned shuttle services)
Automakers/OEMs and Tier-1 suppliers (L3 autonomy and features such as automated parking)

Imagry positions its approach to differentiate from strategies that rely on:

LiDAR-heavy sensor stacks
HD map pipelines
Geo-fenced ODDs tightly bound to pre-mapped areas

Get a comprehensive analysis of Imagry including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →