Buying a 1X NEO: A Home Robot Is Also a Privacy and Service Decision

A field guide for an early adopter considering a networked robot inside a private home, with the current manufacturer claims separated from the configuration, acceptance and legal work that determines whether the purchase is usable.

The offer is a pre-order pathway, not immediate delivery

1X currently presents two headline routes: a US $499-per-month Standard subscription and US $20,000 Early Access ownership. The order page asks for a US $200 deposit and says U.S. deliveries start in 2026. The launch announcement says purchased Early Access units receive priority delivery, while subscription delivery comes later and expansion beyond the United States begins in later markets. That is enough to evaluate the proposition, but not enough to treat a deposit as a confirmed delivery date.

The pre-order terms are explicit: the deposit puts the customer on a waitlist for an order invitation, invitation order can vary by geography and purchase route, and 1X makes no representation about when an invitation will arrive. Pricing, add-ons and descriptions may change before acceptance. A buyer should preserve the exact terms accepted, set a calendar reminder for the cancellation window, and wait for the later Terms of Sale before treating warranty, service and subscription duration as final.

The hardware is designed around a home, but specifications are not warranties

The current order page lists NEO at 5 ft 6 in and 66 lb, with a soft lattice body, tendon-drive actuation and no structural pinch points. It lists a four-hour runtime, 842 Wh battery, self-charging, 18 lb arm payload, 55 lb carry figure and 154 lb lift figure. Connectivity includes Wi-Fi, Bluetooth and 5G; perception includes stereo fisheye cameras and beamforming microphones; onboard compute is described as a 1X NEO Cortex based on NVIDIA Jetson Thor.

Those numbers are useful for planning, but 1X's pre-order terms say product specifications and performance data are general illustrations rather than warranties. Ask how lift and carry figures are measured, at what reach, for how long, and under which software mode. A soft cover reduces contact severity; it does not remove trip, fall, entanglement, dropped-object, battery or navigation risk. Home suitability must be evaluated room by room.

Map stairs, rugs, glass, mirrors, pets, children, narrow passages, wet areas, open flames, fragile objects and private rooms. Decide which doors remain physically closed and where NEO may dock. The body is listed as IP44 and the hands as IP68, which does not make the complete robot submersible or suitable for an uncontrolled shower, outdoor storm or cooking splash zone.

Expert Mode is the center of the privacy decision

1X says NEO arrives with basic autonomy and uses Redwood AI to learn and repeat tasks. For chores it does not know, an owner can schedule an Expert to remotely supervise its actions. That human-assisted model is a practical route to early utility, and it also changes the meaning of placing cameras, microphones and mobile control in a home. The important question is not merely whether data is “in the cloud.” It is when a person or service can perceive the home, what is retained and how the resident knows the session is active.

Before ordering, obtain clear answers about scheduling, authentication, visible and audible session indicators, room exclusion, recording, retention, employee access, subprocessors, model training, deletion, incident response and support access. Ask whether autonomy, remote piloting, voice features and Expert Mode can be disabled independently. Verify how household members and guests are notified and how a resident can stop a session immediately without relying on the same network connection.

A homeowner cannot consent on behalf of every visitor in every jurisdiction. Create a simple house rule: where the robot operates, when remote help may occur, which rooms are always excluded, how guests are informed and who can use the app. Do not put NEO in bedrooms, bathrooms, workspaces containing confidential material or children's areas until the privacy controls have been tested and the household accepts them.

Autonomy should be judged chore by chore

“Folding laundry” is not one capability. It includes finding the basket, separating items, manipulating deformable fabric, choosing a fold, stacking results and handling exceptions. “Tidying” requires deciding where objects belong, which can be a privacy and safety judgment rather than a motion problem. Build acceptance tests around one bounded chore and record intervention.

For example, supply ten known towels in a clear workspace, remove pets and children, and measure task completion, time, drops, incorrect placements, remote interventions and recovery from one intentionally misplaced item. Repeat on several days. A task is useful when the household spends less total time supervising, preparing and correcting it—not when one edited demonstration succeeds.

Voice interaction needs its own test. Check wake behavior, speaker recognition, command confirmation, refusal of ambiguous physical requests and what happens when music or conversation resembles a command. Mobile and VR remote control should use strong account security, revocable devices and a clear local indication. “Pilot from anywhere” is convenient only if unauthorized piloting is difficult and immediately detectable.

Service continuity matters more than nominal ownership

A networked home robot depends on replacement tendons, batteries, covers, software, model service, mobile applications and trained support. Early Access ownership does not make all of those dependencies local. Ask which functions remain after an account closure or service outage, how long security updates are promised, whether cellular service is included, who pays shipping, whether a technician enters the home, and what happens to stored household data during replacement.

The subscription route needs a complete lifecycle description: minimum duration, damage rules, normal wear, upgrade promises, service response, cancellation, return packaging and data deletion. The ownership route needs the same questions plus resale and transfer restrictions. The pre-order terms currently describe personal domestic use and prohibit resale or distribution of the pre-order; later sales terms may add the operational details that actually control the relationship.

Turn the purchase into an acceptance specification

1X NEO should be purchased against a task, not against a showreel. Write one page that describes the operating environment, the objects or payloads, the people who may be nearby, required runtime, permitted network access, maximum intervention and the evidence that constitutes success. This converts broad claims such as “general purpose,” “home assistance” or “industrial research” into a test both buyer and seller can understand.

