Overview
t:β€” Environment: 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
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
UI-only in the Lab. Backend verify can be added later.
Nothing yet.
Flow Explain
Concise
  1. SaaS decides
    Generates refId and stores job state.
  2. SaaS β†’ CLDP
    Calls CLDP HTTP using API Key (server-to-server).
  3. CLDP coordinates
    Validates key, checks online presence, signals Gateway/Client.
  4. Client executes
    Client queries SaaS directly, performs the real local action.
  5. 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.