Local-first data handling
History, screenshots, archives, and learning signals are designed to stay visible and anchored locally instead of disappearing into a remote black box.
Local-first guide
A local-first speech-to-text desktop app for prompt-heavy work.
VoiceSlate is built for people who want AI voice workflows without giving up archive visibility, provider choice, or support clarity.
What local-first means
Local-first is not only storage. It is a workflow boundary.
The point is to keep history, screenshots, and learned context visible on-device while still letting you use external providers when you choose to.
Bring your own providers
VoiceSlate is useful before a hosted stack is complete, so provider choice stays flexible rather than hidden behind a single locked workflow.
Inspectable memory behavior
Project memory, archive summaries, and learned vocabulary are intended to be inspectable and manageable instead of silently reshaping work.
Clear support and release trail
Trust is also operational. The public download path, release history, and support email help people evaluate what is real today.
Take the practical step
Review the trust posture, then install the product or compare plans.
This guide is about trust boundaries. The next useful actions are downloads, pricing, and the trust center.