Endpoint runtime

Endpoint troubleshooting agents controlled from the browser

Caisey uses enrolled endpoint runtimes to make remote troubleshooting durable. The runtime lives on the device, connects back through Caisey bridge infrastructure, and lets the cloud console coordinate support work.

Persistent enrollment

Instead of starting with a one-time support link for every incident, an organization can enroll devices and return to them when troubleshooting is needed.

Bridge-first connectivity

Endpoint bridge connectivity keeps RPC as the always-on sendability channel. Live runtime events can attach while browser subscribers are active.

Control-plane records

Caisey keeps machine records, session metadata, and conversation history in Cloudflare Worker and Durable Object infrastructure rather than treating the browser as the source of truth.

FAQs

Which endpoint platforms does Caisey support today?

Caisey has installer flows for Windows x64 and Apple Silicon macOS endpoints. Intel macOS and Linux endpoints remain deferred.

Does the endpoint initiate the connection?

Yes. Caisey uses outbound bridge connectivity from enrolled machines back to the control plane.

Can endpoint cleanup be requested from the console?

Yes. Deleting a device requests endpoint cleanup first, then the control plane finalizes deletion after cleanup is reported.