Motion Lab
Workflow, supported files, screenshots, outputs, privacy, validation, access, and FAQs for the open-beta movement-analysis workspace.
Read Motion Lab documentationProduct and company resources
Documentation
Start with product scope, methods, data boundaries, and the right support path.
Documentation is organized around what a visitor needs to evaluate before relying on a product: intended use, workflow, supported inputs, output boundaries, validation evidence, privacy, and current maturity.
ErgoThrive
Current product scope, professional workflow, calculation evidence, storage model, validation boundary, and evaluation access.
Read ErgoThrive documentationHF Studio
Closed-beta workflow, controlled records, traceability, privacy, validation limits, and access boundaries for EDU and Professional editions.
Read HF Studio documentationB1 Ergonomics
Catalogue scope, evidence states, demonstration-data boundaries, supported records, and the explicit absence of purchasing claims.
Read B1 Ergonomics documentationMotionLab Performance
On-device iOS workflow, supported activities, local data model, experimental metrics, validation limits, and current access state.
Read MotionLab Performance documentationResearch and validation
Research philosophy, validation stages, known limitations, sample datasets, reports, publications, and technical notes.
Review research evidenceTrust Center
Security, privacy, storage, authentication, MFA, incident response, vulnerability reporting, and the compliance roadmap.
Open the Trust CenterLicensing
Separate information for research projects, academic teaching, institutional evaluation, and future organizational access.
Review licensing pathsHow to evaluate a product
Begin with the product page, then review its validation statement, known limitations, privacy model, and current access stage. A feature list alone is not enough for research or professional adoption.
- Confirm the intended use and excluded uses
- Review inputs, outputs, and data handling
- Assess validation evidence against your protocol
- Document any institutional or professional review
Documentation status
Public documentation describes the current company and product position. It is not a substitute for a signed agreement, organization-specific security review, protocol, or qualified professional judgment.
Need a specific answer?
Send a focused, non-confidential question.
Identify the product, workflow, and document you reviewed so support can route the question accurately.