Skip to content

Sources

Where every number comes from - connect a source with a read-only token, check its status, and manage the signed-event secrets apps push with.

Sources: "Where every number comes from: one connector per source, pulled on a schedule, plus the signed events apps push."

Source

From

auth

REM Auth's sign-in counts (rpt_ watch tower token)

blogs

REM Blogs' inbox counts

payments, credits

REM Payments' admin read API (a read-only ptk_ token of a REM Payments platform admin)

telemetry

REM's telemetry engine (a viewer key)

data

The shared data layer's status

rch, vibecoder

REM CloudHub and REM Vibe Coder events

Each source has a mode: demo (sample numbers, badged), live or off, a pull interval (15 seconds to one day, default 60 seconds) and a health address: "Probed on every sync, in every mode; any answer under 500 counts as up."

Connect a source (super admins)

  1. Open the source.

  2. Under Connection, enter the base address ("Where the source's read API lives") and a read-only token made in that app. The watch tower never makes tokens in other apps.

  3. Save. The token is stored encrypted and never shown again. The source turns live; its sample numbers and sample inbox items are deleted.

Sources set by the deployment are marked "Set by the deployment"; a change made here lasts until the next restart.

The Status shows the last sync, its result and the last error (401 or 403 = a bad token; 404 = the app does not serve that data yet).

Signed Events (Webhook)

"Apps push feedback, failure reports, deleted accounts and plan changes to POST /api/events/{app}, signed with HMAC-SHA256." Here a super admin creates or rotates each app's signing secret (shown once). See Signed events.

Last updated 18 Nov 2026

Sources · REM Platforms Blog