AI in your flows In pilot

Ask the AI what the camera sees.

A node sends the snapshot, or the flow’s data, to a model with a question in plain language. The automation continues according to the answer: yes or no, a category, a number or a short text.

Demo footage
Recording of the panel: the "AI providers" screen with this month’s usage, the permission to send images out and the providers (Tero local, OpenAI, Anthropic, Alibaba Qwen, DeepSeek and OpenAI-compatible); then, in the "Classify what the camera sees" template, Anthropic (Claude) is picked in the node and a notice says the snapshots go to that provider. Recorded in the TeroVision panel, with simulated cameras on a demo database. The panel is in Spanish.

You pick the model

Tero local runs on our server and never leaves the platform. The others belong to other companies and use your space’s key, stored encrypted and never shown again.

  • Tero localAn open vision model on our GPU server. Snapshots never leave TeroVision.
  • OpenAISnapshots and data, with your key.
  • Anthropic (Claude)Snapshots and data, with your key.
  • Alibaba QwenSnapshots and data, with your key.
  • DeepSeekData only, no snapshots, with your key.
  • OpenAI-compatibleYour own service over https, at a public address.

External providers need a key from your own account with them. The cost of those calls is between you and the provider. In pilot

Answers a flow understands

The model must answer in a strict format. If it answers anything else, the flow continues through "Error".

  • Yes or no

    Are more than five people queuing at the till?

    • Yes
    • No
    • Error
  • A category

    What is in the foreground?

    • person
    • vehicle
    • animal
    • nothing
    • Other
    • Error
  • A number

    How many tables are taken? (0 to 30)

    • Answer
    • Error
  • A short text

    Summarize what the camera counted today.

    • Answer
    • Error

In pilot

Private by default

  • External images, off

    Sending images to an external provider stays off until an administrator enables it for the space. Every node that does it says so: "Snapshots go to …".

  • Every image, audited

    Who, when, to which provider and from which automation. Never the image itself.

  • Nothing in the logs

    No images or keys in the history, errors or queue. The snapshot is shrunk to 1280 px and lives only for the duration of the request.

  • The answer is data

    What the model replies is validated and shown as text. It is never used as a command, an address or code.

  • Usage caps

    Calls and tokens per month and per space, calls per minute per automation, and a maximum time per request.

In pilot

To get started

  • Has someone fallen?

    Every 5 minutes, a snapshot and a yes-or-no question. If yes, it calls and alerts with the reason.

  • Classify what the camera sees

    On motion: person, vehicle, animal or nothing, and a path for each.

  • Daily summary

    What the counting recorded, in one paragraph by email. Data only, no snapshots.

Shall we try it with your cameras?

We show you the panel running and build the first automations for your place together. Whatever is in pilot gets tested with you before we promise it.