A source for the claim.
A limit to the conclusion.
Our research is useful only when readers can tell what is known, who says it, which version it describes and what still needs testing.
DROID RESEARCH · SOURCES CHECKED
Current coverage
The initial source universe is the public product documentation, developer guides and official integration repositories linked below. It is a deliberately bounded first cohort, not exhaustive coverage of robotics.
| Record type | Reviewed | Scope |
|---|---|---|
| Companies | 4 | Represented by primary sources; no complete corporate histories or financial assessments. |
| Glove models | 5 | Published decision records with cited facts, unknowns and integration questions. |
| Related robot hands | 1 | Sharpa Wave relationship recorded. Exact hardware revision unresolved; no standalone comparison published. |
| Integration examples | 1 | Manufacturer-published code. No independent operational test claimed. |
| Primary source records | 20 | Retrieved November 10, 2026; source versions retained where available. |
Evidence labels mean different things.
- Manufacturer-documented: a product page, manual or developer reference states the capability. This does not establish independently measured performance.
- Published example: identifiable code or a worked integration is available. It does not establish sustained deployment, safety approval or task success.
- Unknown: the reviewed sources do not resolve the field. It does not mean a feature is absent.
- Droid analysis: an engineering implication or proposed check derived from the cited facts. It is clearly separated from the supplier’s claim.
- Calculated scenario: an explicit formula applied to user inputs. Default values are assumptions, not a market survey.
Compare like with like.
- Keep original units and conditions with a fact. Do not equate angular resolution with tracking accuracy, a software publication rate with latency, or a hand model with independent physical sensors.
- Attach a hardware or software version where the source provides one. An unversioned page remains unversioned; the date we checked it is not its publication date.
- Keep conflicts visible. Seek a version-specific explanation before selecting one value. A newer page is not automatically evidence for an older shipped device.
- Trace compatibility at each boundary: physical mounting, power, transport, data representation, control and operating conditions. Shared interfaces alone establish only a candidate path.
- Publish a page when it answers a distinct decision and adds a useful relationship, calculation or analysis. Keep incomplete entities in the research ledger until they support more than a name and a link.
What we are checking next
- Exact glove configurations, capture licenses and complete system costs.
- Additional capture systems and documented glove-to-hand integrations.
- Dexterous hand revisions, mechanical and electrical interfaces, and public software support.
- Task-specific deployment evidence and the cost of human interventions.
The service robot database remains available elsewhere on Droid. Its older records have not all passed this evidence process and are not included in these coverage counts.
Corrections can be sent through Droid’s contact page. Include the model, version, disputed field and a primary source. Supplier identity does not determine ranking or inclusion.
Source record
- Metagloves Pro product page ↗MANUS · Metagloves Pro; undated page · Checked 2026-11-10
- SDK getting started ↗MANUS · Documentation 3.0.0 · Checked 2026-11-10
- ROS 2 getting started ↗MANUS · Documentation 3.0.0 · Checked 2026-11-10
- Nova 2 product page ↗SenseGlove · Nova 2; undated page · Checked 2026-11-10
- Nova 2 developer reference ↗SenseGlove · Nova 2; includes firmware 2.x notes · Checked 2026-11-10
- Software and headset compatibility ↗SenseGlove · Page states updated September 18, 2025 · Checked 2026-11-10
- ROS overview ↗SenseGlove · Unversioned developer documentation · Checked 2026-11-10
- Connecting devices ↗SenseGlove · Nova 2 firmware 1.x versus 2.x · Checked 2026-11-10
- UDCAP DataGlove introduction ↗UDEXREAL · UDCAP; undated documentation · Checked 2026-11-10
- Hand model and data specification ↗UDEXREAL · HandDriver 2.1.2 onward and legacy conventions · Checked 2026-11-10
- MANUS integration and retargeting repository ↗Sharpa Robotics · Commit b87bff5, May 26, 2026 · Checked 2026-11-10
- Sharpa Wave product page ↗Sharpa · Wave family; hardware revision unspecified · Checked 2026-11-10
- Metagloves Pro Haptic product page ↗MANUS · Pro Haptic; undated product page · Checked 2026-11-10
- Core license types ↗MANUS · Robotics and Motion Capture editions; undated terms overview · Checked 2026-11-10
- Nova ROS workspace installation ↗SenseGlove · Commit 30c9624, March 15, 2026; Jazzy / Ubuntu 24.04 · Checked 2026-11-10
- R1 developer reference ↗SenseGlove · R1 / formerly Rembrandt; hardware revision unspecified · Checked 2026-11-10
- R1 API: tracking conditions and prototype notes ↗SenseGlove · Prototype 0.4 test conditions; 0.5 and API filter revision notes · Checked 2026-11-10
- R1 ROS messages and force commands ↗SenseGlove · Commit 5005aff, October 27, 2026 · Checked 2026-11-10
- R1 ROS initial setup ↗SenseGlove · Commit 5005aff; Windows instructions point to WSL2 · Checked 2026-11-10
- Robotics workflow and HandDriver adaptation ↗UDEXREAL · Includes HandDriver v2.2.1 Windows / Linux Web matching feature · Checked 2026-11-10
START WITH THE WORKFLOWBring us the task.
Request a project review Bring us the task.
Let’s find the fit.
Share your environment, the job to be done, and the outcome you need to measure.