本页提供简体中文版 · 点击切换为中文 This page is also in English · Switch to English
PregOS by Saharvi

Wearable partner programme · A Saharvi partnership initiative

Building the next generation of wearable-powered wellbeing

We are seeking an OEM/ODM partner to help develop a branded wearable that integrates directly with our own mobile application and intelligence platform.

The first application it will serve is Lunelle, our maternal wellbeing companion, built on PregOS.

Where we are: looking for partners. No device has been selected or manufactured.

Saharvi’s management and technology team will be in Guangzhou and Shenzhen from 1 to 6 November 2026. If you would like to meet them, say so in the form.

Smart ring
Screenless wristband
Concept illustration — not an actual product

About PregOS

The intelligence platform underneath

PregOS turns supported observations into an organised record that can be understood over time — the layer that makes contextual, data-informed wellbeing experiences possible.

  1. Ingest

    Takes in supported observations: what a person records herself, and readings from devices she chooses to connect.

  2. Organise

    Keeps every source distinct and arranges observations into one structured record. A device reading never overwrites something she entered herself.

  3. Derive

    Works out series, trends and continuity over time — for example, how complete this week’s sleep record is.

  4. Enable

    Returns structured observations that each application turns into its own experience. PregOS draws no screens and writes no messages of its own.

Lunelle is the first application built on PregOS. The platform is designed so that other applications can build on it too.

Introducing Lunelle

The first application the wearable will serve

Lunelle is a maternal wellbeing companion, designed around the journey of planning a pregnancy, pregnancy and motherhood. The wearable will supply everyday wellbeing data; PregOS will make the supported data useful in Lunelle’s maternal context.

Lunelle is in development and has not yet launched publicly.

What this means for a hardware partner

  • Her record stays on her phone. Lunelle has no user accounts and keeps no cloud copy of her record, so we favour integrations that deliver data directly to the phone.
  • Permission one metric at a time. Each type of data is requested only when she chooses to use it.
  • Shown as measured, not graded. Lunelle shows readings as they are. It does not attach scores, rankings or “on track” labels to them.
  • Wellbeing, not diagnosis. Lunelle is not a medical device, and the wearable is not intended to diagnose, predict or prevent any condition.
  • Already reading everyday data. Lunelle can already read steps, sleep and heart-rate data from Apple Health and Health Connect. A dedicated wearable would deliver that data to Lunelle directly.

Who does what

PregOS

The underlying platform: data integration, normalisation, intelligence and interpretation.

Lunelle

The consumer application and first use case — where she sees her everyday data.

Our partner

The device: hardware, firmware, sensors, and the SDK, BLE interface or API.

The proposed wearable

Two form factors under evaluation

Smart ring

Worn day and night: everyday steps, activity and heart rate, then overnight sleep, resting heart rate and skin temperature.

Screenless wristband

A wristband with no display. The phone is the screen; the band measures and synchronises. Ideally the sensor pod comes out of the strap — off the shelf or as an ODM option — and goes into a clip or an innerwear holder.

Something else?

If you make a wearable better suited to this experience, propose it.

Concept illustration — not an actual product

The intended experience

  1. She wears the device.
  2. The device measures the wellbeing metrics it supports.
  3. It synchronises with Lunelle through the integration we agree.
  4. Lunelle displays her everyday metrics — no separate vendor app to install.
  5. PregOS adds context where appropriate, such as her stage of pregnancy.

The final device, sensor package and technical architecture remain open to discussion with qualified partners. We prefer to evaluate existing ODM hardware before commissioning fully custom hardware.

Requirements

What we need from a partner

Items marked Required are what we need in order to proceed. Preferred and If supported items strengthen a proposal, but are not conditions.

Hardware

  • RequiredEveryday metrics: steps, distance, active minutes, active energy, sleep duration and heart rate
  • If supportedOvernight and recovery: sleep stages and timing, resting heart rate, HRV, respiratory rate, blood oxygen (SpO₂) and skin temperature
  • PreferredWomen’s health: a skin-contact temperature sensor (state the part number), resolution 0.1 °C or better, sampled at least every 5 minutes overnight. Cycle features must be based on temperature, not a calendar
  • PreferredData quality: a timestamp, wear detection and sampling rate with every value
  • RequiredSuitable sensors, with documented measurement quality
  • RequiredComfortable overnight; practical battery life, charging and durability
  • RequiredSamples available for evaluation
  • PreferredFor a wristband: a removable sensor pod with a clip or innerwear holder — off the shelf, or as an ODM option. Please quote tooling cost and lead time
  • RequiredProprietary scores and regulated features (ECG, blood pressure, glucose) may be present, but must be possible to switch off

