English
libremdb Hosting
Look up movies, shows, and cast on a private, ad-free front-end for IMDb data.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- ghcr.io/zyachel/libremdb:latest
- Default port
- 3000
How libremdb works
libremdb receives a title or search request, retrieves the relevant information from IMDb through the server, and renders it in a simplified responsive interface. Images and videos are proxied through the instance so the visitor’s browser does not need to request those assets directly from IMDb. A theme preference can be kept locally in the browser.
The extra proxy path adds latency, and the project documentation acknowledges that not every IMDb route is implemented. Search, reviews, images, or title pages may also fail when IMDb changes access rules or requires an account for information that was previously public. The frontend cannot correct or guarantee the underlying dataset.
Key libremdb features
The project focuses on an ad-free, tracking-reduced, responsive presentation of movie, television, and game information. Dark and light themes improve readability, while proxying media reduces direct exposure of the visitor’s network and browser details to the upstream service. Familiar IMDb paths can be redirected to a chosen instance.
libremdb remains a reader rather than a personal media database. It does not provide user watchlists, ratings, reviews, account synchronisation, streaming access, or a complete copy of every IMDb page. Its current feature coverage and stability follow the upstream project and IMDb’s continuing compatibility.
Who uses libremdb
Privacy-conscious viewers can inspect title information, communities can share cleaner links, and administrators can provide a preferred internal frontend for public movie references. It works best for casual browsing where a simplified page is sufficient.
The service is not suitable as an authoritative film database, rights source, parental-advice guarantee, or durable research archive. Important information should be confirmed through appropriate primary sources.
Self-hosting libremdb: requirements and cost
Resource use depends on searches, title pages, proxied images and videos, concurrent visitors, upstream latency, cache behaviour, and failed requests. The exported libremdb setup does not provision PostgreSQL or MariaDB. Because the mapping marks the frontend as storage-driven, 50 GB on Plan 3 is a realistic starting point where cached or retained assets grow, while 100 GB on Plan 4 better suits a larger reader.
AvaHost maps libremdb to Plan 1 at €2. The libremdb package adds one-click provisioning, a custom HTTPS hostname, automatic application updates, and scheduled backups. The plan does not include an IMDb account, streaming rights, a licensed data feed, content ownership, or assurance that every upstream route will work. Users should treat displayed data as third-party information and verify consequential facts independently.
F.A.Q
libremdb starts at €2 on Plan 1. Searches, title pages, proxied media, concurrent users, upstream latency, cache behaviour, and failures affect resource use. The mapping treats it as storage-driven: Plan 3 supplies 50 GB for growing cached assets, while Plan 4 supplies 100 GB for a larger public reader.
A custom hostname can serve libremdb with automated HTTPS once DNS points to AvaHost. Update any browser redirection rules to use the final address and test searches, title pages, images, videos, and mobile layouts. After changing domains, remove old instance URLs from extensions, bookmarks, and shared documentation.
libremdb is a read-only alternative frontend. It does not provide an IMDb account, personal watchlists, ratings, review publishing, subscription streaming, or rights to the displayed content. The information comes from IMDb, and some routes are not implemented. Use the original authorised service or another appropriate source when account features are required.
Each request travels through the libremdb server to IMDb and back, which adds latency. IMDb can also change routes, markup, access rules, or account requirements, causing searches or pages to fail until the project adapts. The application cannot guarantee completeness or availability, so confirm important title information through suitable primary sources.