Every airport is different.
So is every quote.
We publish the model, not list prices. Tell us your scope; we send a written proposal within five working days.
How we charge.
Per airport, not per user.
Most of the value sits in passenger interactions and operating events, not internal seats.
Per product, modular.
Each product is independently licensed. Start with one. Add the rest later. Same tenancy.
Annual subscription.
Annual billing. Multi-year terms get better commercial treatment. USD pricing on request.
AI is included, not metered.
AI capabilities are included with the product they sit inside. No per-inference, no per-API meter.
What we charge for.
Passenger-voice platform. Scope by channel mix, languages, regulator pack. See AeroFeedback →
Intelligent complaint platform. Pairs with AeroFeedback for closed-loop resolution. See AeroResolve →
Apron / stand monitoring. Hardware + subscription per stand or pier; existing CCTV reused where it covers. See AeroGround →
AOCC brain. Core per airport; each feed (AeroGround, AeroTaxi, AeroRunway, AeroFOD) priced under its own product. See ATOMS →
Taxiway optimisation. Priced per runway or movement-area pair. See AeroTaxi →
Runway-ops monitoring + throughput. Priced per runway. See AeroRunway →
Airfield FOD. Priced per zone (runway / taxi / apron) and per mode (mobile / fixed / stand). See AeroFOD →
Video-AI spine. Included with AeroGround, AeroFOD, AeroRunway. See AeroVision →
From first call to signed proposal.
The conversation.
Your airport, your channel mix, your regulator deadlines, your top three operating frustrations.
The scoping.
We map your scope to product set, deployment modes, integrations, rollout sequence.
The proposal.
Line-item pricing, phased rollout plan, commercial terms, integration template. National-authority engagements take longer.
The pilot.
Pilots scoped in days, live in weeks. Network rollouts: 4–6 weeks per airport on the proven template.
What's included,
not metered.
Pilots in days; per-airport rollouts on the proven AAI template — config, data-residency, training.
Quarterly DGCA pack out-of-the-box. ICAO Doc 9184 framework reflected across the suite.
India tenants stay in India. Other tenants in their region. Consent + audit by design.
Aviation AI included with the product it sits inside. Sentiment, theme extraction, video AI — all included.
Built to plug into
your existing airport stack.
ATOMS reads A-CDM milestones and the AODB schedule, writes back airport-side milestones.
AeroTaxi + AeroRunway ingest standard surface-movement-radar and multilateration streams.
AeroVision reuses existing apron / runway CCTV where coverage allows — no rip-and-replace.
AeroFeedback ships the DGCA submission in the cadence and format the regulator expects.
Federated SSO across the suite. SCIM provisioning to your IdP. Roles + memberships per tenant.
SLA breaches, complaint events, FOD alerts route to ops desks, ground handler comms, and any HTTPS endpoint.
Daily snapshot exports to your data lake. Read-only API for live reads. You always own the data.
Default: NorthSky-hosted in your region (Azure / AWS). On-prem available for national-authority engagements.
Common questions.
Why don't you publish prices?
Scope moves the number too much — channel mix, stands, runways, integrations, regulator format, term length. A list price would mislead you. We send a written proposal within five working days.
Why per airport instead of per user?
Value sits in passenger interactions and operating events, not internal seats. Per-airport billing aligns with throughput, not staff headcount.
Can we start with one product and add more later?
Yes — that's the design. Other products plug into the same tenancy, same login, billed as you turn them on. No re-implementation.
Are AI features metered or charged per inference?
No. Aviation AI is included with the product it sits inside. See the AI governance posture for policy.
How long does a typical airport take to go live?
Pilots are scoped in days, live in weeks. Network rollouts on the proven AAI template land at 4–6 weeks per airport, including configuration, integrations, training, and a regulator dry-run.
What hosting options are available?
Default is NorthSky-hosted in your region (Azure for India tenants, customer-region-of-choice elsewhere). On-prem deployment is available for national-authority engagements — same product, same updates, separate operating model.
Who owns the data?
You do. Data is in-region. Daily snapshot export (Parquet / CSV) to your data lake, plus a read-only API for live reads. We don't resell, train on, or aggregate tenant data across customers.
What about contract length and exit?
Annual subscription, multi-year terms get better commercial treatment. At exit you keep your data via the standard export channels. Standard SaaS data-deletion timelines apply (90 days hot, 365 days cold).
Tell us your airport.
Written proposal within five working days.