Alexandrie Hub: A Gorgeous Self-Hosted Note-Taking Knowledge Base Alternative
If you hang around the self-hosting community long enough, you will eventually come to a very stark realization: finding the "perfect" note-taking system and personal knowledge base is a never-ending, borderline unhealthy obsession for developers and homelabbers alike. We are constantly searching for that elusive golden ratio of speed, aesthetics, data ownership, and cross-platform accessibility.
For years, I personally bounced violently between two extremes. On one side, cloud apps like Notion or Roam Research look absolutely phenomenal, offer robust databases, and are accessible everywhere. But using them fundamentally forces you to surrender your deeply personal data, your intellectual property, to a third-party server where it can be mined, locked behind a subscription paywall, or lost forever if the startup folds. On the other extreme, local-first applications like Obsidian are incredibly powerful, blazingly fast, and wildly secure because everything lives strictly on your local hard drive. However, trying to flawlessly sync a local Obsidian vault across locked-down corporate work laptops, personal desktops, and mobile devices without paying for their official sync service usually requires hacking together custom Git sync servers, Syncthing conflicts, or frustrating iCloud workarounds that frequently break.
I desperately needed something perfectly in the middle: a self-hosted, web-first Markdown engine that I fully control, accessible anywhere, without requiring a thick client installation on the device I'm using. That's precisely when I discovered and deployed Alexandrie Hub into my stack.
In this comprehensive guide, I am going to show you exactly why Alexandrie Hub is rapidly becoming my absolute favorite web-based knowledge base. We will explore its technical architecture, see exactly how it stacks up against the heavyweights like Obsidian and BookStack, and walk through how you can deploy it securely in your own home lab in under five minutes.
Why Alexandrie Hub? (Exploring the Core Technical Features)
Alexandrie Hub is a beautifully designed, lightweight, open-source web application designed specifically and exclusively for personal knowledge management (PKM). It deliberately drops the bloated PHP runtimes and complex SQL database setups required by traditional corporate wikis like BookStack or MediaWiki. Instead, it focuses ruthlessly on raw speed, pure Markdown compliance, and a highly polished visual design that rivals proprietary SaaS apps.
Here are the specific, standout features that actually matter when you deploy it for daily use:
1. A Native Web-First Architecture
This is the absolute killer feature that solved my synchronization nightmare. Because Alexandrie Hub is fundamentally a web service running continuously in a Docker container on my Proxmox lab, I no longer need a dedicated desktop client installed on every machine I own. I simply open Chrome on my locked-down corporate laptop, type in my local IP address (or my secure Cloudflare Tunnel domain), log in, and my entire, up-to-date knowledge base is instantly there. I can write notes, organize folders, and search my brain without ever installing a local executable. There are zero syncing conflicts, zero iCloud delays, and zero Git push errors because every device is just viewing the exact same live web server.
2. Flawless, Real-Time Markdown Editing
As a systems engineer, I write exclusively in Markdown. It is the universal language of the tech world. Alexandrie offers a stunning, distraction-free, real-time editor that renders your formatting instantly. When you type out headers, inject code blocks, or format complex bulleted lists, the editor parses and displays them beautifully in real-time without ever requiring a clunky page refresh or a split-screen "preview" pane. It feels incredibly snappy and responsive, mimicking the feel of a native application while running in a browser tab.
3. Built-In Graph Visualization Engine
Obsidian arguably made the "Graph View" famous—a visual, interactive web showing exactly how all your various notes and concepts connect to each other through internal links. It is a brilliant way to visually navigate complex technical documentation. Alexandrie Hub brings this exact functionality directly into the web browser. It's built-in natively to the core application, requiring absolutely zero plugin configuration, third-party JavaScript libraries, or messy setup. You simply click the graph icon, and you can visually explore your entire brain directly in the web UI.
4. Native Mermaid Diagram Support
As a home labber and systems architect, I spend a significant amount of time drawing network diagrams, server topologies, and CI/CD flowcharts. Alexandrie supports Mermaid.js syntax natively out of the box. This means I can generate beautiful, complex flowcharts and sequence diagrams using pure, version-controllable text directly inside my notes, without ever having to open a heavy external tool like Visio or draw.io and embed screenshots.
Alexandrie Hub vs. The Competition: A Technical Breakdown
So, how does it actually compare to the established heavyweights in the self-hosted arena? Let's look at the data.
| Feature Comparison | Alexandrie Hub | Obsidian | BookStack |
|---|---|---|---|
| Core Architecture | Self-Hosted Web Server | Local Desktop/Mobile App | Self-Hosted Web Server |
| Data Storage Format | Markdown + Database | Raw .md Files on Disk |
HTML / Relational DB |
| Native Graph View | Yes (Built-in) | Yes (Built-in) | No |
| Plugin Ecosystem | Minimal / Core Features Only | Massive (1000+ Plugins) | Limited / API Based |
| Multi-User Support | Yes (Roles & Permissions) | No (Single User Vaults) | Yes (Enterprise Grade) |
Deployment: The Docker Compose Setup Guide
Deploying Alexandrie Hub is wonderfully trivial if you already have a working Docker environment. It is packaged neatly as a single, highly optimized container. Here is the exact, production-ready docker-compose.yml file that I currently use to spin it up in my lab:
services:
alexandrie:
image: ghcr.io/smaug6739/alexandrie:latest
container_name: alexandrie_hub
restart: unless-stopped
ports:
- "3000:3000"
environment:
- NODE_ENV=production
- PORT=3000
# Add database credentials here if using external DB
volumes:
- ./alexandrie-data:/app/data
Simply copy this file to your server, run the standard docker compose up -d command, open your web browser, navigate to port 3000 on your server's IP address, and you will be immediately greeted by the initial setup screen. It is remarkably fast to get off the ground.
Troubleshooting & Architectural Edge Cases
If you are seriously considering deploying this as your primary daily driver in a home lab, you must keep these technical caveats in mind:
- Data Portability & Lock-in: This is a major divergence from Obsidian. Alexandrie fundamentally stores your note content and metadata securely inside a database structure, not as a folder full of easily accessible, raw
.mdtext files on your host file system. If you ever decide you want to migrate away to a different tool years from now, you cannot simply copy and paste a folder; you must rely entirely on the application's built-in export tools. Therefore, it is critical that you ensure you are taking automated, daily backups of the entire mapped/app/dataDocker volume to prevent catastrophic data loss. - Reverse Proxy and WebSocket Issues: If you are exposing Alexandrie Hub to the internet by placing it securely behind a reverse proxy like Nginx Proxy Manager, Traefik, or Cloudflare Tunnels, you must ensure that your proxy is explicitly configured to pass WebSocket (WS/WSS) connections. The beautiful real-time markdown editor and the interactive graph views rely heavily on persistent WebSockets to function smoothly. Failing to pass WebSocket traffic will result in constant, frustrating disconnect errors and a broken UI.
Conclusion & Next Steps for Your Lab
So, what is the final verdict? If you are a power user who requires thousands of custom community plugins, offline-first access, and demands that your data exist as raw, local text files, you should absolutely stick with Obsidian. It remains the king of local PKM. But if you want a beautiful, highly polished, zero-configuration Markdown knowledge base that you can access instantly from any web browser in the world—without fighting sync engines—Alexandrie Hub is a phenomenal piece of software. It strikes the perfect, elegant balance between modern aesthetic design and full self-hosted control.