---
title: "Deploy Grimmory"
description: "Community fork of BookLore for self-hosted libraries."
category: "Other"
url: https://railway.com/deploy/grimmory-1
---

# Deploy Grimmory

Community fork of BookLore for self-hosted libraries.

**[Deploy Grimmory on Railway](https://railway.com/template/grimmory-1)**

- **Creator:** Matt Spear
- **Category:** Other
- **Total deploys:** 4

## Template content

### grimmory-railway https://raw.githubusercontent.com/grimmory-tools/grimmory/develop/assets/logo.svg

- **Source:** matthewspear/grimmory-railway
- **Public domain:** Yes

### mariadb:latest https://cdn.svgporn.com/logos/mariadb-icon.svg

- **Image:** mariadb:latest

## Documentation

# Deploy and Host Grimmory on Railway

Grimmory is a community-maintained fork of BookLore for self-hosting your digital book and audiobook library. It keeps the familiar BookLore-style experience for managing EPUBs, PDFs, and audiobooks, with metadata fetching, cover handling, reading progress, and a modern web UI.

## About Hosting Grimmory

Grimmory runs as a Java application server backed by MariaDB. This template handles the full setup: the Grimmory app, a MariaDB database, and persistent volume storage for your book files and app data. Railway's single-volume-per-service limitation is handled with bind mounts, so your books and configuration persist across redeploys. Once deployed, create an account, point your library at `/books`, and start uploading.

## Common Use Cases

- Managing a personal digital book and audiobook collection with automatic metadata fetching
- Self-hosting a BookLore-compatible library manager with an actively maintained community fork
- Organising and tracking reading progress across multiple devices

## Dependencies for Grimmory Hosting

- MariaDB (included in template)
- Persistent volume storage (included in template)

### Deployment Dependencies

- [Grimmory GitHub](https://github.com/grimmory-tools/grimmory)
- [BookLore Documentation](https://booklore-app.github.io/booklore-docs/)
- [MariaDB](https://mariadb.org/)

### Implementation Details

This template uses a custom Dockerfile that wraps the official `grimmory/grimmory` Docker image. A runtime entrypoint script maps subdirectories from a single Railway volume (`/booklore-data`) to the paths Grimmory expects (`/app/data` and `/books`) using bind mounts.

## Why Deploy Grimmory on Railway?

Railway handles the infrastructure so you can focus on your library. With one click, you get a fully configured Grimmory instance with MariaDB and persistent storage - no Docker Compose, no server management, no manual database setup.

## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — [Jul'26] Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/grimmory-1