Methodology

Our finder is a constraint-matching tool, not a review-score leaderboard. It starts each robot from a neutral baseline and adjusts fit from the user's selected audience, primary goal, upfront budget, recurring-fee tolerance, desire for conversation, movement preference, camera preference and cloud-resilience preference.

Fit score

A robot gains points when it directly matches a stated requirement and loses points when it conflicts with a deal-breaker. Primary use case matters because a tactile comfort robot, a conversational social robot and a movable pet camera should not rank as substitutes merely because all three are called “robots.” The exact logic is published client-side in /assets/app.js; there is no hidden AI model deciding the ranking.

Availability adjustment

Products shown as out of stock by an official source in our dated snapshot receive a strong ranking penalty. “Check live stock” is different: we use it when storefront markup conflicts, stock varies by variant or availability cannot be stated confidently. Those products remain eligible, but their result clearly tells buyers to verify checkout.

Three different recurring-cost cases

Required product membership means the recurring fee is part of the overall service, as with ElliQ; it is included in the three-year required-cost baseline and compared directly with the user's monthly tolerance. Feature-gated conversation means the robot can still do useful things without paying, but the AI conversation the user may want requires a plan; Vector and Mia are handled this way. Optional premium content, such as Miko Max, does not count as a required ownership cost.

Offline/local score

This 0–5 editorial classification describes how much useful interaction appears to remain available without cloud services. A higher number is not always “better”; cloud-heavy robots may offer stronger conversation or remote features.

Cloud-dependence score

This 0–5 editorial classification estimates how much of the product's differentiated value depends on vendor-hosted services. It is a resilience signal, not a prediction that a vendor will shut down. Manufacturer privacy/local-processing claims are treated as claims, not independent audits.

Price and three-year cost

We prefer manufacturer pricing and label sale/reference ambiguity. The three-year required-cost baseline is current upfront price plus 36 months only when the recurring rate is required for the overall product/service. Feature-specific and optional plans are shown separately rather than silently added. The baseline excludes tax, shipping, accessories, a required smartphone when separately owned, repair and future price changes. When a paid service is included in the first three years, as with the current Sony aibo U.S. offer, a post-term renewal is not incorrectly added inside those first three years.

Dataset scope

The main finder currently covers 27 consumer products with a sufficiently clear U.S.-dollar reference and a meaningful official purchase or product path. Region-specific systems such as LOVOT and NICOBO, pre-order products such as Microduck, developer-oriented platforms such as Reachy Mini, waitlist-only launches, discontinued new-purchase products and specialist therapeutic/institutional robots may be tracked without being forced into the same retail ranking.

Source hierarchy

We prefer current manufacturer stores, official support pages and official policy pages. Independent reporting is used only when an official page does not expose a needed number clearly, and that exception is disclosed. Every important product claim should be traceable to a dated source snapshot.

Update policy

Each data snapshot carries a review date. Connected-device markets move quickly; users should always verify price, stock, privacy terms, regional support, subscription terms and feature availability immediately before purchase.