Frequently asked questions

It is a Windows desktop application (with companion support where the line ships it) for local-first analysis of images, video, audio and metadata. It produces structured, open .vtag sidecar files so you can make archives more searchable and connect to tools like catalog software.

The design centre is analysis on your own machines where your build is installed. Platform support is expanding—treat the current product sheet as the source of truth for which OS and companion apps apply to your license.

In the local-first workflow, your source files are processed where you run the suite, and results can be written as sidecar metadata on disk. Any optional online feature (licence checks, model downloads, crash reporting) is version-specific: read the privacy section of your build’s documentation; we do not promise a zero-network binary on this marketing site.

A .vtag is an open sidecar file—usually JSON—saved next to a media file. It contains structured AI output (tags, text, time ranges, model provenance) so that other programs can index and search without a proprietary database. See the .vtag page for detail.

The product targets image, video, and audio with associated metadata paths your build supports. Exact codecs, containers, and file-size limits change between releases; start from the trial on your own samples for a definitive answer for your material.

VisionaryAI Suite is designed to complement NeoFinder workflows by producing structured AI metadata that can be indexed and reused, within the limits of your NeoFinder version and configuration. See NeoFinder workflow and your official product documentation for the step-by-step that applies to your build.

The architecture is aimed at serious collections, but throughput and limits always depend on your storage speed, GPU/CPU, model choices and batch settings. We avoid stating a number here that could be wrong the moment hardware changes. The trial and a pilot are the right next steps to measure your case.

The suite is built to swap and combine model components over time, so a static list in marketing would go stale. Your build’s about or credits window, and release documentation, are the right place to see the exact engines and versions in your installer.

You should assume some network use is possible (for example activation or updates) unless a specific build is documented as offline-capable. Core analysis of files on disk is designed to run without your media being uploaded to our servers as a default workflow—but confirm your contract and the exact product version’s privacy statement for a binding answer.

Both. Individuals and small teams can start with a trial; universities, broadcasters, agencies and public-sector archives are natural fits when scale, compliance, and multi-seat licensing enter the picture. Pricing is structured to grow with that reality.

Open the Download page for system requirements (Windows, NVIDIA recommended), storage expectations, and the ZIP link. If a host URL changes, contact us and we can send a current link.

Use the contact form or email info@bomarkanalys.se. The web form is a static placeholder until you connect a backend (see the TODO comments on the contact page).