Why it matters
What it tends to unlock
Remote access, orchestration, and software maintenance, ecosystem fit across apps, fleets, and smart-home layers, and faster rollout of updates, telemetry, and support workflows.
Connectivity
Single normalized label
SSH
SSH appears across 1 tracked robots, concentrated in Humanoid. Use this page to understand why the signal matters, who relies on it most, and which live profiles deserve the first comparison click.
Tracked robots
1
Ready now
0
Manufacturers
1
Public prices
1
What to verify
Do not stop at the label
Real protocol support, not just marketing labels, offline behavior, pairing friction, and network dependency, and whether the stack stays useful when the vendor service changes.
Coverage
1 category
The heaviest concentration is in Humanoid (1). Top manufacturers include Rotaku (1).
Research brief
Research first. Sweep the roster second.
The useful questions here are how common SSH really is, which robot classes depend on it, and which live profiles are worth opening before you compare the whole stack.
Verified 30d
1
1 in the last 90 days
Top category
Humanoid
1 tracked robots
Paired most often with
Developer SDK, URDF/simulation support, whole-body policy training workflow, and optional NVIDIA Jetson Orin NX compute for local vision models, motion policies, and robot applications; public model details are not disclosed., Onboard Sensors Not Fully Disclosed, and Optional 2D/3D LiDAR navigation kit
Decision brief
What matters before you compare implementations
Where it helps most
- remote access, orchestration, and software maintenance
- ecosystem fit across apps, fleets, and smart-home layers
- faster rollout of updates, telemetry, and support workflows
What to validate
- real protocol support, not just marketing labels
- offline behavior, pairing friction, and network dependency
- whether the stack stays useful when the vendor service changes
Evidence basis
What this route is grounded in
- Aggregated from each robot's `specs.connectivity` field in ui44 data.
Source pack
Official reference links
Market snapshot
Use the structure first: which categories lean on SSH, which manufacturers repeat it, and what usually ships beside it.
Lead category
Humanoid
1 tracked robots currently anchor this label.
Most repeated manufacturer
Rotaku
1 tracked robots make this the clearest manufacturer-level signal on the route.
Most common adjacent signal
Developer SDK, URDF/simulation support, whole-body policy training workflow, and optional NVIDIA Jetson Orin NX compute for local vision models, motion policies, and robot applications; public model details are not disclosed.
1 shared robots pair this component with Developer SDK, URDF/simulation support, whole-body policy training workflow, and optional NVIDIA Jetson Orin NX compute for local vision models, motion policies, and robot applications; public model details are not disclosed..
Top categories
| # | Name | Usage |
|---|---|---|
| 1 | Humanoid | 1 robot |
Top manufacturers
| # | Name | Usage |
|---|---|---|
| 1 | Rotaku | 1 robot |
Commonly paired with SSH
How to read the market
Structure first, prose second.
Category concentration tells you where the component is actually doing work, manufacturer repetition shows whether the signal is market-wide or vendor-specific, and pairings reveal which neighboring technologies usually ship alongside it.
At a glance
Kind
Connectivity
Tracked robots
1
Ready now
0
Public prices
1
Official sources
1
Variants normalized
1
Robot directory · SSH
The old card wall is replaced with a featured first-click strip and a dense inventory table so the route behaves like a serious directory.
Directory briefing
Featured first, dense sweep second.
Open the clearest profiles first, then sweep the full inventory in a denser table. Featured cards are selected by readiness, image quality, and official source availability, so the first click is usually the most informative one.
Ready now
0
Public price
1
Official links
1
Featured now
1
How to scan this directory
Use the shortest credible path through the roster.
- Featured cards: start with the strongest documented profiles to understand real implementation quality fast.
- Inventory table: sweep the whole market once you know which profiles deserve serious comparison.
- Compare intent: use status, official links, and standout specs before treating the label itself as proof.
Best first clicks
Open these before sweeping the full inventory
These robots score highest on readiness, public detail quality, and image clarity, making them the fastest way to understand how SSH shows up in practice.
DO
Pre-order
Humanoid
Rotaku
Since 2026
Domo
Domo is a compact humanoid robot platform from Rotaku for developers, researchers, educators, and early-stage robotics teams. Rotaku's official page lists the base Domo at 90 cm, 20 kg, 23 degrees of freedom, and 70 Nm actuator torque, with a modular design, replaceable end effectors, a wide-FOV depth camera, onboard battery, integrated compute and motor control, wireless access, SSH development access, and no external control cables required during operation. The reservation page positions Domo Basic for programmable humanoid interaction and basic motion control, while Domo Developer adds an SDK, whole-body policy training workflow, and URDF/simulation support. Optional kits cover teleoperation, NVIDIA Jetson Orin NX compute, dexterous hands, LiDAR navigation, extra batteries, and policy-training workflows. Rotaku says the current batch has limited availability and that delivery typically takes 2-4 weeks once fulfillment begins, but exact public ship timing and production volume are not disclosed.
Public price
$2,999
Official reservation page lists Domo…
Size
90 cm (35.4 in)
Shortlist read
Commercial intent is clear, but delivery timing should be validated.
Full inventory · 1 robots
Compact mobile scan: status, price, standout context, and links stay visible without sideways scrolling.
Domo
Pre-order
Rotaku · Humanoid
Price
$2,999
Standout
Size · 90 cm (35.4 in)
Quick answers
FAQ
The short version of what this label means in the ui44 catalog, where it matters, and how to compare it without over-reading the marketing copy.
Frequently Asked Questions
How common is SSH in the database?
SSH currently appears on 1 tracked robots across 1 manufacturers. That makes this route useful for both deep research and fast shortlist scanning, not just one-off editorial reading.
Which robot categories lean on SSH the most?
The strongest concentration is in Humanoid (1). Category mix is the fastest clue for whether this component behaves like baseline plumbing or a more selective differentiator.
Does SSH usually show up on ready-to-buy robots?
0 of the 1 tracked profiles are currently marked Available or Active. That means the label has live market relevance here, but you should still open the profiles with public pricing or official links first before treating it as a clean buyer signal.
What should I compare first on this page?
Start with readiness, official source quality, and the standout spec column in the inventory table. On component routes, those three signals usually remove weak profiles faster than reading every descriptive paragraph.
What usually ships alongside SSH?
The strongest shared-stack signals here are Developer SDK, URDF/simulation support, whole-body policy training workflow, and optional NVIDIA Jetson Orin NX compute for local vision models, motion policies, and robot applications; public model details are not disclosed. (1), Onboard Sensors Not Fully Disclosed (1), and Optional 2D/3D LiDAR navigation kit (1). Use those pairings to branch into adjacent component pages when one label is too narrow for the decision.
Are there enough public price points to benchmark this component?
1 matching robots currently expose public pricing. That is enough to create directional context, but not enough to treat one price bracket as the whole market. Use the directory to find the transparent profiles first, then widen the sweep.
Which manufacturers are worth opening first?
Start with Rotaku (1). Repetition across manufacturers is often the clearest signal that the component is part of a stable market pattern rather than a one-off marketing callout.
Reference library
The original long-form component research is still here, but collapsed so the main route can prioritize hierarchy and scan speed.
Fundamentals
The baseline explanation of what SSH is, why it matters, and how to think about it before comparing implementations.
Fundamentals
The baseline explanation of what SSH is, why it matters, and how to think about it before comparing implementations.
What Is SSH?
SSH is a connectivity component found in 1 robot tracked in the ui44 Home Robot Database. As a connectivity technology, SSH plays a specific role in enabling robot perception, interaction, or operation depending on its implementation in each platform.
At a Glance
Connectivity components define how a robot communicates with other devices, networks, and cloud services. Connectivity determines whether a robot can receive software updates, stream data, integrate with smart home systems, and be remotely controlled.
Key Points
- Includes wireless protocols (Wi-Fi, Bluetooth, Zigbee), wired interfaces (Ethernet, USB), and cellular
- Enables software updates, cloud integration, and remote control
- Determines smart home ecosystem compatibility
In the ui44 database, SSH is categorized under Connectivity components. For a comprehensive explanation of all component types, consult the components glossary.
Why SSH Matters in Robotics
A robot's connectivity stack determines its ecosystem compatibility and long-term value. Limited connectivity can mean the robot operates in isolation, cannot be updated, or requires specific hub hardware.
Broad connectivity support means more smart home platform integrations
Enables over-the-air updates that improve the robot over time
Allows remote monitoring and control from anywhere
SSH Adoption
Used in 1 robot across 1 category — Humanoid, indicating specialized use across the robotics industry.
How SSH Works
Wireless connectivity uses radio frequencies to transmit data between the robot and other devices. The robot's firmware manages protocol switching and connection prioritization automatically.
1
Wi-Fi
High-bandwidth local network access for data-heavy tasks like video streaming
2
Bluetooth
Direct device-to-device pairing for initial setup and nearby peripherals
3
Zigbee / Z-Wave
Low-power mesh networking for IoT device coordination
4
Cellular (4G/5G)
Operation beyond home Wi-Fi range for outdoor or commercial robots
SSH Integration
Implementation varies by robot platform and manufacturer. Each robot integrates SSH differently depending on system architecture, use case, and target tasks. Integration with other onboard connectivity modules and the main processing unit determines real-world performance.
Technical notes and use cases
Deeper technical framing, matched technology profiles, and the longer use-case treatment for SSH.
Technical notes and use cases
Deeper technical framing, matched technology profiles, and the longer use-case treatment for SSH.
SSH: Technical Deep Dive
Beyond the high-level overview, understanding the technical foundations of connectivity technologies like SSH helps buyers and researchers evaluate implementations more critically.
Engineering Principles
Wireless connectivity relies on electromagnetic radiation at specific frequency bands regulated by international standards bodies.
- Wi-Fi: 2.4 GHz and 5 GHz bands (Wi-Fi 6E/7 extends to 6 GHz)
- Bluetooth: 2.4 GHz ISM band with frequency hopping
- Zigbee/Thread: 2.4 GHz with mesh networking topologies
- Cellular: licensed spectrum bands for wide-area coverage
Performance Characteristics
For robotics, latency is often more critical than raw bandwidth.
Bandwidth
Data transfer rate — video streaming needs several Mbps sustained
Latency
Delay between send/receive — remote control needs sub-100ms
Range
Wi-Fi: ~30m indoors through walls, 100m+ in open spaces
Reliability
Packet loss rate and connection stability under interference
Technological Evolution
Robot connectivity has evolved from simple serial cables to sophisticated multi-protocol wireless systems.
Early robots: basic infrared remote control or proprietary radio links
Standardized protocols (Wi-Fi, Bluetooth) dramatically improved interoperability
IoT-specific protocols (Zigbee, Z-Wave, Thread) enabled efficient smart home integration
Matter standard (2022): unifying smart home communication under a single application layer
Known Limitations
Wireless connectivity faces inherent challenges in home environments.
- Signal attenuation through walls, floors, and ceilings creates dead zones
- Interference from growing wireless device density degrades performance
- Security: every wireless connection is a potential attack surface
- Cloud dependency: robots requiring internet for basic functions fail during outages
- Wireless communication is a significant power consumer for battery-powered robots
Use Cases & Applications for SSH
Key application domains for connectivity technologies like SSH.
Smart Home Integration
Connectivity allows robots to communicate with other smart home devices — thermostats, lights, locks, cameras, and appliances. A well-connected robot can serve as a mobile hub or coordinator for your smart home, executing routines that involve multiple devices across different rooms.
Remote Monitoring & Control
Wi-Fi and cellular connectivity enable users to monitor and control their robot remotely via smartphone apps. This is particularly valuable for security robots, pet-monitoring robots, and home assistants, allowing owners to check in, receive alerts, and issue commands from anywhere.
Over-the-Air Updates
Network connectivity is essential for receiving firmware and software updates that improve the robot's capabilities, fix bugs, and patch security vulnerabilities. Robots without reliable connectivity may become outdated quickly and miss important safety updates.
Cloud AI Processing
Some robots offload computationally intensive AI tasks to cloud servers via network connections. This allows smaller, more affordable robots to access powerful AI capabilities like advanced natural language processing, image recognition, and complex decision-making that would be impossible with on-device hardware alone.
Multi-Robot Coordination
In commercial and industrial settings, connectivity allows multiple robots to coordinate their activities, share maps, divide tasks, and avoid interfering with each other. This fleet management capability requires reliable, low-latency communication between robots and a central coordination system.
10 Capabilities Across 1 robot
23 Degrees of Freedom
Bipedal Locomotion
Humanoid Interaction
Basic Motion Control
Full-Body Control Research
Manipulation Experiments
Whole-Body Policy Training
URDF and Simulation Support
Optional Teleoperation
Reinforcement and Imitation Learning
Visit each robot's detail page to see which capabilities are available on specific models.
Market breakdown and adjacent routes
Manufacturer mix, specs context, price context, category overlap, and adjacent components worth branching into next.
Market breakdown and adjacent routes
Manufacturer mix, specs context, price context, category overlap, and adjacent components worth branching into next.
SSH Across Robot Categories
SSH spans 1 robot category — from consumer to research platforms.
Technologies most often paired with SSH across 1 robot.
Wide-FOV depth camera
100%
Optional 2D/3D LiDAR navigation kit
100%
Onboard sensors not fully disclosed
100%
Wireless developer access
100%
Developer SDK, URDF/simulation support, whole-body policy training workflow, and optional NVIDIA Jetson Orin NX compute for local vision models, motion policies, and robot applications; public model details are not disclosed.
100%
Browse the full components directory or see the components glossary for detailed explanations of each technology.
Price Context for Robots With SSH
1 of 1 robots with SSH have public pricing, ranging $3.0k – $3.0k.
Lowest
$3.0k
Domo
Average
$3.0k
1 robot with pricing
Highest
$3.0k
Domo
Alternatives to SSH
235 other connectivity technologies tracked in ui44, ranked by adoption.
Wi-Fi
116 robots
Bluetooth
65 robots
Ethernet
34 robots
Not Officially Disclosed
21 robots
Bluetooth 5.2
13 robots
Wi-fi 6
13 robots
5G
9 robots
App Control
8 robots
Browse all Connectivity components or use the robot comparison tool to evaluate how different connectivity configurations perform across specific robot models.
SSH in the Broader Robotics Industry
Robot connectivity is evolving rapidly as the smart home ecosystem matures and new wireless standards emerge. Supporting the right mix of protocols is a strategic decision for manufacturers.
Key Industry Trends
Wi-Fi 6/7 adoption
Better performance in dense device environments typical of modern smart homes with dozens of connected devices
Matter protocol
Unified smart home standard backed by Apple, Google, Amazon, and Samsung — simplifying cross-platform integration
5G expansion
Opening new possibilities for outdoor robots, delivery platforms, and commercial service robots beyond home Wi-Fi
Industry Adoption Snapshot
SSH is adopted by 1 robot from 1 manufacturer in the ui44 database, providing a data-driven view of real-world deployment patterns.
Integration & Ecosystem Compatibility
Platform compatibility, voice integration, and AI capabilities across robots with SSH.
Platform Compatibility
Rotaku developer SDKURDF simulation workflowsSSH developer accessOptional teleoperation kitsOptional NVIDIA Jetson Orin NX compute unitOptional LiDAR navigation kit
Buyer and operations guidance
The long-form buyer, maintenance, and troubleshooting material kept available without forcing it into the main scan path.
Buyer and operations guidance
The long-form buyer, maintenance, and troubleshooting material kept available without forcing it into the main scan path.
Buyer Considerations for SSH
If SSH is an important factor in your robot selection, here are key considerations to guide your decision.
What to Look For in Connectivity Components
Wi-Fi version
Dual-band (2.4/5 GHz) is preferred for reliability in congested environments
Smart home integration
Does it work with your existing ecosystem (Alexa, Google Home, HomeKit)?
Range & reliability
Important for large homes, multi-floor coverage, or outdoor robots
Data privacy
Does the robot require cloud connectivity to function, or can it operate locally?
Currently, none of the robots with SSH are listed as directly available for purchase. They are in pre-order status. Monitor the individual robot pages for updates.
How to Evaluate SSH
Integration Quality
A component is only as good as its integration. Check how the manufacturer has incorporated SSH into the overall robot design and software stack.
Complementary Components
Review what other connectivity technologies are paired with SSH in each robot — see the related components section.
Category Fit
Make sure the robot's category matches your use case. SSH serves different roles in different robot types.
Manufacturer Track Record
Consider the manufacturer's reputation for software updates, support, and component reliability.
Compare Before You Buy
Use the ui44 comparison tool to evaluate robots with SSH side by side.
Maintenance & Longevity: SSH
Overview
Connectivity components are generally among the most reliable parts of a robot, as they consist entirely of solid-state electronics with no moving parts. However, the evolving nature of wireless standards and smart home ecosystems means that connectivity capabilities can become outdated even while the hardware continues to function perfectly.
Durability & Reliability
Wireless radio hardware (Wi-Fi, Bluetooth, Zigbee modules) is extremely durable under normal operating conditions. These components typically outlast the useful life of the robot itself.
- •Antenna placement and design affect long-term reliability — internal antennas are protected from damage but may offer slightly less range than external designs.
- •Connectors for wired interfaces (USB, Ethernet) can wear over many plug-unplug cycles.
- •Environmental factors rarely affect wireless components, though extreme heat can reduce radio performance and battery-powered wireless modules may see range reduction as battery voltage drops.
Ongoing Maintenance
Connectivity components require minimal physical maintenance. The primary ongoing concern is software-level maintenance: keeping firmware updated, managing Wi-Fi network changes (new router, changed password), and maintaining compatibility with evolving smart home platforms.
- •When a robot has trouble connecting, the issue is almost always software or network configuration rather than hardware failure.
- •Periodically checking for firmware updates and ensuring the robot's network settings match your current infrastructure prevents most connectivity issues.
Future-Proofing Considerations
Connectivity is an area where future-proofing requires particular attention. Wireless standards evolve: Wi-Fi 6E and Wi-Fi 7 offer significant improvements over older standards, and a robot purchased with Wi-Fi 5 may not benefit from a new router upgrade.
- •The Matter smart home standard is still maturing, and early implementations may have compatibility gaps.
- •When possible, choose robots with proven support for current-generation wireless standards and manufacturers that demonstrate a commitment to ongoing software updates.
- •Robots that support multiple connectivity protocols offer more flexibility as the ecosystem evolves.
For the 1 robot in the ui44 database using SSH, we recommend checking the individual robot pages for manufacturer-specific maintenance guidance and support documentation. Each manufacturer has different support policies, update frequencies, and warranty terms that affect the long-term ownership experience of their connectivity technologies.
Troubleshooting & Common Issues: SSH
Connectivity issues can make even the most capable robot frustrating to use. Wi-Fi drops, Bluetooth pairing failures, and smart home integration problems are among the most commonly reported issues. The good news is that most connectivity problems stem from network configuration rather than robot hardware, making them resolvable without manufacturer support.
Robot frequently disconnects from Wi-Fi
Likely Causes
- Weak signal strength is the primary cause, especially when the robot operates far from the router or behind thick walls.
- Network congestion from too many connected devices, router firmware issues, and interference from neighboring Wi-Fi networks on the same channel can also cause intermittent drops.
- Some robots struggle with dual-band routers that use the same SSID for both 2.4 GHz and 5 GHz bands.
Resolution
- Check Wi-Fi signal strength at the robot's dock location and common operating areas using a phone Wi-Fi analyzer app.
- Move the router or add a mesh Wi-Fi node to improve coverage in weak areas.
- If your router broadcasts a single SSID for both bands, try creating separate SSIDs and connecting the robot to the 2.4 GHz network, which offers better range through walls.
- Ensure your router firmware is current.
Robot does not appear in smart home platform
Likely Causes
- Account linking between the robot manufacturer's app and the smart home platform may have expired or failed.
- The robot and smart home hub may be on different network subnets or VLANs that block device discovery.
- Some smart home integrations require the robot to be running specific firmware versions.
Resolution
- Unlink and re-link the robot's account in the smart home platform settings.
- Verify that the robot and smart home hub are on the same local network and subnet.
- Check the manufacturer's compatibility notes for your specific smart home platform version.
- Restart both the robot and the smart home hub after re-linking.
Bluetooth pairing fails repeatedly
Likely Causes
- Previous pairing records may be corrupted on either the robot or the phone.
- Distance or physical obstructions between the phone and robot during pairing can cause failures.
- Some phones have aggressive Bluetooth power management that disconnects low-energy peripherals.
Resolution
- Remove the robot from your phone's Bluetooth paired devices list and factory reset the robot's Bluetooth connection through its settings menu.
- Keep the phone within one meter of the robot during pairing.
- Disable battery optimization for the robot's companion app to prevent the system from killing background Bluetooth connections.
When to Contact the Manufacturer
- Contact the manufacturer if the robot cannot maintain any Wi-Fi connection even when positioned next to the router, if the Wi-Fi or Bluetooth module appears completely non-functional, or if connectivity issues begin suddenly after a firmware update.
- Hardware-level radio failures are rare but do occur and require professional repair.
For model-specific troubleshooting, visit the individual robot pages for the 1 robot using SSH. Each manufacturer provides model-specific support resources and diagnostic tools for their connectivity implementations.
What to do next
Stay in the catalog flow
This page should hand you off to the next useful comparison step, not strand you at the bottom of a long detail route.
1
Widen the layer
Browse all Connectivity
Open the full connectivity workbench when SSH is only one part of the decision and you need the broader market map.
2
Side-by-side check
Compare the strongest live profiles
Move from label-level research into direct robot comparison once you know which profiles are documented well enough to trust.
3
Adjacent signal
Open Developer SDK, URDF/simulation support, whole-body policy training workflow, and optional NVIDIA Jetson Orin NX compute for local vision models, motion policies, and robot applications; public model details are not disclosed.
This is the most common neighboring component on robots that already use SSH, so it is the fastest next branch if you need stack context.