- Type
- not stated
- Format
- JSON over REST API (dated flight records with typed fields; ISO 8601 time windows); sibling endpoints return position traces
- Volume
- Large and unquantified on this page. Bounded from the documented caps: up to 2,000 flights returned per 365-day MEGA query per airport and 1,000 per 90-day ULTRA query — a mid-size airport alone sees tens of thousands of movements/yr, so the underlying per-flight archive is plausibly hundreds of millions of movements worldwide with a companion raw ADS-B position-trace store (much larger). Exact row/byte count not published — request it in outreach.
- Users
- N/A - B2B developer/API product behind mandatory auth with Pro/Ultra/Mega paid tiers; no registered-user base is published (2-person company implies tens of paying accounts, not a user population)
- History
- not stated
- Update frequency
- not stated
- Growth
- Active — documentation is on a versioned v31 API with a tiered historical-ADS-B product hub and adjacent feature launches (carbon emissions), indicating an actively developed commercial platform.
- Launched
- est. 2023-2025 (docs already at versioned 'v31' path with a full paid-tier ladder, implying a product assembled recently and iterating fast; no founding date or funding history on record for the 2-person Milan company)
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated