Cross-platform client
Flutter handles identity, upload, live job state, reports, and deletion across mobile and web.
Built for accountable production
AceSense analyses uploaded tennis footage for shot events, court-relative patterns, pose-derived observations, heatmaps, and frame-linked review on iOS, Android, and web.
Repository-backed product facts · reviewed 26 August 2026
Use the original video as evidence, preserve confidence and unavailable markers, and choose one coaching priority rather than treating a score as medical or officiating truth.
Flutter handles identity, upload, live job state, reports, and deletion across mobile and web.
Firebase owns owner-scoped upload authorization, queue state, billing, dispatch, completion, and deletion.
Disposable GPU workers run a staged vision pipeline and publish immutable generation-scoped artifacts.
Expand the matrix. Choose by boundary and workflow, not slogans.
| This system | Alternative · SwingVision | |
|---|---|---|
| Primary job | Post-session shot, movement, pose, and frame-linked review | Tennis video analysis with prominent live and Apple-device workflows |
| Deployment boundary | iOS, Android, and web client with asynchronous GPU inference | Verify current supported devices and processing model |
| Evidence model | Confidence-aware events linked back to source frames | Match statistics and video review; verify export methodology |
| Operator control | Owner-scoped jobs, immutable artifacts, explicit deletion | Consumer application workflow and account controls |
| Integration surface | Mobile/web app, REST v1, and MCP | Mobile app and current vendor integrations |
Free
Three analyses per month with the complete report surface.
Pro
Higher analysis limits for an individual player.
Team
Pro features for up to ten players and coach workflows.
Current status. The analysis pipeline and public API are production surfaces; Stripe remains in test mode and ordinary monocular video is not an official line-calling or medical measurement system.
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.