Skip to main content
Notable changes to AcuSight, newest first. AcuSight uses increment-based versioning during development — each increment is a major feature milestone. We’ll move to semantic versioning at general availability.

Increment 4 — In development

  • New documentation site, with an API reference generated directly from the platform’s OpenAPI spec.

Increment 3 — Hosted & multi-tenant

Hosted, multi-tenant platform
  • Run AcuSight as a hosted service, with every organization’s data fully isolated.
  • Sign in with Google, GitHub, or email — new users are routed to the right organization automatically, usually by email domain.
Effortless device onboarding
  • Bring a device online with a single setup command and a single-use token.
  • Devices connect outbound only, so they work behind NAT or a firewall with no open ports or inbound networking.

Increment 2 — MLOps pipeline & fleet management

Data & training
  • Automatic batching of incoming images, in-browser annotation, and versioned datasets with train / validation / test splits.
Fleet & container management
  • Manage each device’s containers, stacks, and logs directly from the dashboard.
Monitoring
  • Fleet and model-health dashboards, with model-drift alerts.

Increment 1 — Foundation

Core platform
  • Projects, device registration, and the web app.
  • Virtual devices for trying the platform end to end without hardware.
Video
  • A live, multi-device video wall and recorded playback on a scrubbable timeline.

Contributing

Found an issue or have a suggestion? Open an issue on GitHub.