Airport Operational Database Software: Buy the Core, Build the Layer, or Neither
The threshold is whether your stand and resource rules can be expressed inside a vendor configuration model. If they can, buy a packaged airport operational database, abbreviated to AODB from here, and configure it properly.
On this page
The threshold is whether your stand and resource rules can be expressed inside a vendor configuration model. If they can, buy a packaged airport operational database, abbreviated to AODB from here, and configure it properly. If your allocators are applying rules by hand because the model cannot hold adjacency pairs, stand splitting, tow thresholds and border routing, no amount of configuration will fix that, and the layer around the vendor core is yours to build at $120,000 to $260,000 for a first release over 16 to 24 weeks. Single terminal airports under roughly two million passengers should buy and stop there; most airports above about three million with more than one terminal land on the hybrid.
When is off the shelf genuinely the right call here?
If you are a single terminal airport under roughly two million passengers a year with a stable carrier mix, buy. Amadeus Airport Management and SITA Airport Management will sell you a configured AODB that does the job, the integration surface is small enough for one person to hold in their head, and the money you would spend on a build is better spent on the apron. We say this before quoting and lose the work, and it remains the right advice.
Buy the specialists for the specialist problems, at any size. ADB SAFEGATE is strong on the physical layer, docking guidance and gate hardware. 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 when the products already work and the hardware relationships already exist.
There is a third buy case worth stating plainly. If you already own a vendor AODB and your complaint is that reporting is slow or the interface is dated, that is a configuration and training problem rather than a software problem. Replacing a functioning system of record because the screens look old is the most expensive way to solve a cosmetic complaint, and the migration will consume two years without improving a single operational day.
When does a custom build actually pay off?
Three conditions have to be true together, not one of them alone.
Your stand and resource rules cannot be expressed in the vendor's configuration model and are therefore being applied by humans. Adjacency restrictions where a large aircraft on one stand blocks the neighbour, stands that split into two narrowbody positions or combine into one widebody, wingspan and tail height limits per position, pushback conflicts on a shared taxilane, jet bridge compatibility by door position, tow cost thresholds and border control routing are local to your apron. Generic allocators cannot hold most of them, which is why your allocator overrides the system every morning.
Your aeronautical revenue is large enough that a one percent billing leak exceeds the project cost. That leak is not hypothetical. It comes from movements that never reach the finance export, maximum take off weights read from a fleet table nobody has updated since the airline changed subfleet, and parking durations you cannot evidence when an airline challenges the invoice.
And you have more than about ten tenant systems consuming flight data, which means the integration layer is already your biggest operational risk. Most airports at that point have a graveyard of scheduled exports, several running from a machine under somebody's desk, each one breaking silently until a tenant complains.
When those three hold together, 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.
How do they compare on the things that matter in this industry?
Source arbitration. The packaged products carry source priority configuration, which is genuinely useful, and what they configure is a generic priority ladder. What an airport needs is a rule set that says accept registration from the airline until a defined point before estimated landing then freeze it, accept actual on block from the handler unless surveillance disagrees by more than a set margin in which case raise an exception rather than pick a winner silently, and never let a billing relevant field change after invoicing without an audit entry. That is operating policy, and it changes when your handler mix changes.
Rule expressiveness in allocation. Ask any vendor to load your adjacency pairs and stand splitting rules during evaluation rather than after signature. This is the ceiling that decides the whole question, and it is verifiable in an afternoon.
Billing traceability. Charges are formulas over the flight record. What separates systems is whether each invoice line links back to the exact record and the exact tariff version, so a dispute takes minutes rather than a fortnight, and whether tariffs are held as versioned data so a mid year change needs no release.
Publishing. One documented event stream with a small number of supported shapes, plus a plain interface for partners who cannot consume the industry format, onboards a tenant in days. Fourteen scheduled exports onboards a tenant in weeks and fails silently in between.
Data portability. Whatever you run, establish in writing how the flight record leaves it. Airports buy systems that live for fifteen or twenty years, and the exit terms matter more here than in almost any other category.
What does total cost of ownership look like at your scale?
A first release covering source arbitration into one authoritative flight record, constraint based stand and gate allocation with your geometry loaded as data, and a tenant publish layer runs $120,000 to $260,000 over 16 to 24 weeks in Digital Heroes delivery experience. A full platform adding aeronautical billing with versioned tariffs, resource allocation for check in desks and baggage belts, collaborative decision making milestones and a tenant portal runs $300,000 to $800,000 across 9 to 18 months.
The lines that move the number are structural rather than cosmetic. Each legacy interface costs $25,000 to $60,000, because a baggage handling system interface and a surveillance feed have different protocols, different failure modes and a decade of local customisation, and the specification sometimes has to be bought back from the original integrator. Aeronautical billing adds $50,000 to $110,000. Joining a collaborative decision making programme adds $30,000 to $70,000. Stand allocation at a forty stand airport sits near $88,000.
Running costs are heavier than most software categories because an airport has a first flight deadline every morning. Support and maintenance runs 15 to 22 percent of build, and it covers every hour the airport operates rather than office hours. Add $15,000 to $40,000 a year for legacy interface changes on other vendors' release schedules, $8,000 to $20,000 for tariff maintenance, $12,000 to $30,000 for disaster recovery testing that is exercised rather than documented, $15,000 to $35,000 for rule maintenance as stands and taxilanes and carrier fleets change, and $4,000 to $10,000 for each new tenant you onboard.
Set that against your renewal honestly rather than optimistically. If the vendor system holds everything you need and change requests are rare, the renewal wins and you should say so in the paper. If your integrator's change request line already exceeds the licence, you are funding development without owning any of it, and the fair comparison is against that spend rather than against the subscription.
What does the hybrid look like, and when is it the honest answer?
For most mid sized airports the hybrid is the answer we recommend, and it is not a compromise. Keep the packaged AODB as the record for the fields it holds well, and build the arbitration, allocation and publish layer around it. Budget roughly $40,000 for the integration boundary and design it carefully so the vendor system is never bypassed silently.
This preserves an integration estate you already paid for. It also avoids the failure mode that kills these projects, which is a two year migration that consumes the operational sponsor's patience before anything improves on the apron.
Sequence inside the hybrid by operational dependence. Arbitration first, because nothing else is trustworthy until one record wins per field with a recorded reason. Allocation second, because that is where a disruption day stops being a two hundred case manual rebuild and becomes twenty genuinely hard decisions. The publish layer third, and it is usually the point at which the operations team starts believing the platform is real. Billing last, once the record has been trusted through a full season, because charges are only ever as good as the record beneath them.
One prerequisite catches airports out. Collaborative decision making milestones need reliable actual times, which means a single authoritative flight record. If your sources currently disagree, fixing arbitration is not an optional extra, it comes first.
Which should you choose, by operator size and stage?
Single terminal, under two million passengers, twenty stands, stable carriers. Buy a configured packaged AODB. The allocation problem is small enough for a human with good tooling and the tenant surface is manageable.
Two to three million passengers, one terminal, growing carrier mix. Buy, and start writing the apron rulebook down. Adjacency pairs, wingspan limits, stand splitting, tow thresholds and border routing on paper is the cheapest week you will ever spend, and it is what makes a later decision quick.
Three to ten million passengers, more than one terminal, vendor AODB already installed. Build the layer, not the stack, at $120,000 to $260,000. This is the most common honest answer we give, and the integration boundary at roughly $40,000 is the line that makes it safe.
Ten million and above, multiple terminals, joining a collaborative decision making programme. The full platform at $300,000 to $800,000 is defensible and it should still be phased across 9 to 18 months, with arbitration ahead of milestones rather than alongside them.
Any airport where aeronautical revenue is large and billing is a monthly spreadsheet export. Work out one percent of that revenue before you do anything else. If it exceeds the project cost, the decision has stopped being about software.
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.
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
Frequently asked questions
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, stand allocation and publish layer around it so your local constraints and integrations belong to you.
Budget roughly $40,000 for the integration boundary and design it so the packaged system is never bypassed silently. This avoids a two year migration that would not improve a single operational day.
What does it actually cost to replace a vendor AODB outright?
Far more than the licence difference, and the cost is mostly other people's systems. Every tenant export, every handler feed, every finance interface and every baggage or surveillance connection has to be rebuilt and cut over against an operation that has a first flight every morning.
That is why the layer approach exists. It preserves the integration estate you already paid for, and it lets you move the parts that are failing without touching the parts that are not.
Our integrator charges for every change. Does that change the maths?
It usually is the maths. Pull three figures rather than one: the licence and support, what your integrator charged in change requests last year, and the cost of the scheduled exports nobody owns that break silently until a tenant complains.
At most airports the second figure is larger than the first, and it buys configuration rather than capability. If you are paying that every year to express rules the model cannot hold, you are already funding development without owning any of it.
How long does it take before allocators actually use a new system?
A production first release lands in 16 to 24 weeks. Engineering is rarely the constraint.
The schedule risk is discovery, because stand and resource rules usually live in the heads of two allocators who have worked there for fifteen years and have never written them down, and legacy interface specifications sometimes have to be recovered from the original integrator. Airports that arrive with a documented apron rulebook move noticeably faster and pay less.
Should we build our own version of ADB SAFEGATE or Veovo?
No. ADB SAFEGATE is strong on the physical layer, docking guidance and gate hardware, and Veovo is genuinely good at passenger flow and queue prediction. Both are products with active roadmaps and hardware relationships you would otherwise have to build from nothing.
Integrate with them instead. The gap those products leave is not passenger flow or docking, it is the arbitration and allocation logic that sits between your sources, your stands, your charges and your tenants.
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 one percent of aeronautical revenue exceeds project cost, or when more than ten tenant systems already depend on your flight data.
Should aeronautical billing be in the first release?
No. Charges are formulas over the flight record, so build the record first and let finance keep its monthly export for one more cycle. Billing belongs in phase two, once arbitration has been trusted through a full season.
When it does arrive, expect $50,000 to $110,000 covering 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 with contract exceptions per airline.
How do we stop every new tenant becoming another scheduled export?
Publish one documented event stream with a small number of supported shapes, including the industry exchange format for partners who can consume it, plus a plain interface and a webhook option for those who cannot. New tenants then subscribe rather than commission another file.
Budget $4,000 to $10,000 per tenant onboarding afterwards. That is real and recurring, since concessions, handlers, agencies and fuel suppliers arrive continuously, and each one still wants the data in a particular shape.
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.
Will a custom ERP scale as we grow from 50 to 500 employees?
Yes, if it is designed for that from the start, which mostly means clean database design, permissions that handle new departments, and modules that stay separable. Adding users to software you own costs nothing in licenses, the opposite of the per-seat scaling penalty on NetSuite or Dynamics. What does need budget as you grow is new modules and integrations, so keep a small standing development arrangement rather than restarting a vendor search every two years.
How do we migrate years of data from our old system without losing anything?
Through a staged migration with a parallel run, never a single cutover weekend. The data gets extracted and cleaned early, loaded into the new ERP while the old system stays live, and both run side by side for two to four weeks so your team can verify counts, balances, and open orders match. In Digital Heroes ERP projects, data cleaning consistently takes longer than the technical transfer, so it starts in week one, not at the end.
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 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.
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.
How long does custom ERP development take?
Plan on 3 to 4 months for the first working module and 6 to 12 months for a full multi-module rollout. In Digital Heroes delivery experience the schedule risk is data migration and integration testing, not feature coding, so we stage go-lives module by module instead of one big-bang launch.
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.
Can we keep our current ERP and just build custom modules around it?
Often yes, and it is frequently the smartest first move. Digital Heroes regularly builds custom scheduling, quoting, or warehouse tools that sit on top of SAP, NetSuite, or Odoo through their APIs, which fixes the painful 20 percent without a risky replacement. The hybrid route costs a fraction of a full rebuild and tells you within months whether a bigger migration is even necessary.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
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
Published · Last updated .
