Every airport is different.
So is every quote.
We don't publish list prices. Airport scope, channel mix, integration complexity, term length, and whether the engagement covers one station or a national network all move the number meaningfully. What we publish is the model — how we charge, what's included by product, and what the process looks like. Tell us your scope; we send a written proposal within five working days.
How we charge.
Five principles that hold across every NorthSky engagement. They're how we keep the conversation about operating value, not about per-user-per-month accounting.
Per airport, not per user.
Most of the value comes from passenger interactions and operating events, not from internal seats. Per-airport billing keeps the commercial model aligned with passenger throughput and doesn't charge you to log more staff in.
Per product, modular.
Each product is independently licensed. Start with the one that fixes the sharpest pain (often AeroFeedback for the regulator quarterly, or AeroGround for the apron record), add the rest as your operating priorities grow. Nothing you start with orphans what you add next.
Annual subscription.
Billed annually. Multi-year terms get materially better commercial treatment. Quarterly true-ups available for fast-growing networks. USD pricing on request for non-Indian airports.
AI is included, not metered.
Aviation AI capabilities — multilingual NLU, multimodal complaint AI, regulator-report generation, taxi-time optimisation, runway-ops models — are included with the product they sit inside. No per-inference charge, no per-API-call meter.
What we charge for.
Each product has its natural billing unit. The unit changes the math; the principle (per-airport, annual, AI included) stays the same. The numbers are scoped, not published.
The passenger-voice platform. Channel mix, language coverage, regulator-pack scope, and complaint-loop integration all shape the proposal. See AeroFeedback →
Intelligent complaint platform. Six intake channels (QR live capture, kiosk, mobile, web, AI chatbot, email/SMS/WhatsApp); five AI models; multi-org routing; SLA monitored. Pairs with AeroFeedback for the closed-loop survey-to-resolution flow. See AeroResolve →
Apron, stand, and gate monitoring. Hardware install (cameras + edge boxes) and software subscription priced together per stand or pier; existing CCTV reused where coverage is adequate. See AeroGround →
The operating brain of the AOCC. Core (turn-cycle skeleton) priced per airport; each integrated feed (AeroGround, AeroTaxi, AeroRunway, AeroFOD) priced under its own product. See ATOMS →
Taxiway optimisation. Priced per runway or per movement-area-pair, depending on the surface-radar / MLAT topology you already run. See AeroTaxi →
Runway-ops monitoring, throughput, and optimisation. Priced per runway; configuration changes with the runway-end optics decision. See AeroRunway →
Airfield FOD detection. Three deployment modes (mobile sensor vehicle, fixed airside poles, stand mounts) priced per zone — runway, taxiway, apron — and per mode. See AeroFOD →
The video-AI capability spine across the camera-driven products. Included with AeroGround, AeroFOD, AeroRunway. Terminal-side deployment available via design-partner programme. See AeroVision →
From first call to signed proposal.
The conversation.
Your airport, your channel mix, your regulator deadlines, your top three operating frustrations. Where the network sits today and where you want it in twelve months.
The scoping.
We map your scope to the product set, the deployment modes, the integration complexity, and the rollout sequence. Stand survey if AeroGround is in scope; runway survey if AeroFOD / AeroTaxi / AeroRunway.
The proposal.
A written proposal with line-item pricing, phased rollout plan, commercial terms, and the integration template. Within five working days of the first call. National-authority engagements take longer because the portfolio is bespoke.
The pilot.
Pilots are typically scoped in days, live in weeks. The AAI pilot was production-ready in a single quarter. Subsequent rollouts to the same customer use the proven template — typically 4–6 weeks per airport.
One call moves everything else.
We don't publish prices because publishing prices is publishing the wrong number. Tell us your scope; we'll send a written proposal scoped to your operating reality, your network, and your timeline.
Common questions.
Why don't you publish prices?
Because the right number depends on scope — channel mix, stand count, runway count, integration complexity, language coverage, regulator format, term length. A list price would mislead you in one direction or the other. We publish the model (per airport, per product, AI included, annual subscription); the numbers come in a written proposal within five working days of the first call.
Why per airport instead of per user?
Most of the value comes from passenger interactions and operating events, not internal seats. Per-airport billing keeps the commercial model aligned with passenger throughput and avoids charging you to log more staff in.
What about national networks?
National-authority engagements (the AAI engagement sits here) are bespoke — written across the portfolio with volume terms, dedicated environments where required, customer-managed keys where required, and a named Technical Account Manager. Proposal timelines for these are longer than the standard five working days because the scope is wider.
Can we start with one product and add more later?
Yes — that's the design. AeroFeedback is a common first step for the regulator quarterly; AeroGround for airports prioritising the apron record. Other products plug into the same tenancy on the same login, billed as you turn them on. No re-implementation.
Are AI features metered or charged per inference?
No. Aviation AI capabilities are included with the product they sit inside. No per-inference charge, no per-API-call meter. New AI capabilities reach a product as they mature; capabilities currently in pilot become standard as they're production-validated. See the AI governance posture for the full policy.
What's included in implementation?
Configuration for your terminals, channels, language mix, and regulator templates; surveyor onboarding where AeroGround or AeroFeedback surveyor app is in scope; integration template for A-CDM, AODB, DCS, ATC log; one round of regulator-format report tailoring; SSO integration. Custom integrations beyond the template are scoped separately.
Do you offer USD pricing?
Yes. Non-Indian customers are quoted in USD. We don't publish USD ranges publicly because they vary materially by region — your local cost of compliance, regulatory framework, and channel mix all shape the proposal.
How quickly can you go live?
The AAI pilot was production-ready inside a single quarter. Subsequent rollouts to the same customer use the proven template and typically go live in 4–6 weeks per airport. AeroGround per pier is roughly six weeks from civil-works clear; AeroFOD mobile is days; fixed airside is weeks.
Tell us your airport.
Your channel mix, your stand count, your runway count, your regulator deadlines, your timeline. We'll send a written proposal scoped to your operating reality within five working days.