AirDNA Review: The Three US Prices, and Why the Page Reprices by Country

I approached this review as a verification exercise rather than an opinion piece. The available record establishes three displayed United States prices and a per-plan billing basis, but it does not establish plan names, property allowances, feature boundaries, trial terms, or verified limitations. I will separate those confirmed facts from the questions a prospective subscriber still needs to ask.

That distinction matters when comparing software costs. A price attached to one account, one plan, one property, or one listing can produce very different totals. Readers researching the broader category can start with our overview of Airbnb analytics tools, then use this review to examine the narrower pricing evidence available for this particular vendor.

What is AirDNA?

AirDNA is a software vendor with multiple displayed plan prices. That is the limit of what I can establish from the verified vendor record without inventing a product description or an intended customer profile. The record contains no verified capability list and no verified statement about whether the product is aimed at a host with one property, an operator with ten properties, or another type of customer.

The pricing evidence used on this page was read on 2026-09-10 through a United States connection. That location is material because the vendor’s page changes the displayed amount according to the visitor’s location and does not provide a visible country or currency switcher. A reader can therefore encounter a dollar-denominated page that differs from the version another reader sees.

Consider a concrete research example. If I opened the page from one United States connection and a reader in Europe opened it the same minute, we could record two different amounts while each believed we had seen the definitive price. The dollar sign alone would not settle which regional version was on screen. For this review, I use only the three United States amounts in the verified AirDNA record and exclude the non-US amount entirely.

I also avoid turning related host questions into assumed product capabilities. Market selection, listing performance, and property operations are distinct jobs. Our resources on choosing a short-term-rental market, finding occupancy rates, and improving a listing can help readers define the question they need software to answer, but they do not prove what this product does.

How much does AirDNA cost?

The verified billing basis is per plan. It is not verified as a per-property price, a per-listing price, or a price that should be multiplied by the number of rentals. That means I cannot take a displayed amount and multiply it by three merely because an operator has three properties.

The United States record contains three displayed prices from AirDNA: $125, $34, and $400. The record does not map those amounts to named plans, billing intervals, property allowances, or feature packages. I therefore report the values exactly as captured, and do not annualize them or assign them to a particular portfolio size.

This table may look less satisfying than a row of invented totals, but it preserves the difference between a plan and a property. If the $34 amount covered an entire plan, multiplying it by three would be wrong. If it were a monthly property rate, failing to multiply it could be wrong. The verified record settles neither question, so the defensible total at each count remains unverified.

Why can’t I turn the three prices into portfolio totals?

The record gives three amounts but no verified correspondence between those amounts and one, three, or ten properties. There is also no verified billing interval attached to each figure. For example, multiplying $34 by three properties would be straightforward arithmetic, but it would rest on an unverified assumption that $34 applies once to each property. The same issue affects any attempt to scale $125 or $400 by a portfolio count: the multiplication is easy, while the billing premise is missing.

I would use the vendor’s pricing page to confirm the live plan names, billing interval, and portfolio allowance immediately before purchase. I would also record the country from which I viewed it. The verified evidence says a United States visitor saw $125, $34, and $400 on 2026-09-10, but it does not authorize me to attach additional meaning to those figures.

How should a host compare the price?

Start with the question rather than the displayed number. A prospective buyer researching one market may need a different plan from an operator evaluating ten properties, but the verified record does not tell me which plan either person should select. Write down the actual portfolio count, the required capability, the billing interval, and the plan that contains that capability before comparing totals.

For example, suppose Emiel is evaluating three properties in one town. He should not multiply $34 by his property count until the vendor confirms that $34 is a property-based amount at all. He should instead record “three properties, one required workflow, one selected plan,” then copy the total displayed at checkout. This keeps a per-plan price from being silently converted into a per-property price.

Hosts still defining their research question may find it useful to compare occupancy rates by city, examine what an occupancy rate means, and review high-occupancy markets. Those resources help frame the decision, but they do not change the unverified relationship between the three displayed prices and a specific property count.

What do you actually get on each AirDNA plan?

The verified record contains 3 displayed United States prices but no plan-by-plan capability list. I therefore cannot verify what is included at $34, $125, or $400, nor can I assign any feature to a higher or lower plan.

Readers should consult the vendor’s plan comparison and verify every required capability before subscribing. I would not infer a plan boundary from price order, because a larger number does not by itself establish what the plan contains.

If the purpose of the purchase is to understand demand, pricing, operations, or listing performance, write that job down precisely. Our explanations of Airbnb search ranking and ways to increase occupancy illustrate how different questions can appear related while requiring different evidence.

What does AirDNA not do?

The verified record contains 0 established absences, so I have not established a limitation worth reporting; silence on a pricing page does not prove that a capability is unavailable.

Who is AirDNA right for?

