Tensor Dynamics Watch
Guide & support
Choose your path

Start today, without replacing your cameras.

Validate a task on your own dashboard with Browser Watch. Move to the desktop app or an integrated service when you need persistent operation, direct streams, or a wider workflow.

Use now

Browser Watch

No install: share a dashboard and run Qwen 0.8B locally in the browser. Best for validating your own feed and task first.

Start in browser
Persistent watch

Watch Pro App

Move to the desktop app when you need RTSP, more cameras, background operation, and longer monitoring sessions.

Explore the desktop app
System integration

Watch Service

For existing-system APIs, private deployment, or multi-site workflows, scope the integration with our team.

Discuss integration
Browser setup

Your first watch in four steps

Step 1

Open your existing camera dashboard

Open the multi-camera view in TP-Link, Xiaomi, your NVR, or the camera app you already use.

Step 2

Share that window

In Browser Watch, select “Share camera dashboard” and choose that window. No RTSP password is needed.

Step 3

Align each camera region

Use the 2×2 preset for a standard grid, or open Regions and drag the CAM 01–04 boundaries.

Step 4

Choose what each camera should watch

Choose a fall, intrusion, or doorway task, or describe a focused rule in plain language.

Product path

Prove it in the browser, then move up when the work demands it.

Browser Watch

Prove the feed first

Test regions, tasks, and finding quality on the dashboard you already have—without replacing cameras.

Watch Pro App

Move up when monitoring becomes persistent

Choose the desktop app when background throttling, RTSP, camera count, or all-day reliability becomes important.

Watch Service

Integrate when the workflow expands

Connect findings to existing systems, private environments, and multi-site access after a deployment review.

Production plan details will follow released capabilities and the actual deployment scope.

Phone response

Respond on the phone; keep monitoring on the computer.

  1. Sign in to Browser Watch on the monitoring computer.
  2. Opt in to suspicious and critical event-summary sync.
  3. Open the response page with the same account and allow notifications.
Open the response page
Privacy boundary

Local mode keeps the shared video on the monitoring computer.

Local browser monitoring does not upload the shared video, cropped frames, or camera passwords.

Optional phone sync handles event-summary data, not the continuous camera feed.

Review the data boundary before enabling a gateway or external integration.

Browser Watch may be throttled in the background; use Watch Pro when reliable long-running operation is required.
Helpdesk decision tree

Where are you stuck?

Start with the symptom and take the next step without reading the full manual.

The shared screen is blank+

Share again and select the camera app or camera tab—not the Watch tab itself. If the source stops updating when minimized, keep its window open.

The camera regions are misaligned+

Open Regions, select the CAM number, and redraw it over the source preview. Use the 2×2 preset to reset a standard grid.

The model download is slow+

Qwen 0.8B downloads about 0.85 GB the first time. Keep the page open on a stable connection; later sessions load it from the browser cache.

The local model will not start+

Use a current Chrome or Edge browser with WebGPU available and close memory-heavy tabs. On an 8 GB Mac, start with 0.8B; reserve 2B for devices with more memory.

Monitoring slows or stops in the background+

Browsers can throttle background tabs. Keep Watch visible, leave screen sharing active, and prevent the computer from sleeping. Use Watch Pro when reliable background operation is required.

Events are not reaching the phone+

Phone event summaries are optional. Confirm both devices use the same account, summary sync is enabled on the computer, and browser notifications are allowed on the phone.