My only gripe with wiki.js was the use of SQL for local storage. My wiki must be future proof and locking myself in an obscure SQL database was the deal breaker. I know that you can sync with a Git repo, but it felt like an overkill.

Thank you for your comment, however, considering that renting a VPS with similar specs would cost twice, if not more, for a single year, I believe that factoring in a second drive for RAID configuration and a potential UPS (although I would not mind the downtime) is more than possible.

While I totally agree that managing hardware at home can be cumbersome, if you need large and slow amounts of storage - e.g. for torrenting o plex - VPS are too expensive. With a ~250 € investment I could get a server with 2TB HD that consumes 50W at max while the same VPS would cost me twice - if not more - for 12 months.

+1 Dokuwiki. It is a little complicated than most to configure the first time, but once you have everything running, it will work without complaints. Also, the whole wiki is stored as plain text files, which is awesome for backups.

I researched using Bookstack but you can access the pictures even if you do not have an account and have the right URL, anybody can see the picture/attachment file in any browser.

Not having well-implemented access control was a big No No for us.