SDK Hub

Choose the Persistly path for your game engine.

Start with Available SDKs for JavaScript, Unity, and Godot. Planned tracks show where additional examples and integrations may follow.

JavaScriptUnityGodotadapters next

Start JavaScript Copy a template

Template Center

Copy the smallest starter that matches your save shape.

The SDK pages explain concepts. Templates give you a service wrapper and usage file you can adapt before building custom flows.

JavaScript

Browser and web-game templates

One-save, multi-slot, and account + slots starters for @persistlyapp/sdk.

Open JavaScript templates

Unity

C# service templates

MonoBehaviour-friendly starters for one-save games, manual slots, and cross-device account restore.

Open Unity templates

Godot

GDScript service templates

Autoload-friendly starters for one-save games, named slots, and account/session restore.

Open Godot templates

Integration Rule

One core contract, many game surfaces.

The SDK ecosystem should grow through wrappers and plugins around the same runtime behavior, not separate clients that drift.

Start with PersistlyGameSaves unless you intentionally need the lower-level runtime API.

JavaScript-based integrations should wrap @persistlyapp/sdk instead of copying runtime, error, autosave, or conflict logic.

Available means the SDK is part of the launch documentation path. Planned means it is not shipped yet.

SDK Catalog

Available SDKs

SDK paths for the game surfaces supported in this release.

JavaScriptAvailable

For browser games, Vite apps, JavaScript clients, and future JS-based wrappers using @persistlyapp/sdk.

Open docs

UnityAvailable

For Unity games using the engine package, PersistlyGameSaves, local-first autosave, and Last Beacon examples.

Open docs

GodotAvailable

For Godot games using the addon, PersistlyGameSaves, local-first autosave, and Last Beacon examples.

Open docs

SDK Catalog

Additional JavaScript examples

Planned examples that will use the core JavaScript SDK without forking the runtime client.

BrowserPlanned

Plain browser usage with localStorage and simple game saves.

Open docs

VitePlanned

Vite web-game setup using @persistlyapp/sdk as the dependency.

Open docs

PhaserPlanned

Phaser examples first, adapter package later only if engine-specific lifecycle helpers justify it.

Open docs

PlayCanvasPlanned

PlayCanvas examples first, adapter package later if editor/component integration needs it.

Open docs

SDK Catalog

Additional plugin tracks

Planned engine ecosystems that are not part of the current launch SDK set.

Cocos CreatorPlanned

Thin TypeScript wrapper package around @persistlyapp/sdk.

Tracked roadmap item

ConstructPlanned

Real Construct addon with actions, conditions, expressions, and bundled/core SDK dependency.

Tracked roadmap item

RPG MakerPlanned

Plugin file and commands that wrap the core JavaScript SDK behavior.

Tracked roadmap item

SDK Catalog

Future SDK tracks

Native and tooling integrations are planned after the current SDKs reach stable parity.

Native mobilePlanned

Native mobile SDK tracks are planned after available SDKs reach stable parity.

Tracked roadmap item

UnrealPlanned

Future engine SDK track for Unreal projects.

Tracked roadmap item

Python toolingPlanned

Future tooling/server-side helper SDK, not a primary game-client SDK.

Tracked roadmap item

References

Use these references when wiring an SDK or checking the runtime contract.

JavaScript Package

@persistlyapp/sdk

The intended public package name for the JavaScript/TypeScript core SDK.

Open npm package

OpenAPI

Runtime contract JSON

Machine-readable runtime API contract for direct HTTP integrations and SDK validation.

Open openapi.json

API Examples

Exact request and response shapes

Use these pages when you need the advanced lower-level API contract.

Open API examples