From sensor signals to usable movement data.

Sense OS connects device control, sensor processing and partner applications without requiring every team to rebuild the software stack.

An engineer reviewing movement and plantar-pressure data while a participant walks through a biomechanics lab

The five Sense OS layers.

Each layer has a defined job, from configuring an insole to delivering a metric inside a partner application.

  1. Device

    Commissioning, power modes, sleep timing, sensor cycles, accuracy settings, security configuration, firmware updates and supported wireless behavior.

  2. Signals

    Pressure, motion and environmental readings with structured export for downstream analysis.

  3. Baseline

    Personal ranges, balance and load distribution, and long-term detection of meaningful changes from a person's usual movement.

  4. Modules

    Research, rehabilitation, performance, occupational and wellness workflows built from shared movement measures.

  5. Connect

    Integration libraries, partner APIs, device fleets, application integrations and white-label delivery.

A common movement engine for different applications.

Sense OS is planned to calculate reusable measures once, then apply them in workflows appropriate to each partner and intended use.

Sensor acquisition

Pressure, motion, temperature and humidity recorded by both insoles for later analysis.

Activity and gait context

Step events, cadence, speed, elevation and activity-aware processing on edge.

Personal baselines

Load, timing and movement differences compared with the person's own history.

Decision support

Recovery, fatigue and risk-oriented summaries developed for defined research or professional workflows.

Application modules.

The roadmap groups applications by workflow rather than presenting every possible use case as a separate product.

Safety, quality and validation are built around intended use.

StepSense already applies these engineering practices throughout development, building the records, traceability and technical documentation needed for future partner certification.

Risk and usability

We use the ISO 14971 standard to connect hazards with controls and measurable requirements, and IEC 62366-1 to address use-related risk.

Software lifecycle

We apply IEC 62304 practices across architecture, implementation, verification, traceability, maintenance and problem resolution.

Safety and security

IEC 60601-1 principles inform our work on basic safety and essential performance. IEC 81001-5-1 guides threat analysis, communications, update integrity and vulnerability management.

Engineering controls

Firmware is developed using MISRA-compliant coding, supported by static analysis, configuration control, fault-injection testing, watchdogs, range checks, explicit invalid-data states, strong peer review and testing procedures.

Formal certification has not yet been submitted. Once a partner product, intended use and target market are defined, the evidence and documentation produced through this process can form the basis of a submission to the relevant certification or regulatory body.

Build on Sense OS.

Our integration libraries support Android, iOS, Windows, macOS, Linux and the web. Qualified partners can discuss hardware control, data access and application requirements.