One wearable
shouldn’t decide
what matters.

Two body slots. One for the environment.

A reusable core. Three swappable sensor pucks. You choose what each configuration measures, and you get the raw data underneath it.

Start the conversation How it works
The OpenPulse wearable band: a woven grey strap with a metal sensor module set into it.

The choice today

Two bad options.

  1. Adapt

    Bend a consumer device to fit

    It measures what its maker decided to measure and hands back a score instead of a signal. Your question stops where their product roadmap stops.

  2. Build

    Build your own from scratch

    Electronics, firmware, enclosure, certification, manufacturing. Years of engineering and a budget most teams do not have, and a fixed sensor set at the end of it.

  3. Configure

    Configure one

    Keep the core, the radio, the enclosure and the software. Change only the part that senses. That is the whole of what we are building.

Sensor pucks

PPG

Built and tested

PPG sensor puck: a circular metal housing with a black optical sensor die at its centre.

Optical pulse. Heart rate, variability and perfusion at the wrist.

EDA

Built and tested

EDA sensor puck: a circular metal housing with two gold-plated skin electrodes.

Electrodermal activity across two gold electrodes. Arousal and load.

Environment

Built and tested

Environment sensor puck: a circular metal housing with a brushed steel plate and a central intake port.

The air around the wearer. Temperature, humidity and volatiles.

Reuse the core.
Change the sensing.

OpenPulse is a modular wearable sensor platform built around a reusable core and swappable sensor pucks.

The core carries the battery, the radio and the clock. The pucks carry everything that changes. When the question changes, you swap a puck, not the product.

Sensor slots
2 body, 1 environment
Battery life
48 h+ per charge
Mainboard
36 × 20 mm
Core module
XIAO nRF52840 Sense
Exploded view of the OpenPulse core: retaining ring, sensor board, metal shell, main PCB, chassis and two further pucks with gold pogo pins.

The interface

Every puck lands on the same contacts.

A single mechanical and electrical interface across the whole range. A puck we design next year drops into a core built today.

Contacts
Pogo pads, I²C
Retention
Neodymium magnets
Swap
Tool-free
Macro photograph of a sensor puck’s two gold-plated electrode pads seated in a black bezel.

The signal path

Puck Core Your system

Raw signal, not a score. Most wearables hand back a number their maker invented and keep the measurement behind it. Fine for a consumer app, useless for research or a safety case.

  1. Puck

    Raw sensor data, straight off the die.

    Optical AFE, I²C

  2. Core

    Samples, timestamps and buffers every channel.

    Zephyr RTOS, buffering

  3. Bluetooth

    A reliable link that survives a real work floor.

    Bluetooth Low Energy

  4. Your system

    Your pipeline, your models, your decisions.

    Raw stream, API in build

  • The measurement itself

    Timestamped signal as the sensor produced it, so your own analysis sits on top of the data rather than on top of somebody else's interpretation of it.

  • Into your systems

    An API into the tools you already run, rather than a dashboard you have to log into. In development, and shaped by the first pilots.

  • No fee to read your own data

    You own the deployment and what it records. Access to your own measurements is not a subscription.

You receive the underlying raw data. Production API in development.

Example configurations

A machinist in safety glasses working at a press, wearing an OpenPulse band on his wrist.

Workforce safety

Monitor strain and environment together, so the picture of a shift is a whole one.

A researcher in a white lab coat inspecting an OpenPulse band at a workbench.

Research & performance

Change the sensing between studies without changing the platform or the pipeline.

A wrist wearing an OpenPulse band, holding a plate with a slice of mouldy bread.

Environment-aware work

Track the conditions that affect people and product, where the work actually happens.

Where the hardware is

What works today,
and what does not.

The platform works. Here is exactly how far that goes, so nothing comes as a surprise midway through a pilot.

  1. Working now

    Core and pucks, together

    All three sensor pucks are built and tested. The mainboard recognises each one over the interface we designed, and the assembled device runs battery powered for over 48 hours, transmitting sensor data over Bluetooth.

  2. Current milestone

    Out of our hands

    Getting units onto people who did not build them. External testers wearing configured devices through real days, which is the only way to learn what bench testing cannot tell us.

  3. Next

    Configured pilots

    Devices built around a specific partner question, with the raw stream landing in their systems. The production API is being built alongside them.

These are working prototypes, not production units. The case and strap are still prototype parts, and certification is ahead of us. Everything above is where it genuinely stands.

Ready when you are

Tell us what you need to measure.

If a configuration of this platform answers a question you have, we would rather hear it early than late.

Start the conversation

Built by
people who
build.

We’re engineers building the platform we wish we’d had, because we kept hitting the same wall: one wearable, one fixed set of sensors, one set of questions you’re allowed to ask.

  • Mateo MamaladzeCo-founder, CEO
  • Juan Rivera ChopinaudCo-founder, CTO
  • Roman DaugavetCo-founder, Head of Software

Based in Munich. Fabrication and prototyping through the UnternehmerTUM MakerSpace at TU Munich.

The three founders of OpenPulse standing together, one wearing the band.

Recognition

  • 1st in Europe Blue Ocean Student Entrepreneur Competition, 2026. Over 23,000 students from 173 countries.
  • 1st nationally STARTUP TEENS, 2026. One of seven national category winners from 1,482 projects.
  • Top 14 nationally Jugend gründet, 2025/26. Invited to pitch from 1,461 teams.

Tell us about your workflow

What should this configuration measure?

We’re choosing which pucks to build next based on real workflows. Tell us yours.

Or write to us directly at contact@openpulse.eu.

  1. You tell us what you need to measure, and in what setting.
  2. We work out whether a configuration of the platform answers it.
  3. If it does, we build that configuration and you run it.

Your configuration

  • Body 1empty
  • Body 2empty
  • Environmentempty

Load pucks in the sensor section and they’ll travel with your message.

We reply to every message. No list, no newsletter.