That's the first thing I'm going to do as soon as it's possible! I recently refactored the code base to a monorepo, and still need to make some adjustments so it'll run stable again. Stay tuned :)

Ebooks in an S3 compatible storage bucket, metadata in a Postgres database. That has the huge advantage of being able to do full text search and kNN similarity right in the database, for example.

Colibri is built around a pretty solid data schema (I hope). Check out the migrations folder if you’re curious :-)

Thanks you, that means a lot. And good luck for your search!

So, Colibri is intended to be a companion to Calibre, maybe do like 80% of what it does, but not all of it. Also, I want Colibri's core to have a fully clean collar: It handles your personal books, but will not be able to automatically de-DRM books and such. However, the way book assets work, you're of course free to just attach an encrypted AZW3 file to a book!

> Are these ebooks supported and does it only supports metadata, what about the content search for these ebooks?

Have you seen https://github.com/colibri-hq/colibri/issues/45? Content search is planned, but requires access to a book's text content, obviously. My recommendation would be to use Calibre to strip DRM and convert the books to epub/mobi files, and import those to Colibri; this has the general benefit of ensuring access to content you bought without depending on Amazon's good will :-)