Own the data path for medical speech to text.
Download the model to the computer, keep the workflow on the workstation, and use the browser only for sign-in, downloads, and device-aware access. Taquora Flow is positioned for healthcare teams that want a stronger local story from the first click.
Local model delivery with browser-based access control.
Taquora Flow is built around a clear operating model: install locally, authenticate in the browser, activate the desktop app, and keep the speech workflow close to the device.
A clearer story for healthcare and enterprise deployment.
The website explains how the product is installed, authenticated, managed, and rolled out across workstations without hiding the operating model behind vague platform language.
A browser layer that supports the desktop product instead of replacing it.
Download the model to the workstation and keep speech processing close to the user.
Taquora Flow is positioned around local model delivery and desktop execution, so teams can keep voice handling on the computer instead of routing raw speech through a remote browser flow.
Authenticate in the browser, then return to the same device over localhost.
The browser remains the account and control layer, while the desktop app receives the session and keeps the dictation experience native to the machine.
See the device ID that is connected and what desktop sessions are active.
Signed-in users can confirm which workstation is linked to their account before they start using the app or downloading a new installer.
Ship one browser surface for downloads, sign-in, and future license enforcement.
The same website can handle activation, downloads, device listing, and later subscription or license checks without changing the desktop auth contract.
Built around local ownership of models and machine-level workflow.
Download the models to the workstation, keep voice processing close to the user, and use the browser for access control instead of raw speech handling. This is a stronger fit for healthcare teams with HIPAA-sensitive workflows and tighter data ownership requirements.
Own the data path
Voice input, local models, and desktop workflow stay inside infrastructure your organization controls.
Built for HIPAA-sensitive workflows
Downloaded models and workstation execution make it easier to keep protected health information on systems your organization controls.
Ready for controlled rollout
The same web surface can handle installer delivery, device visibility, activation, and future subscription enforcement.
Download locally. Authenticate in browser. Work on the device.
That is the core Taquora Flow model. Clinicians, admins, and hospital buyers can see exactly how the product is installed and operated without guessing where the data path lives.
Start with the correct installer, prepare the local models on the computer, then return to browser auth only when you need access control, device visibility, or future license enforcement.
One story from installer to desktop access.
Download the app for macOS or Windows and prepare the models on the computer that will run the workflow.
The desktop app opens `voice.taquora.com`, the user signs in, and the browser hands a short-lived auth code back to the same machine.
Once activated, the desktop experience stays native: hotkey, recording, dictation, history, and structured output.
Users can come back to the browser surface to see device IDs, active sessions, and the right installer package.
Download the app, install the local models, and activate the desktop flow.
The website delivers the installer, handles sign-in, and shows device-aware access once the app is connected. The speech workflow itself stays on the machine.