Nutrition-first
You have users and a product, and you need meal planning, logging and analysis. Start with ONE alone and add wearable context later, or never.
Integrations
Nutrition first. Wearable context only if you want it.
ONE has no dependency on wearable data. Everything the engine does works from a profile your product already holds. Wearables add context; they are not a prerequisite.
How the pieces fit
One required component. Two optional ones.
This is the whole topology. There is no bundle you have to buy into and no hidden dependency between the products.
Your product
One brand, one user experience, one customer relationship
ONE by OSCA
Personalised nutrition engine
Profiles → plans → logging → analysis
Required
WearSightful
Health and wearable data platform
Activity · sleep · recovery signals
Optional
Your existing aggregator
Whatever you already run
Mapped into the profile on a bespoke basis
Optional
Only the first column is required. Nothing in the nutrition engine depends on a wearable being connected.
Entry points
Start where the gap in your product actually is.
Most teams arrive with one of these three shapes. All of them are supported as a first contract.
Wearable-first
You already run WearSightful for health and activity data and now want nutrition on top of the same user context.
Both, under your brand
Activity and sleep from WearSightful inform the nutrition profile in ONE, and your product presents a single joined-up experience.
WearSightful
Two platforms, one sentence each.
WearSightful helps platforms understand the person. ONE helps platforms personalise what they eat.
ONE by OSCA
Personalised Nutrition Engine
Requirements, allergens, meal plans, food logging, deficiency analysis, substitutions and preference learning.
WearSightful
Health & Wearable Data Platform
Wearable connections, ingestion and normalisation, trends, insights and engagement on top of health data.
Bespoke aggregators
Keep the vendor you already have.
Plenty of teams have already standardised on a wearable or health data stack. That is not a reason to change it, and it is not a reason to lose nutrition personalisation.
01
Scoped to what matters
Nutrition only needs a few signals — activity load, sleep quality, recovery proxies. We map those rather than every field your aggregator emits.
02
You keep the contract
Your existing vendor relationship stays yours. We integrate against it; we do not ask you to replace it.
03
Still optional
If the integration is delayed or dropped, the nutrition engine carries on working from the profile alone.
Design the integration path that matches your roadmap.
Whether you start with ONE alone, pair it with WearSightful, or need your existing aggregator mapped in — we will help you pick the lowest-friction entry point.
Product teams book a demo · Engineering teams explore the API and SDKs