Racket perception pipeline
A staged perception pipeline detects court, players, ball, contacts, bounces, and rally structure.
Built for accountable production
UNFORCE turns racket-match video into tactical sequences, rally patterns, shot context, and coaching debriefs that stay linked to the original frame evidence.
Repository-backed product facts · reviewed 26 August 2026
Move from a match-wide pattern to the exact rally and frame, add human tactical context, and leave with a small number of reviewable priorities.
A staged perception pipeline detects court, players, ball, contacts, bounces, and rally structure.
A frame-addressable event graph links tactical statements back to source moments and confidence.
The debrief layer groups repeatable patterns and preserves coach annotation rather than replacing it.
Expand the matrix. Choose by boundary and workflow, not slogans.
| This system | Alternative · SwingVision | |
|---|---|---|
| Primary job | Post-match tactical debrief with source-frame traceability | Tennis video analysis with prominent live and Apple-device workflows |
| Deployment boundary | iOS, Android, and web workflow with asynchronous inference | Verify current supported devices and processing model |
| Evidence model | Every tactical statement links to rally, event, and frame evidence | Video and match statistics; verify current export granularity |
| Operator control | Coach/player annotation remains authoritative context | Consumer analysis workflow and current coaching features |
| Integration surface | Mobile/web report, sharing, frame review, API surfaces | Mobile app and current vendor integrations |
Free
Two complete sessions for evaluation.
Pro
Higher session limits and complete tactical reports.
Team
Shared review workflows for players, coaches, and teams.
Current status. Post-match analysis is the boundary; it does not claim live officiating, medical diagnosis, or certainty where the video is unreadable.
Start with the architecture, reproduce the documented workflow, and verify the boundary against your own threat model.
No. Mutable vendor pricing is deliberately excluded. Verify current vendor terms before a purchase decision.
The status note, architecture page, and engineering articles state the current boundary and failure behaviour.