CLDP SaaS Lab

Gateway Status

—

Last seen: —

Client Status

—

Last seen: —

Last Event

—

Type

—

refId

—

Time

—

Quick Actions

Lab-only

How it works

SaaS generates refId → calls CLDP (API Key) → CLDP signals Gateway/Client → Client executes and ACKs → SaaS updates UI.

Console preview

Gateway

—

deviceId

—

Last seen

—

Version

—

OS

—

Client

—

clientId

—

Last seen

—

Capabilities

—

Hint

Read-only

This page reflects technical presence (online/offline). It does not imply business success.

Simulations

Choose an action

Payload (Lab)

This payload is only for demo. CLDP should not store business payload.

Results

—

Run an action to see the simulated outcome.

Note

In a real integration, the Client queries the SaaS directly after being signaled by CLDP.

Events / Console

Gateway

Recommended

Download and install the Gateway in the customer environment. It will connect to CLDP via WebSocket.

In the real SaaS, this uses CLDP onboarding/download endpoints.

Sample Client

Lab-only

Download the official Sample Client to validate connectivity and demonstrate the flow.

Pairing / Verify

Stub

Pair code

UI-only in the Lab. Backend verify can be added later.

Nothing yet.

Flow Explain

Concise

SaaS decides

Generates refId and stores job state.
SaaS → CLDP

Calls CLDP HTTP using API Key (server-to-server).
CLDP coordinates

Validates key, checks online presence, signals Gateway/Client.
Client executes

Client queries SaaS directly, performs the real local action.
ACK returns

Client ACKs via CLDP (technical status), SaaS updates UI.

Example payload

About

CLDP SaaS Lab

This is a reference UI that behaves like a developer SaaS, used to demonstrate CLDP integration.

No login. Tenant context comes from the URL. No sensitive data should be used here.

Rules

CLDP coordinates; SaaS decides; Client executes.
This Lab is demo-only and independent from CLDP codebase.
Avoid business payload; keep it technical.