Skip to content

Beekon Cloud

Beekon has two halves: the SDK’s cloud mode — shipped, fully specified, and documented across these pages — and the Beekon Cloud platform (console, signup, dashboards, billing), which is being built now and is not yet open.

Configure the SDK with a single project key and the server owns the rest:

  • One-line setupBeekonConfig.cloud(projectKey: "bkproj_<cell>_…"). The key names your project’s home region (cell); the SDK derives its endpoints from it with zero network calls. See Configuration.
  • Server-owned config — tracking knobs live in a remote config document, cached on-device, applied fresh > cache > defaults. Every remote value passes a device-enforced clamp table: no server value can push a device outside safe battery ranges or redirect uploads. Tracking never blocks on configuration.
  • Server-owned geofences — authored centrally, delivered per-device as a proximity slice on the sync response; circles and polygons; offline killed-state crossing notifications included. See Geofencing.
  • Device control plane — config acks, health snapshots, and remote commands (flush, diagnostic-log pull) ride the same sync exchange.
  • MTU meteringsetUserId(...) binds identity to fixes at record time; anonymous devices meter by install id.

The wire contracts are open specifications in the spec/ directory — cloud mode is the same open client as every other mode.

You don’t need Beekon Cloud to ship. Point the SDK at your own backend (or stay fully on-device) and you have retrying batched uploads, background tracking, and geofencing — no managed service required.

Want to hear when the Beekon Cloud platform opens? Reach out via getbeekon.com.