Capture before organization
A useful system should accept a thought or source without demanding folders, tags, graph upkeep, or AI configuration first.
Keep knowledge close enough to change your thinking.
Arivu keeps saved sources and personal notes on your server, with local search and optional AI learning.
The simpler workspace and source learning described here shipped in Arivu 1.7.0.
A collection is not yet a second brain.
Links, documents, quotes, and notes often end up in separate tools. Even a well-organized archive can go quiet when it offers no path from capture to connection, discovery, and learning.
Arivu keeps those forms of knowledge together and makes their relationships inspectable. It supports quick retrieval when you know what you need and careful exploration when you do not.
Simple capture. Visible evidence. Durable ownership.
Connections should be legible
Explicit links, provenance, confidence, citations, and bounded views help you understand why material appears together.
AI should remain optional
Capture, reading, notes, local search, and Graph work without a provider. Chat and quizzes require one, with consent before sending passages.
Your knowledge should travel
SQLite, asset-aware host backups, and account-level exports keep recovery and portability understandable.
Sharing should be deliberate
Revocable secret links publish point-in-time evidence copies, not a social feed or a live view into private work.
Tamil · அறிவு
Arivu
Knowledge or wisdom.
Information becomes valuable through understanding.
Arivu is a Tamil word for knowledge or wisdom. The name reflects the product’s purpose: helping scattered material become connected knowledge you can return to and use.
Focused on personal knowledge, not feature accumulation.
Home, Library, Notes, and Search form the primary experience. Review and Graph are secondary. Planning tools and standalone Insights are retired; useful legacy writing becomes notes, and full backups keep the original records.