Web dashboard
Use the browser-based SaaS dashboard for auth, downloads, files, transcripts, billing overview and privacy flows.
- ✓ No installer
- ✓ Works in modern browsers
- ✓ Connected to API
VATranscribe currently runs as a web dashboard with API-backed media workflows. The download page is prepared for future desktop installers, release notes, checksums and platform-specific builds.
channel:web-dashboard desktop:planned checksums:planned-for-signed-builds release-notes:0.1.0-web The current production path is the web dashboard. Desktop and CLI distribution are prepared as a public product surface.
Use the browser-based SaaS dashboard for auth, downloads, files, transcripts, billing overview and privacy flows.
Future Windows installer for local desktop workflows and bundled runtime integration.
Future macOS build for users who prefer a local desktop entry point.
Future Linux package for local workflows, testing and developer usage.
Developer-oriented tools for controlled local processing and worker diagnostics.
Desktop requirements will be finalized when signed platform builds are produced and tested.
| Web app | Modern Chromium, Firefox, Safari or Edge browser. |
| API access | Backend API and worker stack must be running for media jobs. |
| Desktop runtime | Tauri-based desktop shell is present as a project foundation, not a release. |
| Storage | Depends on downloaded media, transcripts and local runtime cache. |
| Network | Required for URL analysis, downloads, auth and billing flows. |
Use this section later for public version history, release channels and installer integrity data.
Checksums and signatures are reserved for the first signed installer release. Add SHA256 values and signing details when installers are published.
SHA256: set-on-first-signed-build Signature: planned-code-signing Short answers about the current web app, future desktop builds and installer verification.
Not yet. The project has a desktop foundation, but public installers are scheduled for a later release stage.
Use the web dashboard. It is the current supported access path for authenticated workflows.
Yes. When desktop builds are published, the download page should include SHA256 checksums and signing details.
No. Stage 3.6 is a marketing/distribution surface. Release storage or version APIs can be added later.
The fastest path today is the authenticated web dashboard. Desktop installers can be added when the desktop runtime is production-ready.