Core capture flows do not require a separate Voryn account before you can start recording.
Current product home
Focused software, starting with one real public product.
Zestva Studio builds calm software for people who think out loud and want the result to stay useful. Today, that public product is Voryn: an iPhone capture workflow you can inspect before you commit to it.
Export is part of the documented product surface, along with Voryn bundle backup paths.
Power users can supply external model API keys for cost and model control.
Flagship Voryn
Capture the thought. Keep the shape.
Voryn is an iPhone capture tool for people who think out loud and want the result to stay useful. It earns that spot by turning raw thought into notes, tasks, summaries, and exports instead of leaving it stuck as untouched audio.
Why it belongs here
One flagship app with enough public detail to judge before you commit.
Voryn combines fast recording, quick memo entry, AI-assisted structure, and exportable results in one iPhone workflow without making a separate web account the starting point.
Fast capture on iPhone
The product already supports one-tap voice capture, quick memo entry for quiet environments, and draft recordings that can be resumed later.
Structure after the capture
Voryn is not just a recorder. It can turn raw input into task lists, journal-style writing, summaries, and prompt-based outputs.
Private-first with honest limits
The local core matters, but some transcription and AI paths can use Voryn-managed or third-party providers depending on the feature and configuration.
Portability is part of the promise
Export paths already described in the product materials include Markdown, CSV, PDF, and Voryn bundle backups.
How it works
Capture first. Shape later. Keep or export when it matters.
This is the core promise the page has to make legible: Voryn catches the thought first, then helps you decide how much structure to add without trapping the result in one closed system.
Capture quickly
Record a thought or type a quick memo as soon as it appears.
Process intentionally
Transcribe, summarize, or run a built-in or custom prompt when you want more structure.
Keep or export the result
Leave it in your timeline, revisit it later, or export it into the rest of your workflow.
Public boundaries
Trust comes from visible pages and visible limits, not just polished promises.
A product home should help someone judge what is maintained, what depends on outside services, and where support starts when the product becomes part of real work.
Readable public pages
Product, privacy, terms, and support stay visible enough to inspect before you commit to the workflow.
Honest network boundaries
When a feature depends on hosted AI or third-party providers, the public surface should say so clearly.
Support that stays attached
Help should stay close to the actual product instead of disappearing into an app store listing.
Studio close
The goal is not another giant notes app. The goal is to shorten the distance between an idea and an action.
Learn the studio context, or go straight to contact when the product docs are not enough.
Keep reading
Learn the studio context, or go straight to support.
The About page explains the studio posture behind the product. The Contact page is the direct path when the public docs are not enough.