Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

  • Information Frontier Agent
  • Vendor Management Agent
  • Product Tour
  • Pricing

Solutions

  • All Solutions
  • Atlas
  • Wayfinder
  • Horizon

Suppliers

  • Sell Your Data
  • Start Onboarding
  • Programmatic Data License

Community

  • Public Index
  • Signals
  • Blog

Company

  • About
  • Team
  • Careers
  • Brand

Connect

  • LinkedIn
  • X
PrivacyTermsCookies

© 2026 Brickroad

/Index/Quanergy/Quanergy
Q

Quanergy

QUANERGYManage supplier listing

Curb-to-gate airport movement telemetry captured by LiDAR and unified in a cloud platform: live and historical wait times at check-in, security and boarding; journey mapping and dwell analytics; concourse, lounge and restroom congestion; gate-readiness, boarding progress and assistance-need detection; lane and gate productivity measured as passengers-per-lane and turn times; plus shift-level KPI benchmarks and historical flow replays usable for scenario simulation. Notably the platform also ingests third-party systems, so the store is heterogeneous airport operational data rather than sensor output alone

Open buyer room →
Quanergy/Quanergy
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Quanergy and files the sample in your catalog — private to you.

Start 7-day trial→Nothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry
Electronic EquipmentAirport Services
Instruments
equities
Categories
Alternative
Geospatial
Regions
USUKOtherEurope
Sample tickers
DALUALAALLUVIAG.LFRA.DEDFS.L
Dataset card
Type
not stated
Format
Tabular high-frequency time-series per sensor zone (timestamp, counts, wait minutes, dwell minutes, congestion state, throughput per lane/gate), reduced from raw LiDAR point clouds; delivered as cloud analytics with dashboards, AI forecasting outputs and replayable historical series. Third-party feeds are normalised into the same schema
Volume
Per-site order 10^7-10^8 reduced rows annually, estate order 10^8-10^9. Basis: continuous LiDAR sensing reduced to per-zone metrics at sub-minute to minute cadence across check-in, security, boarding, concourse, lounge and restroom zones — a large terminal plausibly carries 10^2 sensor zones, each generating 10^5-10^6 timed records a year, with raw point-cloud data one to two orders of magnitude larger in bytes. The unification of third-party feeds adds further volume that is not LiDAR-derived and therefore not bounded by sensor count
Users
N/A — B2B airport analytics deployment with no consumer account base; scale is counted per instrumented airport and per sensor zone. Airport operator staff consume dashboards under operator licences, so there is no registered-user population that could be licensed
History
5 years
Update frequency
not stated
Growth
Active but restructured and revenue-constrained. Active evidence: an airport-specific product brief dated February 2026, indicating a deliberately marketed current line rather than legacy collateral, and a product surface spanning flow, gate operations, forecasting and resilience rather than a single tool. Constraint evidence: ~63 staff carrying ~$9.3M revenue against ~$162.1M of cumulative funding, with the funding stage recorded as an unlabelled non-standard category rather than a growth round — a funding-to-revenue ratio far from a normal expansion profile, which points to an asset history or restructuring rather than clean compound growth
Launched
Company est. mid-2010s; the Q-INSIGHTS airport analytics line materially newer. Basis: the corporate record shows substantial cumulative funding and a mature sensor business built around the Q-TRACK LiDAR product, which implies a decade-scale company history, whereas Q-INSIGHTS is presented as an analytics layer that unifies an already-deployed sensor base — analytics layers follow hardware installs, they do not precede them. The airport positioning itself is current: the product brief is dated February 2026. No explicit founding or launch year appears in the retrieved brief, so the split dates are bounding estimates and both should be confirmed with the vendor
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site

Quanergy has not added their own details yet. Not yet on file:

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling