Get startedPlatform SDK overview

Platform SDK overview

Build independent applications with application-owned data, authority, and peer communication.

Build an independent application with your own data model and authority policy. Platform provides local storage, replication, events, live streams, and peer communication.

Choose the data path

RequirementMechanismCompletion means
Retain a report or latest saved observationSchema-backed record or documentA local commit, followed independently by replication
Announce a bounded factEventLocal acceptance, with a separate delivery outcome
Receive continuing producer samplesLive streamAn authorized, consumer-owned subscription
Exchange protocol-specific bytesManaged transport or messagingThe selected protocol's delivery result
Derive allowed state transitionsWorkflowA validated transition and derived state

A local UI notification does not confirm remote event delivery. A stream descriptor describes a stream but does not open a subscription. A schema defines data but does not create storage or a transport.

Choose a primitive

TopicModel
EntitiesTrack, Geo, Asset, and Template values, including relationships and derived quantities
GroupsProof-carrying membership with offline conflict resolution
SchemasField definitions, validation, and merge semantics
DocumentsSchema-bound structured fields and lifecycle
BlobsContent-addressed binary references
EventsBounded notification envelopes and delivery outcomes
StreamsProducer descriptors and continuing samples
WorkflowsTransition definitions and derived state

The Entity primitive is distinct from a generic record's EntityRef. Records belong to the storage interface.

Principal belongs to Identity. Capability delegation belongs to Authorization. Their Principal and Authorization references remain separate from the eight primitive topics above.

Keep application ownership explicit

You choose record types, schema versions, replication scopes, capability commands, trusted roots, and external adapters. A replication scope names the data peers exchange. A capability authorizes an action on that data. Matching scope names do not grant access.

Two independent peers can exchange your records directly. You can run an always-on peer for availability without changing the application's data model or authority.

Platform also provides identity and authorization, messaging, and logging. Read those concepts as your task needs them.

Select a reference

Language references describe exact declarations and target constraints. Use Rust for custom composition, Python for native integrations, Kotlin, Swift, browser TypeScript, or Dart.

Read compatibility before pairing packages, changing schemas, or deploying mixed peer versions.