
Kivo
Kivo is a local-first desktop app for keeping notes, files, useful links, and personal information in one place.
- Role
- Product design + full-stack development
- Outcome
- One private vault on your own device for notes, files, links, and passwords.
- Stack
- TauriReactRust
What it is
Kivo is a local-first desktop app for keeping notes, files, useful links, and personal information in one place. It is made for people who want to organize their digital things with their own device as the main place they are stored.
This case study covers the desktop app, including organizing content, search, the Password Manager, and backup tools.
The problem and the fix
Notes, documents, and saved links tend to end up scattered, with no common place to store and find them again. This is the problem the project set out to solve; it is not based on user research.
Kivo brings these things into one local vault. Collections and tags keep things organized, while Favorites and search make them quicker to find. Backup, restore, and export tools give people ways to keep their information safe or move it elsewhere. Cloud sync is outside the core scope.
What I did
- Interface design for setup, content pages, search, and settings.
- Frontend development with React 19 and TypeScript.
- Rust backend for storage, file handling, search, protection, and recovery.
- Database migrations and automated tests.
How I designed it
- 01Setup
Guided setup
Setup splits profile details, starter collections, and optional app lock into steps
- 02Navigation
Navigation by content type
Notes, Sources, Files, and Collections each have a page, with All Items showing everything
- 03Speed
Quick access to common actions
Quick Add, search, and the command palette support everyday saving and finding
- 04Choice
Advanced tools stay optional
Related search, tag suggestions, and summaries are off by default
Main features
Notes
Rich-text editing, automatic saving, and version history you can restore from.
Sources and files
Save useful links, import files into managed local storage, and preview supported file types.
Organization
Group items into collections, add tags, mark favorites, and recover items from the trash.
Search
Find items by their details and indexed content, including text pulled from PDFs. Encryption limits what content can be indexed.
Password Manager
Store logins behind a separate password and lock.
Protection and recovery
Optional field encryption, local backups, checked restores, and Markdown or JSON export tools.
Local discovery tools
Optional related-item matching, tag suggestions, and short summaries use text processing on your device, not a cloud language model.
Tech Stack
Tauri 2
connects the desktop interface to native operations.
React 19 and TypeScript
build the screens, interactions, and frontend data contracts.
Vite
supports frontend development and builds.
Tailwind CSS 4 and HeroUI 3
provide styling and interface components.
React Router
handles navigation between app screens.
Tiptap
powers rich-text note editing.
Rust
handles storage, files, search, protection, and recovery.
SQLite through rusqlite
stores structured app data; managed local storage holds imported files.
Argon2 and AES-256-GCM
support password-based key creation and authenticated encryption.
Vitest, Testing Library, and Rust tests
cover frontend and backend behavior.
These technologies are confirmed by the project files and source code. Their presence alone does not mean the app is ready for release.
Hard parts and how I solved them
- Keeping search consistent with encryption
- Search indexes can keep information taken from protected content. Kivo clears saved content-search and related-search data when encryption is turned on, and limits indexing while protection is active.
- Restoring a vault without losing the current copy
- A restore replaces both the database and managed files. Kivo checks the backup before replacing anything and makes a safety copy to roll back to. Tests cover broken backups; checks for real desktop interruptions are still open.
- Keeping app lock separate from data protection
- Hiding the screen is different from encrypting stored content. Kivo keeps app lock and the Password Manager separate, with optional encryption for selected content fields, note versions, and managed files. Titles, tags, file names, and other details stay readable, and an independent security review is still pending.
- Adding discovery without the cloud
- Related search, suggestions, and summaries use text processing on the device. This fits the local-first goal, but it is not generative AI or proven understanding of meaning.
How it works
- 1
Set up the vault.
Enter profile details, choose starter collections, and optionally turn on app lock.
- 2
Add something worth keeping.
Create a note, save a source, or import a file from the right page or with Quick Add.
- 3
Organize the item.
Add it to a collection or tag it, and mark often-used items as favorites.
- 4
Find it again.
Browse content pages, use search, or open the command palette. What search can find depends on indexing and encryption settings.
- 5
Look after the vault.
Review storage, recover items from the trash, restore earlier note versions, and use Settings for protection, backup, and export.
Results
- Reviewing the source confirms connected screens and backend commands for the core vault and supporting tools.
- Recorded checks report 543 frontend tests passing across 47 files, successful type checks and builds, and passing Rust test suites. These are earlier recorded results, not checks rerun for this write-up.
- Windows desktop checks are still open, including protection, backup and restore, and advanced features.
- An independent security review is still pending. Encryption covers selected data, not the whole database or every outside copy.
- No user numbers, usability results, speed tests, or time savings are reported.
What I learned
What I learned
- Local storage still needs recovery planning: keeping data on the device makes checked backups, restores, and exports an important part of the product.
- Protection affects more than the original content: search indexes, note versions, temporary files, and backups all need clear protection rules.
- Automated tests and desktop checks answer different questions: passing tests support specific behavior, while native file dialogs, previews, interruption recovery, and full user journeys still need checks on a real desktop.


