Beekon Cloud (private beta)

Everything else in these docs is self-managed mode: you run the backend (or stay fully on-device). Beekon Cloud is the managed alternative — you point the SDK at a project and the server owns ingest, configuration, and geofences.

Private beta

Beekon Cloud is still being built and tested. These docs cover the self-managed SDK, which is generally available and what you should build on today. If you see cloud in the API (BeekonConfig.cloud, a GeofencesManagedByServer error, the user_id extras key), this page is what it refers to.

What it is

In cloud mode you configure the SDK with a project key (bkproj_…) instead of a sync URL:

BeekonConfig.cloud(projectKey: "bkproj_…")

The SDK then mints its own upload token, fetches tracking configuration from the server, and uploads to managed ingest — no backend for you to build or operate. A console (projects, keys, usage) manages it all.

How it differs from self-managed

	Self-managed (these docs)	Beekon Cloud
Backend	You build and run the ingest endpoint	Managed ingest, nothing to operate
Config	You set the gate locally	Server-owned, fetched and applied remotely
Auth	Your headers / AuthConfig	Project key → SDK-minted tokens
Geofences	You manage them (addGeofences)	Server-managed (the app addGeofences call reports GeofencesManagedByServer)
License	Optional, you supply	Delivered with the server config
Metering	None	Monthly tracked users, by the user_id you set via setExtras

The data on the wire is identical — cloud ingest receives the same upload payload. Cloud just owns the endpoint, the config, and the geofences for you.

Register interest

Want early access? Reach out via getbeekon.com. Until then:

Build on self-managed Install, track, and run your own backend today.