Introduction to Notivae
Why Notivae?
Notivae was created to solve the limitations of existing knowledge and note-taking platforms. Tools like Notion, Outline, Obsidian, Logseq, and Joplin each offer parts of the solution—but not the whole. Some are closed-source, cloud-dependent, or hard to self-host. Others lack real-time collaboration, structured access control, or robust offline support.
Notivae brings together the best of these systems while staying fully self-hosted, markdown-native, and privacy-first.
Feature Comparison
Feature | Notivae | Notion | Outline | Obsidian | Logseq | Joplin |
---|---|---|---|---|---|---|
For Teams and Solo use | ✅ | ✅ | ✅ | ❌ | ⚠️ | ❌ |
Fully Self-Hosted | ✅ | ❌ | ⚠️ | ✅ | ✅ | ✅ |
Real-Time-Sync | ✅ | ✅ | ✅ | ❌ | ⚠️ | ❌ |
Real-time Collaboration | ✅ | ✅ | ✅ | ❌ | ⚠️ | ⚠️ |
Remote Access (Internet-Ready) | ✅ | ✅ | ✅ | ⚠️ | ⚠️ | ⚠️ |
Web-First UI (no install needed) | ✅ | ✅ | ✅ | ❌ | ❌ | ⚠️ |
Offline-First Support | ✅ | ⚠️ | ❌ | ✅ | ✅ | ✅ |
Hierarchical Documents | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Markdown-Native Editing | ✅ | ⚠️ | ✅ | ✅ | ✅ | ✅ |
Other Text-Based Documents (code, note dumping, ..) | ✅ | ✅ | ⚠️ | ✅ | ✅ | ✅ |
Export to Markdown/PDF | ✅ | ✅ | ⚠️ | ✅ | ✅ | ✅ |
Snapshot-Based Versioning | ✅ | ❌ | ✅ | ⚠️ | ⚠️ | ✅ |
Inline Comments & Discussions | ✅ | ✅ | ⚠️ | ❌ | ❌ | ✅ |
Per-User Access Control | ✅ | ✅ | ✅ | ❌ | ⚠️ | ✅ |
⚠️ = Partially supported or requires plugins/workarounds
❌ = Not supported
Got Feedback?
Notivae is early-stage — rough, changing, and evolving. We'd love your input! Head to the GitHub repo to report issues, suggest improvements, or star the project.
Thanks for trying out Notivae. Your knowledge. Your structure. Your control.
LLMs.txt Support
To improve compatibility with AI tools, Notivae provides a machine-readable llms.txt
file.
This file helps large language models (LLMs) — such as those used in AI-powered search, summarization, or assistant systems — understand the structure and content of our documentation. It includes clean, structured Markdown for each public page, along with its canonical URL.
Developers building tools, bots, or integrations can use this to:
- Feed context into chat-based assistants
- Build semantic search or RAG pipelines
- Preprocess documentation for embedding/indexing