How Much Does Airport Operational Database Software Cost in 2026?
An airport operational database build costs $120,000 to $800,000.
On this page
An airport operational database build costs $120,000 to $800,000. A focused first release covering source reconciliation into one authoritative flight record, capacity aware stand and gate allocation, and a clean publish feed to tenant systems runs $120,000 to $260,000 over 16 to 24 weeks, and a full platform adding aeronautical billing, resource allocation for desks and belts, collaborative decision making milestones and a tenant portal runs $300,000 to $800,000 across 9 to 18 months, based on Digital Heroes delivery experience. The decision that moves the number most is how many legacy systems have to keep working, because each baggage, surveillance or finance interface is its own protocol archaeology project and three of them can cost more than the entire allocation engine.
The bands an airport operational database build falls into
A focused first release runs $120,000 to $260,000 over 16 to 24 weeks in our delivery experience. That covers arbitration of your flight sources into one authoritative record with every field carrying its source, timestamp and the rule that let it win, constraint based stand and gate allocation loaded with your actual apron geometry, and a publish layer that tenants subscribe to rather than receive files from. It is a system the apron and allocation teams use in production, not a pilot.
A full platform runs $300,000 to $800,000 phased across 9 to 18 months, adding aeronautical billing with versioned tariffs, resource allocation for check in desks and baggage belts, collaborative decision making milestone emission, and a tenant portal.
Neither band assumes you rip out a vendor airport operational database. For most mid sized airports the honest answer is to keep the packaged system as the record for the fields it holds well and build the arbitration, allocation and publish layer around it. That preserves an integration estate you already paid for and avoids a migration that would consume two years without improving a single day of operations.
What drives an airport operations build up
- Each legacy interface, $25,000 to $60,000. A baggage handling system interface and a surveillance feed have different protocols, different failure modes and often a decade of local customisation, and the specification sometimes has to be bought back from the original integrator.
- Aeronautical billing, $50,000 to $110,000. Landing fees by maximum take off weight, parking beyond a free period at rates that differ between contact and remote stands, passenger charges split by domestic, international and transfer, plus noise, emissions, bridge, power and de-icing lines, each with contract level exceptions.
- Collaborative decision making, $30,000 to $70,000. Joining a network programme means emitting defined milestones with reliable timestamps, and message quality gets audited by parties outside your control.
- Multiple terminals with different operating models. Two terminals that share a runway but not a process are two rule sets with one shared record, which is harder than two separate systems.
- Discovery. The line nobody budgets. Stand and resource rules usually live in the heads of two allocators who have worked there fifteen years and have never written them down.
- Tenant count. Airlines, handlers, retail, parking, border agency, fuel and taxi all want data in their own shape, and every additional shape is a supported contract.
What keeps the number down
- Keep the vendor system underneath. Build the layer, not the stack. Amadeus Airport Management and SITA Airport Management hold plenty of fields adequately, and the value you are missing is arbitration, local rules and publishing.
- Write the apron rulebook before kickoff. Adjacency pairs, wingspan and tail height limits, stand splitting, pushback conflicts, tow thresholds and border routing. Getting these onto paper is the cheapest week of the project.
- Publish one event stream, not fourteen exports. A documented stream with a small number of supported shapes onboards a new tenant in days instead of commissioning another scheduled file.
- Defer billing to phase two. Charges are only as good as the record beneath them, so build the record first and let finance keep its monthly export for one more cycle.
- Sequence interfaces by operational dependence. Not everything must migrate at once, and an interface that only feeds a report can wait behind one that feeds a stand decision.
A worked example that adds up
A two terminal airport handling roughly seven million passengers a year with 42 stands. A SITA airport operational database stays as the record for schedule and movement fields. Fourteen tenant systems consume flight data today through scheduled exports. Baggage and surveillance interfaces are both a decade old. The airport is joining a collaborative decision making programme next year.
- Discovery and apron rule capture with the allocation team: $21,000
- Source arbitration engine over an append only event log: $76,000
- Constraint based stand and gate allocation with loaded geometry: $88,000
- Tenant publish layer with event stream, standard exchange format and webhooks: $54,000
- Integration boundary with the existing vendor database: $41,000
- Baggage handling system interface: $38,000
- Surveillance feed integration: $32,000
- Aeronautical billing with versioned tariffs and contract exceptions: $69,000
- Resource allocation for check in desks and baggage belts: $47,000
- Milestone emission and message quality monitoring: $43,000
- Tenant portal: $29,000
That totals $538,000. Add a 12 percent contingency, because one legacy interface specification will turn out to describe a system that was modified in 2016, and the committed figure is $603,000 across roughly fourteen months.
How the spend phases
- Weeks 1 to 5, about $21,000. Rule capture with the two allocators who currently hold the rulebook in their heads. Everything downstream depends on this being honest rather than aspirational.
- Weeks 3 to 18, about $76,000. The arbitration engine and event log. Nothing else is trustworthy until one record wins per field with a recorded reason.
- Weeks 8 to 20, about $41,000. The boundary with the vendor database, designed carefully so the packaged system is never bypassed silently.
- Weeks 14 to 30, about $88,000. Stand and gate allocation, which is where disruption recovery stops being a two hundred case manual rebuild.
- Weeks 20 to 30, about $54,000. The publish layer, and the point at which the operations team starts believing the platform is real.
- Weeks 24 to 36, about $70,000. Baggage and surveillance interfaces, sequenced by operational dependence rather than by convenience.
- Weeks 32 to 46, about $69,000. Aeronautical billing, built once the record has been trusted through a full season.
- Weeks 38 to 50, about $47,000. Desk and belt allocation, timed for a schedule change rather than mid season.
- Weeks 42 to 54, about $43,000. Milestone emission and message quality monitoring, ahead of the programme join date.
- Weeks 50 to 58, about $29,000. Tenant portal, last because it is a view over everything before it.
The ongoing costs nobody quotes
- Support and maintenance, 15 to 22 percent of build. On a $603,000 platform that is roughly $90,000 to $133,000 a year, and airport support is a round the clock obligation with a first flight deadline every morning.
- Legacy interface changes, $15,000 to $40,000 a year. Baggage, surveillance and finance systems get patched and upgraded by their own vendors on their own schedule, and your interface follows.
- Tariff maintenance, $8,000 to $20,000 a year. Charges change annually and sometimes mid year. Held as versioned data this is configuration, but somebody still has to make and check the change before invoicing runs.
- Tenant onboarding, $4,000 to $10,000 each. New concessions, handlers and agencies arrive continuously and each wants data in a shape.
- Milestone quality and programme audit, $10,000 to $25,000 a year. Message quality gets reviewed by partners outside your control and remediation is on your side of the fence.
- Disaster recovery and resilience testing, $12,000 to $30,000 a year. A flight record that stops updating is an operational incident, so failover has to be exercised rather than documented.
- Rule maintenance, $15,000 to $35,000 a year. New stand configurations, a resurfaced taxilane, a new carrier with a type you have not parked before. Each is a rule change with an operational consequence.
Comparing a build against your current renewal
Pull three figures rather than one. First, your vendor airport operational database licence and support. Second, what your integrator charged you last year in change requests, because at most airports that number is larger than the licence and it buys configuration rather than capability. Third, the cost of the exports nobody owns, meaning the scheduled jobs running from machines under desks that break silently until a tenant complains.
Then do the revenue arithmetic, because it usually dominates. Take your annual aeronautical revenue and work out what one percent of it is. That is the scale of a billing leak from movements missing the finance export, weights taken from a stale fleet table, and parking durations you cannot evidence when challenged. If one percent of aeronautical revenue exceeds the project cost, the business case is not really about software.
Finally, price the stand time. Eleven minutes of hold because an aircraft was allocated to a position sized for a different type is a delay with an owner, and a disruption day rebuilt by hand is a set of decisions nobody can defend afterwards. Those do not appear on any invoice and they are what the operations director is actually buying.
When buying beats building
If you are a single terminal airport under roughly two million passengers with a stable carrier mix, buy. Amadeus and SITA will sell you a configured airport operational database that does the job, the integration surface is small enough to manage, and the money you would spend on a build is better spent on the apron. We would say so rather than quote.
Buy the specialists for the specialist problems. ADB SAFEGATE is strong on the physical layer, docking guidance and gate hardware, and Veovo is genuinely good at passenger flow and queue prediction. Neither of those is a reason to build, and building your own version of either would be a poor use of capital.
The case for building starts when three things are true together: your stand and resource rules cannot be expressed in the vendor's configuration model and are therefore being applied by humans, your aeronautical revenue is large enough that a one percent billing leak exceeds the project cost, and you have more than about ten tenant systems consuming flight data so the integration layer is already your biggest operational risk. At that point the coordination logic between sources, stands, charges and tenants is the airport's operating system, and no vendor is going to encode your apron for you.
If you want that decision made properly rather than quickly, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- McKinsey estimates that digitizing the supply chain (Supply Chain 4.0) can cut lost sales by up to 75%, reduce inventories by up to 75%, and lower supply chain operational costs by up to 30%, with up to 30% lower transport and warehousing costs. Source: McKinsey & Company (2016) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
Frequently asked questions
How much does a custom airport operational database cost?
A first release covering source reconciliation into one authoritative flight record, constraint based stand and gate allocation and a tenant publish layer runs $120,000 to $260,000 over 16 to 24 weeks in Digital Heroes delivery experience. Adding aeronautical billing, desk and belt allocation, collaborative decision making milestones and a tenant portal takes the total to $300,000 to $800,000 over 9 to 18 months.
Legacy interfaces and baggage or surveillance integration are the largest cost drivers, not passenger volume.
Can we keep our Amadeus or SITA system and build around it?
Yes, and for most mid sized airports that is what we recommend. Keep the vendor system as the record for the fields it holds well, then build the arbitration rules, allocation and publish layer around it so your local constraints and integrations are yours.
Budget roughly $40,000 for the integration boundary and design it carefully so the packaged system is never bypassed silently. This avoids a two year migration that would not improve a single operational day.
What does aeronautical billing add to the build?
Between $50,000 and $110,000. Landing fees by maximum take off weight, parking beyond a free period at different contact and remote rates, passenger charges split by domestic, international and transfer, plus noise, emissions, bridge, power and de-icing lines, each with contract level exceptions negotiated per airline.
Build it in phase two rather than phase one. Charges are only as good as the record beneath them, so the arbitration layer has to be trusted through a full season first.
What does it cost to run an airport operations platform each year?
Budget 15 to 22 percent of build for support and maintenance, roughly $90,000 to $133,000 on a $603,000 platform, with support covering every hour the airport operates rather than office hours.
Add $15,000 to $40,000 a year for legacy interface changes, $8,000 to $20,000 for tariff maintenance, $12,000 to $30,000 for disaster recovery testing and $15,000 to $35,000 for rule maintenance as stands, taxilanes and carrier fleets change.
How long does it take to build and go live?
A production first release lands in 16 to 24 weeks and a full platform in 9 to 18 months. Engineering is rarely the constraint.
The schedule risk is discovery, because stand and resource rules usually live in the heads of two long serving allocators and have never been written down, and legacy interface specifications sometimes have to be recovered from the original integrator. Airports arriving with documented apron rules move noticeably faster.
Why does our stand allocation always get overridden manually?
Because the rules the allocator applies are not in the system. Adjacency restrictions, stand splitting, wingspan and tail height limits, pushback conflicts on a shared taxilane, tow cost thresholds and border control routing are local to your apron and generic allocators cannot express most of them.
Loading that geometry as data and solving against it costs roughly $88,000 at a 42 stand airport, and it turns a disruption day from a two hundred case manual rebuild into twenty genuinely hard decisions.
What does joining a collaborative decision making programme add?
Between $30,000 and $70,000 for milestone emission and message quality monitoring, plus $10,000 to $25,000 a year afterwards because partners outside your control review message quality and remediation sits with you.
There is a prerequisite most airports discover late: milestones need reliable actual times, which means a single authoritative flight record. If your sources currently disagree, fixing arbitration comes first and is not optional.
How do we justify this against our vendor licence?
Pull three numbers instead of one: the licence and support, what your integrator charged in change requests last year, and the cost of the unowned scheduled exports that break silently. The second is usually larger than the first.
Then work out one percent of your annual aeronautical revenue. That is the scale of a billing leak from missing movements, stale weights and unevidenced parking durations. If that figure exceeds project cost, the case stops being about software.
Is it worth building with one terminal and twenty stands?
Usually not, and we would say so before quoting. At that scale a properly configured packaged database handles the flight record, the allocation problem is small enough for a human with good tooling, and the tenant integration surface is manageable.
The case starts when allocation rules are applied manually because the vendor model cannot hold them, when a one percent aeronautical revenue leak exceeds project cost, or when more than ten tenant systems already depend on your flight data.
What tech stack should a custom ERP be built on?
A boring, hireable one: Digital Heroes most often ships ERPs on PostgreSQL with a Node.js or Python backend and a React frontend, hosted on AWS or Azure. The stack matters far less than the database design, because your ERP schema will outlive every framework choice. Be skeptical of any agency proposing a niche or proprietary framework, since your ability to hire maintainers later is part of the total cost.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
Who owns the source code if an agency builds my ERP?
You should, in full, and it must be written into the contract as work for hire with IP assignment on payment. At Digital Heroes every client receives the complete repository, database schemas, and deployment documentation, so they could hand the system to another team tomorrow. Walk away from any ERP proposal built on the agency's proprietary platform with ongoing license fees, because that recreates the vendor lock-in you were escaping.
Is SAP overkill for a mid-sized company?
For most companies under about 500 employees, yes. SAP S/4HANA is built for multi-entity, multi-country enterprises with implementations measured in years and seven figures, while SAP Business One, the mid-market product, still forces your processes into its mold. If your competitive edge lives in how you operate, a custom ERP scoped to your actual workflows ships faster and costs a fraction of an SAP program.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
Is customizing Odoo cheaper than building an ERP from scratch?
Usually yes in year one, and often no by year three if your workflows sit far from Odoo's assumptions. Odoo's published pricing starts around $25 per user per month and the Community edition is free, but heavy customization means every version upgrade can break your modules and needs paid rework. If you expect to rewrite more than about a third of the core flows, a scratch build with clean ownership tends to cost less over the life of the system.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
What happens to my ERP if the agency shuts down or we part ways?
If ownership was set up correctly, nothing breaks: you hold the source code, the system runs in cloud accounts you own, and handover documentation lets a new team take over. Insist on repository access from day one, admin ownership of all hosting and third-party accounts, and documentation as a contract deliverable rather than a favor. This is the single most important clause to check before signing an ERP contract.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Rohan.
Director of Web Platform Engineering · Delhi · 2 posts on the site
Published · Last updated .
