Overview
Usage across every service, for the selected app.
Apps
Every service is scoped to an app — create one per project, then use the app switcher above to work inside it. API keys, devices, geofences, storage, tables, pages, and verifications all belong to exactly one app.
| Name | Created | |
|---|---|---|
| Loading… | ||
API keys
Your backend uses these to register devices and read location data. Scope each key to only what it needs.
| Name | App | Key | Scopes | Status | Last used | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Devices
Trackers, vehicle units, and mobile app instances reporting locations.
| External ID | Name | Status | Last seen | |
|---|---|---|---|---|
| Loading… | ||||
Geofences
A center point and radius. Assign devices to get ENTER/EXIT events as they cross the boundary.
Pages
Publish an account-deletion or privacy-policy page (or any other admin-defined template) with your own logo, app name, and contact email — no HTML to write.
| Slug | Public URL | Updated | |
|---|---|---|---|
| Loading… | |||
Storage
S3-compatible object storage. Buckets are a logical namespace per tenant — upload, download, and delete objects within them.
Database
Define tables for your app to use — your own end users read/write rows directly (secured with Postgres row-level security), no backend of your own required.
| Name | Access | Columns | Created | |
|---|---|---|---|---|
| Loading… | ||||
Verification
Try the phone and email OTP flows your end users go through. In dev mode the code is always 123456 and nothing is actually sent.
Not an OTP — any email your backend wants to send through this service's configured SMTP.