Modular biosensor platform

Not another wearable.
A platform.

Configurable sensor hardware, open data access and flexible integration, built around replaceable sensor pucks.

Explore hardware Talk to us
Scroll to explore
The problem

Most wearables are closed by design.

Fixed sensor stacks
Locked, black-box data flows
One-size-fits-all software
The platform inside

OpenPulse is different.

A reusable wearable base. Replaceable sensor pucks. Customer-controlled data. Integration into your own systems.

01 - Main PCB

The reusable core

Compute, wireless, power management and the interface between sensor modules and software.

The base stays. The configuration changes.
02 - Skin-side slots

Signals from the body

Skin-facing slots designed for future biosignal modules such as optical, electrical or thermal sensing.

03 - Outward-facing slot

The world around the wearer

Not every useful signal comes from the body. OpenPulse leaves room for environment-facing sensing.

04 - Sensor pucks

Configure around the use case

Pucks make OpenPulse configurable. Partners define what to measure; the hardware can evolve around it.

The puck is the business model.
05 - Software and API

Built to integrate

Designed to connect sensor data to apps, dashboards, research tools, safety workflows or partner platforms.

06 - Data ownership

Your data flow, not ours

Built around the idea that companies and users should understand and control how biosensor data is captured and integrated.

07 - Built to evolve

Repairable and upgradeable

Replaceable modules do not only create more use cases. They make hardware easier to repair, upgrade and adapt over time.

From modules to solutions

Configure biosensing around your product.

OpenPulse lets partners combine wearable hardware, sensor modules and software integration into a system that fits their use case.

Start a pilot conversation See configurations
Stage Prototype platform in active validation
Hardware Working main PCB, puck boards in development
Focus B2B pilots with concrete sensor and data needs
Platform thesis

A wearable foundation companies can configure instead of reinventing.

OpenPulse separates the wearable into reusable platform hardware, swappable sensing modules and software integration. The goal is not to sell one fixed device. The goal is to help partners build their own biosensing product layer.

Partner product App, dashboard, workflow
OpenPulse software API, export, integration layer
Wearable base Main PCB, wireless, power, firmware
Sensor pucks Use-case-specific sensing modules
01

Configure the sensor stack

Pick the sensing direction around a partner use case: body-facing, environment-facing or experimental developer modules.

02

Own the data path

Design the data flow around the partner system instead of locking it inside someone else's app.

03

Validate honestly

Main PCB works. Sensor pucks exist as PCBs and components, with assembly and signal validation next.

The platform, by design

Built modular from the first board.

1
Reusable platform base
One core reused across every configuration.
3
Sensor slots per device
Two skin-facing, one outward-facing.
B2B
Primary market
Built for pilots, integrations and white-label directions.
API
Integration mindset
Data access designed around partner systems.
Example configurations

One architecture. Multiple directions.

The same foundation, configured around different signals and use cases. These are candidate directions, not finished product lines.

Human Signals

Body-data experiences

Skin-facing biosignal modules for research, fitness platforms, biofeedback and corporate wellness.

OpticalThermalElectrical
Safety / Environment

Context awareness

Environment-facing modules for workplace and safety-related contexts such as heat, air and surroundings.

TemperatureAir qualityUV / heat
Developer / Open

Room to experiment

For teams who want deeper access, transparent data flows and the freedom to build their own thing.

Open APIData exportSDK vision
OpenPulse is currently looking for concrete B2B use cases and pilot partners.
Partner motion

From use-case question to configured prototype.

01

Define the signal problem

What needs to be sensed, in what context, by whom, and how often?

02

Select a sensing direction

Skin-facing, environment-facing or a custom puck concept around the partner need.

03

Shape the data path

Define export, API, dashboard or integration requirements before pretending the hardware is finished.

04

Build and validate

Prototype, test signal quality, verify mechanical fit and decide whether a pilot makes sense.

Where we are today

Ambitious, but honest.

OpenPulse is an early-stage platform with a working main PCB and sensor-puck hardware in active development.

Read the hardware status
Built In progress Planned / open
  1. Done

    Concept and competitions

    The platform thesis - modular, open, data-sovereign biosensing - has been shaped through early concept work and competitions.

  2. Done

    Main PCB designed, assembled and tested

    The reusable core works: compute, wireless, power management and the module interface are up and running.

  3. In progress

    Sensor-puck PCBs and components in hand

    Puck boards and parts exist. Next up: assembly, reflow and bring-up of the first sensing modules.

Pilot partners

Building something that needs wearable biosensor data?

Let's explore whether OpenPulse can become the hardware layer for your product.

Talk to the founders