Separate hardware acceptance from application acceptance. Hardware acceptance checks that the delivered configuration matches the order, boots cleanly, charges, reports healthy joints and sensors, executes supported reference motions, stops on command and arrives without shipping damage. Application acceptance asks whether the buyer's own task works. The seller can reasonably warrant the first without promising the second.

Ask for the complete commercial packet

For an early adopter considering a networked robot inside a private home, the acquisition route is a refundable-deposit waitlist followed by a later purchase or subscription invitation. Before money becomes non-refundable, collect the quotation, configuration schedule, warranty, software license, privacy policy, support plan, shipping terms, battery documentation, declaration of conformity where applicable and every safety or certification document the seller is willing to stand behind. Marketing pages can guide questions; signed documents allocate risk.

Have engineering, safety, security, facilities, finance and legal review the same configuration. Otherwise each group approves a different imagined robot. Engineering may picture an EDU API while finance prices the Standard unit. Security may picture offline use while the application team depends on cloud learning. Facilities may picture guarded trials while a sponsor imagines a public demonstration. Put these assumptions in one bill of materials and operating-envelope document.

Use a conservative commissioning ladder

1. Inventory without motion. Photograph shipping condition, verify serials and options, inspect batteries and record installed software.
2. Power with restraint. Establish the emergency stop, command timeout, user roles, logs and a safe recovery method before free movement.
3. Run manufacturer references. Reproduce supported health checks and basic motions on a clear surface under the documented limits.
4. Add one project variable. Introduce the buyer's sensor, model, payload or task separately so failures have an identifiable cause.
5. Repeat under realistic conditions. Measure success, intervention, energy, temperature, falls, resets and damage over enough runs to reveal variance.
6. Expand access last. People outside the trained team enter the operating area only after controls have been demonstrated and documented.

This ladder is intentionally slower than an unboxing video. It is faster than debugging simultaneous hardware, network, policy and task failures after a public demo has been scheduled.

Import, privacy and liability are configuration-dependent

Do not copy a generic duty percentage into a budget. Classification, origin, destination, declared value, battery handling and current trade measures determine the actual customs treatment. Use a broker and identify importer of record. Confirm who pays when customs requests documents or returns the shipment. Radio approvals, electrical compliance and workplace obligations likewise depend on destination and use; a seller's global availability page is not proof of local approval.

Map every camera, microphone, telemetry stream, remote-support route, mobile app and OTA service. Record destination, encryption, credentials, retention, administrator, offline behavior and deletion. Put the robot on a segmented network during evaluation and observe traffic rather than relying only on a “local mode” label. If recording workers, visitors or household members is possible, establish notice, access and retention rules before collecting real data.

Physical liability cannot be assigned by a sentence in an article. Applicable law, the sales contract, product defect, buyer modifications, operator conduct and the chosen environment all matter. The buyer should insure the actual use and preserve logs, configuration and maintenance records. Never assume the manufacturer absorbs all autonomous-motion risk, and never accept a blanket claim that it absorbs none. Get jurisdiction-specific advice for a consequential deployment.

Measure cost per accepted task, not cost per robot

The purchase price is only the first denominator. Track engineer setup time, operator supervision, failed attempts, charging, battery aging, replacement parts, service travel, software subscriptions, network service, floor-space controls and the time spent preparing the environment. Then divide by accepted task cycles under the conditions that matter. This calculation prevents a low acquisition price from hiding a platform that consumes a full-time operator, and it prevents an expensive platform from being rejected when it reliably replaces a genuinely costly process.

Set a learning budget before commissioning. Decide how many weeks, engineering hours, falls, damaged consumables and vendor support cases are acceptable before the team pauses or changes scope. Record failures as structured observations: command, software version, environment, robot state, intervention and recovery. Video is useful evidence, but it should accompany logs rather than replace them. A failed trial that identifies a repeatable boundary has value; an endless sequence of undocumented demonstrations does not.

Plan the exit while the robot is still working. Determine how accounts are closed, credentials and recordings deleted, batteries shipped or recycled, licensed software removed and hardware resold, returned or stored. A platform with no supported transfer or decommissioning route carries a residual cost that belongs in the original decision.

A purchase-order checklist

• Exact model, edition, revision, serial-number range and included end effectors.
• Compute, storage, sensors, controller, batteries, chargers, cables and case.
• SDK and firmware versions, API level, source access and update policy.
• Permitted development, commercial use, model ownership and redistribution rights.
• Safety documents, certified standards and the exact configuration in their scope.
• Price, currency, tax, Incoterms, freight, broker, duty and importer of record.
• Delivery window, cancellation, acceptance period and remedy for mismatch.
• Warranty duration, excluded uses, spare prices, service location and response time.
• Telemetry, remote access, privacy controls, retention and offline capability.
• Training, installation, maintenance schedule and safe decommissioning.

Bottom line

NEO is an early-access home service with scheduled human-assisted operation, not merely a box of autonomous hardware. The right purchase is the configuration that passes a written task, safety and service case at a defensible landed cost. Preserve the source page, quote, software version and acceptance evidence together. That record is what lets a team distinguish a capable platform from a compelling demonstration and keeps the next software update or repair from erasing the basis of the decision.