Adaptor Onboarding

This is the recommended path for a new adaptor — an organisation deploying Blue Dots for a district, state or domain. It assumes you have read Blue Dots as a DPG.

The path at a glance

1

Stand up Signals

Start with the network-aware backend — get the Signals API and UI running against local Postgres + Redis.

2

Define network + domains

Decide the network you participate in and the domains your instance serves, expressed as schemas and SERVED_DOMAINS config.

3

Add Aggregator

Add the Aggregator DPG to onboard partner organisations at scale, writing participant signals through the bulk-create paths.

4

Add capture channels

Web — the schema-driven Signals UI and the Aggregator portal — plus Voice AI for low-cost, local-language signal capture.

5

Integrate notifications

Wire SMTP (email) and an SMS provider for OTP, confirmations and match notifications.

6

Pilot & measure

Run a bounded pilot in one district and track the before/after metrics that matter.

Step 1 — Stand up Signals

Start with the network-aware backend. Follow Signals DPG Setup. At the end you should have the Signals API and UI running against local Postgres + Redis.

Step 2 — Define your network and domains

Decide the network you participate in (e.g. blue_dot) and the domains your instance serves (e.g. student, employer). Because the model is schema-driven, you express these as schemas and SERVED_DOMAINS config, not code. Define your item types (e.g. profile_1.0) up front.

Step 3 — Add the Aggregator DPG

When you are ready to onboard partner organisations at scale, add the Aggregator DPG. Configure it to write participant signals into your Signals instance through the bulk-create paths, authenticating with the two-header service-auth model:

x-api-key: <your aggregator's API key>
x-acting-org-id: <the organisation you act as>

Step 4 — Add capture channels

• Web — the schema-driven Signals UI and the Aggregator portal.
• Voice AI — for low-cost, local-language signal capture. A voice DPG integrates the same way an aggregator does (service-auth + bulk create).

Step 5 — Integrate notifications

Wire SMTP (email) and an SMS provider for OTP, confirmations and match notifications. Mailpit covers email locally.

Step 6 — Pilot and measure

Run a bounded pilot in one district (as Ghaziabad and Dharwad did) and track the before/after metrics that matter: jobs surfaced, discovery time, cost per interaction, and conversion. See Pilots.

Onboarding checklist

• Signals API + UI running, migrations applied.
• Network schema and SERVED_DOMAINS defined; item types registered.
• Aggregator DPG deployed; Keycloak protocol mappers added.
• Service-auth API key issued and acting-org configured.
• SMTP + SMS providers connected.
• S3 bucket + credentials provisioned for bulk upload.
• Pilot scope and impact metrics agreed.