Palimia

A personal cultural library

Palimia brings movies, TV series, and video games together in one personal space. Its goal is to replace scattered lists with a private library where every work keeps its status, progress, rating out of ten, favorite state, and personal notes.

The main journey starts with searching a catalog supplied by external providers, continues with adding a work to the library, and leads to personal tracking and statistics. The application is designed as a cultural profile that can expand over time without mixing catalog data with each user’s private choices.

A deliberately gradual scope

The planned first beta focuses on movies, TV series, and video games. The data model and some integrations also anticipate anime, manga, and books, but these media remain outside the public scope until their sources and usage rights have been reviewed.

Developed social features — public profiles, reviews, lists, and relationships — also remain disabled. The product therefore stays centered on a private tracker. Planned recommendations follow the same principle: they should be personal and explainable, using understandable signals rather than an opaque score.

A full-stack foundation

The project is a modular monolith built with Next.js and strict TypeScript. PostgreSQL and Prisma support the catalog, provider references, and personal states, while Better Auth handles authentication. Provider calls remain server-side, and their data is validated and normalized before import.

This architecture gives each work a shared identity without flattening the characteristics of each media type. Imports are designed to be idempotent and safe under concurrency, while data provenance stays separate from the ratings, progress, and lists created by users.

Why Palimia is not in production

Palimia is not in production, and its launch status remains blocked. The written permissions required for some uses of provider data have not all been obtained and reviewed. In particular, the public scope must exclude sources that do not yet allow the intended tracking, storage, or display.

The repository includes unit, component, PostgreSQL, and Playwright tests, alongside security, privacy, and release checks. Its deployment architecture is prepared, but evidence from a target environment — configuration, migrations, backup and restore, monitoring, staging tests, and final legal review — is still incomplete. These local checks describe the project’s engineering state; they are neither a production release nor user metrics.