Software and integration

  • RequiredIntegration into our own app on iOS and Android
  • RequiredA Flutter plugin is preferred; a native iOS/Android SDK or full BLE protocol documentation is accepted — we will build the Flutter bridge
  • RequiredDirect access to the supported data
  • RequiredNo mandatory separate consumer-facing vendor app
  • RequiredWorks with no vendor account and no internet connection
  • RequiredFirmware updates (OTA) can be run from our app, through your update library
  • RequiredA clear statement of cloud dependencies and data portability — and, for any vendor cloud, the country that hosts it. Data about users in India falls under India’s Digital Personal Data Protection Act, 2023
  • RequiredDocumentation of which outputs are measured, estimated or derived
  • RequiredFor each metric, the data tier you can provide — A, B or C, explained below
  • PreferredAn SDK overview and data-field list shared before any sample purchase. We will sign an NDA
  • PreferredDirect-to-phone synchronisation (BLE or on-device SDK), with no mandatory cloud

Commercial and partnership

  • RequiredUnit prices at 100, 500, 1,000 and 5,000 units, for the standard and the branded product, FOB Shenzhen — and the sample price
  • PreferredA price for a pilot or validation batch of 20–50 units
  • RequiredCustomisation options and tooling costs
  • RequiredDevelopment and production timelines
  • RequiredWarranty, firmware and security updates, long-term support and production continuity
  • RequiredCertifications held, with test evidence: CE and FCC, and for India a WPC ETA for the Bluetooth radio and BIS registration where the product falls under it
  • RequiredWhether you own the factory or are a trading company, and where the factory is
  • To be negotiatedIP ownership and any exclusivity terms

Nothing on this page offers or assumes exclusivity, ownership or volume commitments. Those are settled only in a signed contract.

Metrics of interest

Everyday activity, sleep and heart rate are the baseline. Overnight and recovery signals — which change noticeably through pregnancy — are welcome in addition, where your device supports them. Tell us exactly what yours provides, and how each value is produced.

Proprietary scores — readiness, stress, “body age” — and regulated features such as ECG, blood pressure or blood glucose do not rule a device out. They must be possible to switch off, and we will not use them. The everyday measurements underneath are what matter to us.

  • StepsEveryday
  • DistanceEveryday
  • Active minutesEveryday
  • Active energy (calories)Everyday
  • Sleep durationEveryday
  • Heart rateEveryday
  • Sleep stagesIn addition, if supported
  • Sleep timing and awakeningsIn addition, if supported
  • Resting heart rateIn addition, if supported
  • HRVIn addition, if supported
  • Respiratory rateIn addition, if supported
  • Blood oxygen (SpO₂)In addition, if supported
  • Skin temperature (nightly)In addition, if supported

Data tiers

For each metric, tell us which of these you can give us. Tier A is the most useful to us; daily summaries alone are the least.

  1. Raw sensor signals — PPG, accelerometer, temperature — at their native sampling rate
  2. Per-minute intermediate values
  3. Daily summaries only

Vendor intake

Tell us about your device

Around ten minutes. Only the three fields marked * are required — answer what you can, and we will follow up on the rest.

Company
Do you own the factory, or are you a trading company? optional
Preferred language optional

Saharvi’s management and technology team will be in Guangzhou and Shenzhen from 1 to 6 November 2026. If you would like to meet them, say so in the form.

Would you like to meet in person, 1–6 November 2026? optional
Product
Form factor optional

Select all that apply.

Current product status optional
For a wristband: can the sensor pod come out of the strap and be worn in a clip or an innerwear holder? optional

For example “MAX30208, 0.1 °C”. Leave blank if the device has no skin-contact temperature sensor.

What are your cycle features based on? optional
Technical
Can the device work with our own consumer app, without your separate consumer app? optional
Integration methods available optional

Select all that apply.

Supported metrics optional

Tick each metric your device provides, and choose the tier you can give us: A raw signals, B per-minute values, C daily summaries.

Can raw sensor signals (PPG, accelerometer, temperature) be read at their native sampling rate? optional

For example: heart rate measured by PPG; sleep stages estimated by an algorithm; “readiness” is a proprietary score.

Can proprietary scores and regulated features (ECG, blood pressure, glucose) be switched off? optional
Does the device work fully with no vendor account and no internet connection? optional
Can firmware updates (OTA) be run from our app, through your update library? optional
Is your cloud service mandatory? optional
Can data be exported if the commercial relationship ends? optional
Can you provide a working sample and documentation? optional
Can you share an SDK overview and data-field list before any sample purchase? optional
Can you send a sample data file — one night of raw data? optional

We will tell you where to send it. Please do not attach it here.

Commercial
Currency for prices optional
Unit prices, FOB Shenzhen optional

Per unit, in the currency chosen above. Leave blank any quantity you do not quote.

QuantityStandard productBranded
100
500
1,000
5,000
Certifications held for this product optional

Select all that apply. In India, Bluetooth devices need a WPC ETA; BIS registration applies to some wearables, such as smart watches.

For example ISO 13485, test reports from SGS or TÜV, or certifications you could obtain for India.

This form collects business information only. Please do not include personal health information.