Skip to main content

What is Synheart Core SDK?

Synheart Core SDK is the unified integration point for developers who want to collect multimodal signals, process human state on-device via the Synheart runtime (native), and upload derived state snapshots (HSI 1.3 format) to the cloud with explicit user consent.
Not sure whether you need Core or just one of the standalone SDKs (synheart_wear, synheart_behavior, synheart_session)? Start with How it fits together — a one-page mental model of the stack with a mandatory-vs-optional table.

Key Features

Unified API

  • Single SDK: One integration point for all Synheart features
  • Modular Design: Enable only the modules you need
  • Consistent Interface: Same API patterns across all platforms
  • Multi-Module Support: Wear, Phone, Behavior, HSI Runtime, Consent, Cloud

On-Device Processing

  • HSI Runtime: Powered by the Synheart runtime (native) — on-device human state fusion
  • Privacy-First: All processing happens on-device
  • Designed for low overhead: targets sub-100ms HSI emission and a single-digit-percent CPU budget on a typical mid-range device
The numbers above are design targets, not measurements — actual footprint varies by device class and workload. Profile your app and read Synheart.runtimeDiagnostics() for live counters.

Multi-Platform Support

Capability System

Access levels tied to app signature and tenant ID: By default, third-party apps run under Core capabilities. Extended and Research capabilities are enabled only for first‑party Synheart apps and approved partners, since they may unlock higher-sensitivity data access and require additional privacy/security review and contractual controls.

Module System

The Core SDK consolidates all Synheart signal channels:

Quick Start

Flutter/Dart

Flutter SDK Guide

Complete Flutter integration guide
Installation:
Basic Usage:

Android (Kotlin)

Kotlin SDK Guide

Complete Android integration guide
Installation:
Basic Usage:

iOS (Swift)

Swift SDK Guide

Complete iOS integration guide
Installation:
Basic Usage:

Privacy & security

  • Zero raw content: no text, microphone audio, URLs, or messages.
  • On-device processing: HSI inference runs locally on the host.
  • Consent-gated cloud: uploads require an explicit cloudUpload grant from the consent service.
  • Capability-enforced: feature access is bound to the consent token’s capability tier; the SDK silently downgrades responses when the tier is insufficient.

Performance targets

These are internal targets, not measured runtime numbers. Use Synheart.runtimeDiagnostics() and the uploadQueueLength / lastUploadAt getters to inspect what the SDK is doing in your app.

Available SDKs

Flutter SDK

Flutter integration

Kotlin SDK

Android/Kotlin integration

Swift SDK

iOS/Swift integration
Each repo ships a runnable example in its example/ directory: Flutter · Kotlin · Swift.

Stability

Synheart Core is pre-1.0. Minor version bumps may include breaking API changes — pin exact versions (or a tight constraint like 0.0.x) in production, and read the CHANGELOG before upgrading. The HSI wire contract is versioned separately and follows its own policy.

Technical Documentation

Architecture

Module system and HSI Runtime

HSV Specification

The typed inference output of the Synheart Runtime — six heads + 64D JL embedding

Capability System

Access level enforcement

Consent System

Permission model and enforcement

Use cases

Mental health platforms

Subscribe to the typed HSIState stream and read the affect axis to monitor arousal/valence over time:

Productivity apps

The engagement axis tracks interaction stability over the session window:

Research applications

Use a research-tier capability token to collect data with broader fidelity bounds, and activate the cloud connector to upload HSI snapshots:

Next Steps

Quick Start

Get started in 5 minutes

Architecture Guide

Deep dive into the system

HSV Specification

Understand Synheart Core’s internal state model

Flutter SDK on GitHub

View source code