Skip to main content
Pylon’s wire format is plain HTTP + WebSocket + JSON. You can talk to it with fetch and a WebSocket from any language. But Pylon ships first-party SDKs that handle the bookkeeping — auth tokens, optimistic mutations, reconnection, CRDT decoding, typed entities — so you don’t reinvent them.

Available SDKs

Picking the right combination

The SDKs share the same wire formats; you can use @pylonsync/react on the web, the Swift SDK on iOS, and @pylonsync/react-native on Android — they all agree about what a ChangeEvent looks like, and CRDT bytes are identical across platforms because they wrap the same Loro Rust core.

Common quickstart

Every SDK shares the same shape. The TypeScript flow:
The Swift flow (mirror image):

Codegen

Every SDK supports typed access via pylon codegen:
Generated files emit:
  • Entity types — Codable structs (Swift), interface declarations (TS) per entity
  • Function signatures — typed args and results
  • Typed client extensionsclient.listTodos(), client.createTodo(NewTodo(...)) instead of stringly-typed APIs
Run codegen on every manifest change. Add it to your build script.

Wire compatibility guarantees

Pylon treats wire format as a stability contract — never break it without a major version bump. The SDKs evolve independently of the binary; a v0.2.x client works against a v0.3.x server within the same minor.

Where to next

Pick your platform and dive in: TypeScript, React, React Native, Next.js, Swift, sync engine, or Loro CRDTs.