velith watches your notes accumulate, sorts them into buckets by genre and topic, and — the moment a bucket crosses the threshold you set — writes the artifact itself. A report, a newsletter, a book. Unattended.
The three stages below are the whole product — a pipeline that runs without you.
A thought from a book you're reading, a lesson from work, a half-formed argument. Type it into the dashboard or the mobile app — every note is kept and counted.
Each note is classified into a (genre, topic) bucket — keyword heuristics offline, or a language model for semantic clustering. You watch buckets fill instead of managing folders.
Set a rule: ten notes on one topic. When the bucket crosses it, a six-phase pipeline — outline, draft, quality gates, edit, publish — hands you a finished artifact.
Your keys, your server, your words.
Notes land in (genre, topic) buckets on their own — offline keyword heuristics, or semantic clustering through your model.
"Fire at 10 notes on one topic." Rules are the only management the system asks of you.
Ideation → outline → draft → continuity and style gates → edit → publish. Every phase must pass before the next runs.
The model bills your provider account. Keys are sealed with AES-256-GCM per tenant and never leave the server.
Artifacts render to whatever the destination needs, with expiring signed download links.
A single binary serves one writer or a team — per-user isolation, SSO sign-in, per-user API keys.
Payment is handled by PortOne in Korea and Stripe everywhere else — velith never sees your card.