ERDB generates poster/backdrop/logo/thumbnail images with dynamic ratings on-the-fly.
| Poster 1 | Poster 2 |
![]() |
![]() |
| Poster 3 | Poster 4 |
![]() |
![]() |
| Backdrop 1 | Backdrop 2 |
![]() |
![]() |
| Backdrop 3 | Backdrop 4 |
![]() |
![]() |
| Logo |
![]() |
| Custom Logo 1 | Custom Logo 2 |
![]() |
![]() |
| Thumbnail |
Click to view Self-Hosting Instructions (Docker / Local)
git clone https://github.com/realbestia1/erdb
cd erdb- Install dependencies:
sudo npm install - Build:
npm run build - Start the app:
npm run start - App available at
http://localhost:3000
By default, npm run start now launches the standalone server in multi-process mode and uses all available CPU cores on the machine. You can override it with ERDB_WORKERS=<n> npm run start, or force single-process mode with npm run start:single.
For high performance (on-the-fly image rendering), a server with a strong CPU and plenty of RAM is recommended.
Minimum recommended:
- CPU: 4 vCPU
- RAM: 4 GB
Basic start:
docker compose up -d --buildDocker now runs a single app container in multi-process mode. By default it uses ERDB_WORKERS=auto, so the container starts one worker per available CPU core. You can pin a fixed number with ERDB_WORKERS=4 docker compose up -d --build.
Run the published image directly:
docker pull ghcr.io/realbestia1/erdb:latest
docker run -d \
--name erdb \
-p 3000:3000 \
-v ./data:/app/data \
ghcr.io/realbestia1/erdb:latestUpdate the published image:
docker pull ghcr.io/realbestia1/erdb:latest
docker stop erdb
docker rm erdb
docker run -d \
--name erdb \
-p 3000:3000 \
-v ./data:/app/data \
ghcr.io/realbestia1/erdb:latestThe public port is ERDB_HTTP_PORT (default 3000) exposed directly by the app container. Set it in the .env file.
Data (SQLite database and image cache) is persisted in ./data.
Custom port:
ERDB_HTTP_PORT=4000 docker compose up -d --buildThe repository includes a GitHub Actions workflow at .github/workflows/docker-image.yml.
- On pull requests, it verifies that the Docker image builds successfully.
- On pushes to
main, it builds and publishes the image toghcr.io/<owner>/<repo>. - On tags like
v1.0.0, it also publishes a versioned image tag.
Full documentation, interactive API builder, and Addon generator are available on our official website:
Please configure your instance and obtain the erdbConfig payload directly from the website.
Our interactive configuration tool provides the easiest way to generate the required base64url configurations for Addon Developers.
ERDB can act as a proxy for a Stremio addon and rewrite supported artwork with ERDB-generated posters, backdrops, logos, and thumbnails.
Generate the proxy manifest URL from the ERDB website in the Addon Proxy section.
The generated URL is token-based and does not use query parameters.
https://YOUR_ERDB_HOST/proxy/{token}/{config}/manifest.json
{token} is your ERDB token.
{config} is generated automatically by the site from the source addon manifest and the selected proxy options.
- Open the ERDB website and sign in with your token.
- Go to the
Addon Proxysection. - Paste the original addon
manifest.jsonURL. - Configure the image types and proxy options you want.
- Copy the generated proxy manifest URL.
- Install that URL in Stremio.
- The proxy can rewrite
meta.poster,meta.background,meta.logo, andmeta.videos[].thumbnail. - The enabled image types can be toggled in the
Addon ProxyUI. - The source URL must point to the original addon
manifest.json. - With token-based URLs, your saved ERDB configuration is resolved server-side.
- API keys and rendering settings are usually taken from the token configuration created in the workspace.
© 2026 ERDB Project










