Capture
Sensor modules generate candidate body or environment data.
Developers
Data access should be a feature, not an afterthought.
OpenPulse is open-source-inspired: transparent data flows, controllable exports and APIs designed for teams building their own apps, dashboards or experiments.
openpulse-sdk
Puck
Core
API
Partner app
const stream = await openpulse.connect({
device: "pilot-band-01",
modules: ["skin.puck.1", "environment.puck"],
});
stream.pipe({
sampleRate: partnerDefined,
ownership: "customer-controlled",
destination: partnerSystem,
});Data flow
From puck signal to partner workflow.
The developer story should make the data path visible. OpenPulse is not claiming finished SDKs yet; this is the integration direction the platform is being built around.
Transport
The base board handles firmware, power, wireless and module routing.
Normalize
Data becomes structured enough for export, dashboards or partner APIs.
Integrate
The customer decides where the data goes and how it is used.
/devices
/modules
/streams
/exports
Live stream mock
modulesignalqualitydestination
skin.puck.1candidate_biosignalpilotpartner.app
skin.puck.2temperature_pathpilotresearch.csv
environment.puckcontext_signalplannedworkflow.api
Schema shape
timestamp
module_id
sample_value
quality_state
owner_scope
Code examples
Readable by product teams, useful for engineers.
await openpulse.device("pilot-01")
.modules(["skin.puck.1", "skin.puck.2"])
.authorize(partnerToken);{
"module": "skin.puck.1",
"signal": "candidate_biosignal",
"timestamp": 1780147200000,
"quality": "pilot"
}stream.on("sample", sample => {
partner.dashboard.write(sample);
partner.archive.append(sample);
});Developer principles
Open enough to build with. Careful enough for sensitive data.
Transparent capturePartners should understand what is captured, how it is processed and where it is sent.
No unnecessary lock-inThe long-term direction is export and integration, not forcing every use case into one consumer app.
Structured dataCandidate APIs should make module identity, timestamps and quality states explicit.
Developer kit pathDeveloper access remains a secondary direction for technical users, research and experimentation.
Developer waitlist
Want deeper access when the hardware is ready?
Join the technical interest list for API concepts, hardware updates and developer kit availability.