A lightweight, self-hosted bookmark service with tagging, search, and auto-metadata extraction, ideal for RaspberryPi deployment.
NeonLink is a simple, open-source bookmark service that users can self-host on their own servers. It allows individuals to save, organize, and search bookmarks privately, with features like automatic metadata extraction and customizable backgrounds. It solves the need for a lightweight, private alternative to cloud-based bookmark managers.
Users who want a private, self-hosted bookmark solution, especially those with limited hardware like RaspberryPi, or developers seeking a minimal, customizable bookmarking tool.
Developers choose NeonLink for its ease of self-hosting via Docker, low system requirements, and focus on privacy without sacrificing core features like tagging and search. Its open-source nature allows for customization and community contributions.
Simple self-hosted bookmark service.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
With minimal dependencies and low resource consumption, it's specifically optimized for deployment on RaspberryPi, as stated in the README, making it ideal for low-power hardware.
All data stays on your own server, ensuring complete control and privacy without relying on third-party clouds, aligning with its core philosophy of simplicity and self-hosting.
Provides straightforward Docker and Docker Compose commands for installation, including multiarch builds for platforms like ARM, reducing setup complexity for self-hosting.
Fetches icons, titles, and descriptions from bookmarked URLs automatically, as highlighted in features, saving manual entry time and enriching bookmark entries.
Allows personalization with custom background images via volume mounts in Docker, enhancing user experience without requiring code changes.
Designed for personal use only, lacking multi-user support or collaboration features, which restricts it to individual deployments and limits team adoption.
Uses SQLite as the database, which may not perform well with large numbers of bookmarks or concurrent access, as admitted in the tech stack, posing risks for growing datasets.
The README doesn't mention backup or export features, requiring users to manually manage data persistence through file system copies, increasing maintenance overhead.
Setting up for development requires Node.js, npm, and global installations like fastify-cli, which can be cumbersome for contributors compared to simpler stacks.