I cannot responsibly declare this product right for a particular portfolio shape because the verified record contains no audience description, property allowance, or capability list. I can, however, show how a buyer should test suitability without confusing the number of listings with the number of plans.

Emiel’s example has one town, three properties, and the same platform mix for every property: each rental is offered on Airbnb and VRBO. That produces 3 properties × 2 platforms = 6 platform listings. It does not automatically produce six billable items, three billable items, or one billable item because the verified basis is per plan.

At what count does it become the cheaper choice?

I cannot establish that count. Doing so would require a verified relationship between each plan price and the number of properties or listings it covers, followed by a like-for-like comparison against a defined alternative. Neither component appears in the verified record.

For Emiel, the proper question is not whether six platform listings make the software cheap. It is whether one selected plan covers his three-property use case and contains the capability he needs. If the answer requires a different plan, he should compare the actual checkout amount rather than multiplying one of the recorded prices.

At what count does it become the obvious choice?

I cannot establish that count either. An “obvious” threshold would need evidence about both price and capability at the same portfolio size. The available evidence provides three displayed prices but no verified plan boundaries, so naming a threshold such as three or ten properties would be invented precision.

A buyer can still make the decision concrete. For a one-property operator, record the total for one selected plan. For Emiel’s three properties, record whether the same plan still applies. For a ten-property portfolio, ask whether the plan, allowance, or price changes. These three observations produce a usable comparison without assuming that a per-plan amount scales linearly.

Readers building a broader software shortlist can also examine our guide to apps for hosts and the review explaining a room-based pricing structure. Different billing units deserve separate calculations; a room, property, platform listing, and whole plan are not interchangeable.

What do AirDNA users say in their reviews?

I do not collect user reviews of other companies, and I will not summarize ratings, advantages, complaints, or quotations that I did not gather. Readers can inspect the reviews published on Capterra directly; what this page offers instead is a check at 1, 3, and 10 properties, based on the per-plan pricing record read through a United States connection on 2026-09-10, with every unsupported portfolio total marked as unverified.

What should you check before subscribing to AirDNA?

I would use a short purchase checklist and complete it while the pricing page and checkout screen are open. Ten minutes is enough to record the critical fields, but only if the buyer resists filling gaps with assumptions.

1. Confirm the billing basis. The verified basis is per plan. Ask whether one plan covers the full account, one market, one property, a defined quantity, or another unit. For Emiel’s three-property portfolio, the key question is whether he buys one plan or more than one—not whether he should automatically multiply a displayed amount by three.

2. Write down the billing interval beside the amount. The verified record contains $34, $125, and $400, but it does not preserve a confirmed monthly or yearly label for each figure. Do not annualize $34 as $34 × 12 or divide $400 by 12 unless the live page clearly identifies the period. The arithmetic would be simple; the unsupported premise would be the problem.

3. Record the viewing country. The pricing page changes by visitor location and has no visible country or currency switcher. The figures used here were viewed through a United States connection on 2026-09-10. A dollar sign without a country note is not enough to reproduce the result.

4. Enter the real property count. Test one, three, and ten properties only if those counts reflect the decision you are making. Emiel should test three because he has three properties; he should not use the one-property display and assume the result scales as 1 × 3.

5. Separate properties from platform listings. Emiel has three properties and two platform listings per property, giving six platform listings. Ask which count the selected plan recognizes. Never assume that six visible listings create six charges when the published basis has been recorded as per plan.

6. Identify the required capability before selecting a plan. The verified record does not map capabilities to prices. Write one required job in plain language, then confirm which plan contains it. If it sits on a higher plan than expected, use that plan’s checkout total in the comparison.

7. Save the final total. Capture the selected plan, billing interval, portfolio allowance, country, and checkout amount together. A note containing only “$34” cannot later explain whether the figure was monthly, yearly, account-wide, or connected to a particular plan.

For adjacent purchasing questions, our reviews cover costs framed around one, three, and ten properties, another three-count software comparison, and a separate portfolio-cost review. The purpose of reading them is not to transfer their billing logic to this vendor, but to see why every comparison must preserve the original pricing unit.

It is also worth separating market research from operational software. We build no pricing tool ourselves, and our pages on analytics-tool selection, pricing tools and the owner workflow define different jobs. A buyer should choose the job first and compare plans only after confirming that the required capability is included.

BnBGenius Pro costs $10 per month; the free tier includes the first 500 messages, all features, and requires no card. We answer Airbnb and VRBO guest messages around the clock, request guest reviews and publish host reviews, create cleaning and repair tasks after checkout, offer a Voice Concierge for an additional $7 per month per unit, and support upsells for empty nights, early check-in, and late checkout. We do not provide channel management, calendar synchronization, direct bookings, pricing tools, owner accounting, SMS, WhatsApp, Facebook Messenger, Booking.com, or Expedia; current details are on our pricing page.