IoT and embedded SDK integration

For embedded fleets, provision the SDK once, run it under systemd, and keep per-device identity stable across firmware updates.

1. Install

# Linux x86_64 — install once at provisioning time.
curl -L https://getpassive.io/sdk/binaries/getpassive-sdk-linux-x86_64 \
  -o /usr/local/bin/getpassive-sdk
chmod +x /usr/local/bin/getpassive-sdk

2. Initialize

# /etc/systemd/system/getpassive-sdk.service
[Service]
Environment=GP_DEV_API_KEY=${apiKey}
Environment=GP_DEVICE_UUID=<STABLE_PER_DEVICE_UUID>
ExecStart=/usr/local/bin/getpassive-sdk
Restart=on-failure

[Install]
WantedBy=multi-user.target

3. Binary downloads

4. Lifecycle notes

  • Current Linux x86_64 builds are small enough for typical gateway and appliance images.
  • Store GP_DEVICE_UUID in persistent device storage, not a tmpfs path.
  • Use systemd Restart=on-failure and log to journald for diagnostics.
  • Disable or remove the unit when the user opts out or the device is deprovisioned.

Start the SDK only after your app has shown the required disclosure and the user has accepted it. Use the shared consent guide for the wording and placement expectations.

6. Verify

Use the in-dashboard tester at app.getpassive.io for your app key, or follow the shared quickstart verification steps while the key is in test mode.

Roadmap notes

ARM IoT builds, including aarch64 and armv7, are in pilot. Apply for early access at app.getpassive.io.

Last updated June 14, 2026