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.
Cloud mode (the SDK side) — shipped
Section titled “Cloud mode (the SDK side) — shipped”Configure the SDK with a single project key and the server owns the rest:
- One-line setup —
BeekonConfig.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 metering —
setUserId(...)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.
Build on self-managed today
Section titled “Build on self-managed today”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.
Get started Install, configure, and start tracking — one page, all platforms.
Sync & your backend The upload payload and a working ingest endpoint.
Early access
Section titled “Early access”Want to hear when the Beekon Cloud platform opens? Reach out via getbeekon.com.