Minut is monitoring software for short-term-rental operators. Its verified capabilities include monitoring noise by decibel level with quiet hours, detecting smoking, providing occupancy signals, working with a water-leak sensor, and guest messaging. The monitoring functions require hardware, so the software subscription and the physical sensor should be treated as separate parts of the purchase.
I read the product and pricing information used for this review through a United States connection on 12 September 2026. The pricing page provides a manual selector for USD, EUR, GBP, AUD, CAD, and SEK, with USD displayed by default. That selector should not be confused with automatic country-based repricing.
The clearest way to understand the product is to start with the problem it addresses. Consider an operator responsible for 3 rental units. Messages can tell that operator what a guest reports, but a monitoring device can provide a signal about noise, occupancy, smoking, or a water leak before or without a guest complaint. The service combines those property signals with guest messaging, although the verified material does not establish that every capability is included on every plan.
This category also needs to be separated from broader operational software. A noise-monitoring service answers a different purchasing question from an account-wide host tool, maintenance system, or pricing application. Readers comparing different billing structures may find the per-user maintenance software review, the whole-account subscription review, and the percentage-of-bookings review useful. Those pricing shapes cannot be compared accurately by looking at a headline monthly figure alone.
The same principle applies here. A displayed subscription of $10 per month for a rental unit does not establish the total acquisition cost when monitoring rows require a device and the device has a separate one-time charge. For an operator considering 3 units, the first question is therefore not merely whether the monthly software total is $30. The operator also needs the unlisted hardware amount for every device required by the intended setup.
The verified basis is per rental unit per month, billed annually, but the cards do not all print that basis in the same way. Starter displays $5 per month for a single property, while Standard and Pro display their prices per month per home. The vendor’s FAQ resolves the wording by stating that plans are billed per rental unit.
I read these figures on the official pricing page on 12 September 2026. The visible cards showed Starter at $5 per month, billed as $60 per year; Standard at $10 per month per home, billed as $120 per year; and Pro at $15 per month per home, billed as $180 per year. Every visible card expressed its charge through annual billing, so I have not verified a separate month-to-month rate.
| Plan | 1 rental unit | 3 rental units | 10 rental units | Verified billing basis |
|---|---|---|---|---|
| Starter | $5 monthly equivalent; $5 × 1 = $5 | Not verified for this count | Not verified for this count | Single property; billed as $60 per year |
| Standard | $10 monthly equivalent; $10 × 1 = $10 | $30 monthly equivalent; $10 × 3 = $30 | $100 monthly equivalent; $10 × 10 = $100 | Per rental unit, billed as $120 per year per unit |
| Pro | $15 monthly equivalent; $15 × 1 = $15 | $45 monthly equivalent; $15 × 3 = $45 | $150 monthly equivalent; $15 × 10 = $150 | Per rental unit, billed as $180 per year per unit |
| Enterprise | Contact the vendor | Contact the vendor | Contact the vendor | No published figure verified |
The Standard arithmetic is the most useful reference because the vendor provided a multi-property basis. At 1 rental unit, $10 multiplied by 1 is $10 per month, or $120 per year. At 3 units, $10 multiplied by 3 is $30 per month, while $120 multiplied by 3 is $360 per year. At 10 units, $10 multiplied by 10 is $100 per month, while $120 multiplied by 10 is $1,200 per year.
Pro follows the same per-unit arithmetic. At 1 unit, the monthly equivalent is $15 and the annual bill is $180. At 3 units, $15 multiplied by 3 produces a $45 monthly equivalent, while $180 multiplied by 3 produces a $540 annual bill. At 10 units, the corresponding figures are $150 per month and $1,800 per year.
I have not extended Starter beyond its verified single-property position. Multiplying $5 by 3 would be easy arithmetic, but that would not prove that the plan can be purchased for 3 properties under the same terms. When a count is not covered by the verified plan information, the defensible answer is that I have not verified it.
Call Assist is an add-on priced at $10 per month per rental unit and billed annually with the plan. If an operator has 3 rental units and adds it to Standard, the add-on contributes $10 × 3 = $30 to the monthly equivalent. Standard contributes another $10 × 3 = $30, producing a combined monthly equivalent of $60. On an annual basis, that arithmetic is $60 × 12 = $720. These figures cover the subscription and add-on only, not the separate sensor purchase.
The subscription is not the complete bill. The monitoring rows are marked as requiring a device. The vendor’s FAQ also states that the sensor carries a one-time cost separate from the plan charge. The pricing page did not publish that sensor amount when I checked it, so I will not guess it. An operator costing 10 units can verify the $100 Standard monthly equivalent, but cannot calculate the complete first-year acquisition cost from the published subscription table alone.
This distinction matters in comparisons. A review that lists only $10 per month per home can make a hardware-dependent service look directly comparable with software-only subscriptions. It is not enough to compare $30 at 3 units with another product’s $30 account charge unless both totals include the components required to perform the advertised job.
For more examples of pricing bases that change the result, see a property-count pricing breakdown, a stepped subscription calculation, a room-based pricing calculation, and a flat-fee versus revenue-share calculation. The purpose of those links is not to declare equivalent capabilities. They show why the unit being billed matters as much as the displayed amount.
Answering guests at 11pm is the part software should do.
Start free — first 500 messagesOr book a demo callThe verified plan boundaries concern retention, portfolio support, integrations, access, and reporting. Starter is presented for a single property at $5 per month, billed as $60 per year, and includes 7-day data retention. Standard is the multi-property tier at $10 per month per home, billed as $120 per year, with OTA integrations, 30-day retention, and team access. Pro costs $15 per month per home, billed as $180 per year, and adds PMS integrations, advanced reports, and unlimited retention.
| Plan | Price shown by the vendor | Verified inclusions | Example at a verified count |
|---|---|---|---|
| Starter | $5 per month, billed as $60 per year | Single property and 7-day data retention | 1 property costs $5 × 1 = $5 monthly equivalent |
| Standard | $10 per month per home, billed as $120 per year | Multi-property use, OTA integrations, 30-day retention, and team access | 3 units cost $10 × 3 = $30 monthly equivalent |
| Pro | $15 per month per home, billed as $180 per year | PMS integrations, advanced reports, and unlimited retention | 10 units cost $15 × 10 = $150 monthly equivalent |
| Enterprise | Contact the vendor | No additional verified inclusion I can assign safely | No published total verified for 10 units |
Retention creates a concrete dividing line. Starter retains data for 7 days, while Standard retains it for 30 days. Pro has unlimited retention. An operator who needs to review an event from 20 days earlier would find that 20 is greater than Starter’s 7-day period but remains within Standard’s 30-day period. That requirement points to Standard before integrations or team access are considered.
Portfolio shape creates another boundary. Starter is identified as a single-property option, while Standard is identified for multiple properties. If a host expands from 1 unit to 3 units, I would not assume that 3 Starter subscriptions are available at $5 each. The verified multi-property calculation is Standard: $10 × 3 = $30 per month equivalent and $120 × 3 = $360 per year.
The verified product-wide capabilities are noise monitoring by decibel level with quiet hours, smoking detection, occupancy signals, a water-leak sensor, and guest messaging. I have not verified a complete plan-by-plan boundary for those 5 capabilities, so I will not assign each capability to a particular tier without evidence. The accurate statement is that they are supported capabilities, while the published plan information above identifies the verified differences among Starter, Standard, and Pro.
Noise monitoring should also be described precisely. The product monitors decibel levels; that is not the same claim as recording sound. The distinction affects how a host explains the device to guests and evaluates its purpose. For a 3-unit portfolio, the relevant operational question is whether each unit needs its own monitoring hardware, followed by the separate question of which subscription tier supplies the needed retention and access.
Other software categories draw their plan boundaries in different places. The per-property operations review, the annual-versus-monthly billing review, and the operations-platform cost review provide additional examples. A feature table is useful only when the reader keeps the billing unit, required hardware, and plan boundary together.
I can verify 2 limitations without inferring anything from silence. First, the monitoring functions do not work without hardware: the relevant rows are marked as requiring a device. Second, the pricing page does not publish the sensor price, even though the vendor states that the sensor is a separate one-time cost.
For a concrete 3-unit example, the Standard subscription can be calculated as $10 × 3 = $30 per month equivalent. The complete initial cost cannot be calculated from that page because the separate hardware figure is absent. That does not mean the sensor costs $0, and it does not justify estimating a figure from another retailer or an older review.
I will not turn an omitted row into a broader product limitation. A pricing page may be incomplete, a capability may appear elsewhere, or a boundary may differ by plan. The 2 limitations above are the only absences I have established well enough to report here.
Response speed and calendar hygiene, handled for you.
Start free — first 500 messagesOr book a demo callThe clearest fit is an operator who specifically wants property-level monitoring signals and is willing to install the required hardware. That includes a host concerned with decibel levels during quiet hours, smoking detection, occupancy signals, or water leaks. Guest messaging is also among the verified capabilities, but monitoring is what creates the distinctive hardware requirement.
Take Casper, who operates 3 Airbnb rental units in Boise and does not list them on another platform. Casper wants multi-property support, 30-day retention, team access, and the verified monitoring capabilities. Standard is the relevant published tier for that shape: $10 × 3 units = $30 per month equivalent, and $120 × 3 units = $360 billed annually. The complete first-year figure remains unavailable until Casper receives the separate price for the required sensors.
Casper should not select Starter merely by calculating $5 × 3 = $15. Starter is identified as a single-property plan, and I have not verified that it can be multiplied across 3 units. Pro would produce $15 × 3 = $45 per month equivalent and $180 × 3 = $540 per year, but Casper would need a reason to pay for PMS integrations, advanced reports, or unlimited retention rather than Standard’s verified 30-day retention.
I cannot responsibly name a property count at which this product stops being the cheap answer, because that requires verified prices and matched capabilities across alternatives as well as the missing sensor cost. For the same reason, I cannot name a count at which it becomes the obvious answer. At 1, 3, and 10 units, the subscription arithmetic is available; a universal value verdict is not.
The decision is better expressed as a requirement shape. If the operator needs device-based monitoring and accepts an annually billed per-unit subscription plus separately priced hardware, the product belongs on the shortlist. If the operator only needs another operational job, that should be evaluated in its own category rather than forcing a monitoring product into it. The turnover-software overview, maintenance-tracking overview, and host-app category map separate those jobs.
At least 1 independent directory publishes user reviews, but we do not collect reviews of other companies and I will not summarise ratings I did not gather. Readers who want that material can consult the independent review directory directly. I am not repeating a star rating, review count, quotation, reported advantage, or reported complaint from it.
What this page provides instead is verifiable pricing in the shape the vendor uses: a per-rental-unit subscription billed annually, calculated at 1, 3, and 10 units where the plan terms support those counts. Standard works out to $10, $30, and $100 per month equivalent at those respective portfolio sizes, before the separate and unpublished sensor cost.
I would use the following 6-point checklist before paying. It can be completed quickly because every item asks for a specific figure or capability rather than a general sales promise.
For a separate software need, BnBGenius Pro costs $10 per month; our pricing page also explains the free tier covering the first 500 messages. We answer guest messages on Airbnb and VRBO, request and publish host reviews, create cleaning and repair tasks after checkout, offer a voice concierge, sell empty nights and early or late checkout, and run through Telegram, but we do not provide channel management, calendar synchronization, direct bookings, pricing tools, owner accounting, SMS, WhatsApp, Facebook Messenger, Booking.com, or Expedia. We do not currently have a dedicated comparison page for these 2 products, so I would keep the monitoring decision tied to the device requirements and the separate automation decision tied to the jobs listed here.