Slite vs Alexandrie
Alexandrie is the better fit for teams prioritizing self-hosting, source-code access, offline use, Markdown, and control of their data and infrastructure. Slite remains the stronger choice when the core requirement is verified documentation with permission-aware AI answers and automated knowledge-maintenance workflows; those capabilities are not documented for Alexandrie.

Decision guide
The practical reasons to choose either option, based on documented capabilities.
Choose Alexandrie if
- Teams required to host their knowledge base on their own infrastructure
- Developers and technical writers using extended Markdown, LaTeX, diagrams, snippets, and full-text search
- Organizations needing offline access with synchronization after reconnecting and no native mobile-app requirement documented today for Alexandrie via its PWA/web experience instead of native apps properly speaking (the P
Stay with Slite if
- Document verification and visible freshness signals are required
- Permission-aware AI answers across documents and connected company tools are central to knowledge retrieval
- Teams depend on stale-document detection, bulk maintenance queues, AI-drafted fixes, or approval routing of updates to owners for review and approval using Slite's Agent and workflows as documented in the profile, none o
Deployment and operations
Alexandrie is MIT-licensed and self-hostable with a supplied Docker Compose configuration; Kubernetes deployment is not documented. Its stack includes frontend, backend API, MySQL, and object-storage services. Production operators are responsible for configuration, backups, upgrades, HTTPS termination, secrets, database and storage operation; the guide recommends a reverse proxy and not exposing MySQL or RustFS directly. The project website says its maintainer works on it in spare time, which is
Migration considerations
Alexandrie documents Markdown-file import, PDF export, and ZIP import/export for selective nodes, metadata, or full platform states. No direct Slite importer or guaranteed preservation of Slite permissions, comments, verification state, AI metadata, or document hierarchy is documented, so a pilot export/import and manual validation would be required.
Feature fit
What Alexandrie covers
- Team knowledge-base documents
- Collaborative document editing
- Hierarchical workspaces and documents
- Granular document permissions
- Public document sharing
- Full-text document search
- Comments and mentions
- Knowledge analytics
What’s different or missing
- Document verification workflow
- Permission-aware AI answers
- Cross-tool AI search
- Knowledge maintenance panel
- AI-drafted document updates
- MCP access for AI agents
Project snapshot
- GitHub stars
- 2,326
- Contributors
- 32
- Language
- Vue
- Last commit
- Aug 13, 2026
- Latest release
- Aug 12, 2026
Categories: Document Collaboration, Knowledge Management, AI Assistants, Project Management, Note Taking, File Sync & Storage, Calendars & Scheduling, Task Management, Search Engines, Digital Whiteboards
Sources and editorial review14 linked sources
Public documentation supports this comparison. Automation assists collection and classification; editorial standards and corrections remain the responsibility of Kris.
The open-source, offline-first Notion, Obsidian & Confluence alternative. Advanced Markdown, multi-tenant teams, OIDC/SSO, and local S3 backups. Deploy in one command.
repository description · github.comA self-hosted, open-source knowledge base with an extended Markdown editor.
readme · github.comGranular Organization: Multi-tenant architecture supporting Teams, Workspaces, Categories, and nested Documents.
readme · github.comFull-Text Indexing: Instant lookup with snippet highlights and precise relevancy sorting scores.
readme · github.com5-Level Access Model: Fine-tune user privileges from None, Read, Write, Admin, to Owner status per node or workspace.
readme · github.comOffline-First PWA: Install on any desktop or mobile device with full offline capabilities and seamless synchronization.
readme · github.comOne-Command Deployment: Bring up the entire full-stack application instantly using Docker.
readme · github.comA self-hosted, open-source knowledge base with an extended Markdown editor.
verdict · github.com5-Level Access Model: Fine-tune user privileges from None, Read, Write, Admin, to Owner status per node or workspace.
shared feature · github.comYes, Alexandrie is designed with offline-first principles. Your notes are available locally and sync when you reconnect.
best for · alexandrie-hub.frIn production, you should: For advanced configuration options for backend you can create your own config.toml file with the same structure as the default one (in backend/config.toml ) and add the following environment variable to your .env file:
deployment · alexandrie-hub.frYes, Alexandrie is 100% open-source under the MIT license. You can use it, modify it, and distribute it freely. No hidden costs, no premium tiers.
deployment · alexandrie-hub.frData Portability: Comprehensive ZIP import/export tools allow users to backup or restore selective nodes, metadata configurations, or entire platform states in a single action.
migration · github.comYes! You can import Markdown files from other apps like Notion, Obsidian, or any Markdown editor. Export to PDF with beautiful formatting is also supported.
migration · alexandrie-hub.fr



