Private preview · infrastructure for WhatsApp products

Own the pairing layer.

Provision, pair and isolate WhatsApp sessions without sending customers through someone else’s dashboard. One API, inside your product.

Request early access View the architecture

Tenant: Scoped
Pairing: Embedded
Events: Webhook-first

Session console Interface preview

Session northstar-support

Awaiting pair

PAIRING WINDOW

Scan inside your app.

The QR belongs in your onboarding flow. PairingDock handles the session state behind it.

Rotates automatically00:42

14:02:11POST/v1/sessions201

14:02:12EVENTqr.ready200

14:02:54WAITsession.paired—

Your interface in front. Session infrastructure behind.

PairingDock is being designed as the operating layer between your application and each WhatsApp session—not as another dashboard your customers must learn.

YOUR PRODUCT Customer onboarding UI · billing · identity

PAIRINGDOCK Session control plane Provision · route · observe

ASessionisolated state

BSessionisolated state

CSessionisolated state

POST /v1/sessions

{
  "client_reference": "northstar-support",
  "region": "eu-west",
  "webhook_url": "https://app.example/events"
}

→ 201 { "status": "awaiting_pair" }

Three calls between signup and connected.

The intended flow is deliberately small. Your customer stays in your interface while PairingDock manages the session lifecycle.

1.0
Create the session.
Send your tenant reference, region and callback destination. Receive a session ID owned by that tenant.
POST /sessions
2.0
Render the pairing state.
Display the rotating QR or connection status directly inside your onboarding experience.
GET /sessions/{id}/pair
3.0
Operate through events.
Receive message and lifecycle events at your webhook. Route them into the workflow you already own.
event: session.ready

Boundaries before scale.

The platform is being shaped around tenant separation, observable delivery and infrastructure choices that can grow with the customer base.

Credentials: Tenant-scoped keys; Keep one customer’s access separate from another.
Session state: Isolated lifecycle; Pair, pause, restart and revoke without crossing tenants.
Event delivery: Webhook-first; Signed callbacks with delivery visibility and retry policy.
Provider layer: Adapter-based; Keep the application contract stable as session engines evolve.
Network path: Region-aware; Infrastructure placement and egress controls can follow risk.

Frontend now. Control plane next.

This is the public product direction. Account creation, login, billing, session provisioning and the live API will arrive as the functional platform is built.

Available nowProduct preview
NextPrivate tenant accounts
ThenSession API and webhooks

Build the first integration with us.

PairingDock is in private development. Leave an address to prepare for early access—the preview does not send or store it yet.