Select an entry to preview the full post in the reading panel.
Wed, 22 Jul 2026 10:00:00 GMT
Why We Replaced Our Cloud Knowledge Base with a 10MB SQLite File
SQLite FTS5, Litestream replication to B2, and 0.5ms local search speeds.
For a zero-maintenance self-hosted database, multi-node cloud clusters like PostgreSQL or MongoDB are complete overkill.
SQLite FTS5 indexes handle full-text search across thousands of notes in less than 0.5 milliseconds, compiling directly into a single file.
To manage backup concerns, we integrated Litestream. It monitors the SQLite write-ahead log (WAL) and streams incremental changes asynchronously to a private Backblaze B2 bucket every second.
This architecture guarantees sub-millisecond local reads with secure offsite backup coverage—the ultimate blueprint for private self-hosted knowledge databases.
Mon, 20 Jul 2026 12:00:00 GMT
MIT vs. BSL: Why We Split Our Ecosystem Into fid and kikr
Frictionless open-core utilities vs. commercial sync hosting.
Trust is foundational in Personal Knowledge Management (PKM).
To ensure your notes are never locked behind proprietary subscription walls, the core parser library (Fid CLI) is licensed under the MIT license. It is 100% open-source and free, handling Tesseract OCR, local search, and file formats (Evernote ENEX, Bear, Joplin) entirely offline.
The commercial self-hosted server container suite (Kikr Cloud) uses the Business Source License (BSL 1.1). It is free for non-commercial personal usage but requires a subscription for hosted commercial team networks.
This open-core delineation keeps your core parser tools forever free and community-developed, while funding the continuous engineering of Kikr's webhooks, visual triage dashboards, and compliance filters.
Tue, 21 Jul 2026 14:00:00 GMT
Time, Talent, or Treasure: How to Support the SeeWhatSticks Open-Core
Time, talent, and funding options for open-core support.
As Adam Curry says on the No Agenda Show: Time, Talent, or Treasure are how we show support for the tools we rely on.
If you want to contribute to the SeeWhatSticks note-routing ecosystem, there are multiple avenues:
1. TALENT: Submit code pull requests, fix bugs, or build new note importers in the open-source repositories.
2. TIME: Write documentation, share tutorials, and help test alpha builds on your local dev vaults.
3. TREASURE: Support us financially via our fiat or Bitcoin Lightning network tipping widgets to fuel development.
Finally, we believe in supporting the community. If you have a charitable organization or cause in need of knowledge management and note-routing services, please reach out to us:
[email protected].