Your Saturday game, analysed by Sunday lunch.
Set it on the touchline and let it watch the whole match. Then ask it questions the way you would ask an analyst, instead of watching the game twice.
The answer lands wherever you already are.
The EOT-1 speaks MCP and REST, so your agent can put what it sees into anything with an API. That is the difference between a camera you check and a camera that tells you.
Other things to ask it.
- ❯Count how many times we pressed in the first ten minutes.
- ❯Tell me which of our players never got into the box.
- ❯Clip every corner we defended and tell me what went wrong.
Common questions
Is 60fps enough to follow a match?
For shape, positioning, who went where and what kept happening, comfortably. That is most of what analysis actually is. For freezing the moment of a strike you want a higher frame rate, and we build those units to order.
We film children. What about safeguarding?
A fair question and one you have to answer whatever camera you buy. Filming children at a club or school needs consent and a policy, and that duty is yours, not the manufacturer of the camera. What local-first gives you is a much easier position to defend: footage stays on your own network, you control exactly what gets sent for analysis, and with a local model nothing leaves the building at all.
Do we need more than one camera?
One on the halfway line gets you most of it. Each unit announces itself on the network at its own address, so if you want a second angle behind the goal, a single script can pull from both. How they coordinate is your code, not our firmware.
Batch 001 is in stock and shipping now.
100 Founder Edition units. Ships worldwide. One-time payment, no subscription required, 30-day returns.