T
Taquora Flow
Download Taquora Flow

Install locally. Keep speech workflows under your control.

Choose the installer for the workstation, download the model to the computer, and use browser sign-in only for device-aware desktop access. Taquora Flow is built for healthcare teams that want a clearer local story from the first install.

Download macOS DMG
Windows installer uploading
Local deployment story

Download the model to the computer. Keep the workflow on the device.

Taquora Flow is designed for healthcare teams that want browser-based access control without pushing raw speech through a browser app. Install locally, authenticate once, and run on the workstation you control.

Device-bound access
Browser sign-in activates the desktop app on the same workstation and gives users a visible device ID in their account.
HIPAA-sensitive posture
Protected health information can stay on systems your organization controls. Compliance still depends on your safeguards, policies, and deployment choices.
macOS
.dmg

Apple Silicon DMG

Installer for macOS deployments. Download the desktop app, complete browser sign-in, and prepare the local model on the same workstation.

Download installer
Windows
pending

Windows installer publishing next

The macOS installer is live now. Publish the Taquora Windows installer and this card can switch back to a direct download immediately.

Delivery architecture

A cleaner install story for healthcare deployment.

The download experience should feel like part of the product, not a file handoff. Users get a direct installer, a clear next step, and a local-first explanation of how Taquora Flow works on the workstation.

Installer access
Same-domain download from Taquora

Users stay on voice.taquora.com while downloading the installer, which makes the flow cleaner for enterprise rollout and support.

Device setup
Browser auth returns to the same workstation

The browser completes sign-in, then hands access back to the desktop app so the machine can be activated and listed in the account.

Local execution
Prepare the model on the computer that will run dictation

The product story stays consistent: installer, auth, model preparation, and then a native desktop workflow close to the user.

Visual handoff

Install. Sign in. Run locally.

Desktop packagedirect
Auth
Browser session returns to the same device.
Runtime
Model prepared on the workstation.
Device ID visibility, installer delivery, and local execution all live inside one coherent flow.
After download
Step 01

Install the desktop app

Use the correct installer for the machine that will run dictation and local speech processing.

Step 02

Authenticate in the browser

The app opens `voice.taquora.com`, the user signs in, and the browser returns access to the same device over localhost.

Step 03

Download and run the model locally

Prepare the speech model on the workstation so the actual runtime stays on the computer instead of inside a browser session.

Why this setup

A cleaner deployment story for regulated healthcare environments.

Taquora Flow is positioned around local execution and browser-based access control. The product story is simple: install on the machine, keep the speech path local, and manage access centrally.

Local model ownership

Downloaded models live on the workstation, which gives teams a more credible story around data control and operational ownership.

Device-aware access

Users can see which device ID is connected in the browser account and control who can activate the desktop experience.

HIPAA-sensitive messaging

The website can say the right thing: protected health information can stay on infrastructure you control, while formal compliance still depends on your organization’s safeguards and policies.