Skip to main content
[ PIER ]

Berth

A lightweight self-hosted audiobook server with Android and iOS apps.

Service #audiobook#media#library#s3#mobile

Berth is an open-source audiobook server written in Rust. Upload books through the web admin, store the files on local disk, S3-compatible storage or Google Drive, and listen in the Berth app on Android and iOS — phones connect by scanning a QR code.

Deploy with Pier

  1. 1 Open the Pier dashboard and click Add service.
  2. 2 Pick Berth from the template list.
  3. 3 Choose the version, set a service name, and Pier provisions the container, storage, and ports automatically.
  4. 4 Attach a domain if you want HTTPS. Traefik auto-provisions the Let's Encrypt certificate.

What is Berth?

Berth is a self-hosted audiobook server written in Rust. You upload books through a web admin, keep the files on local disk, any S3-compatible storage or Google Drive, and listen in the Berth app on Android and iOS. Phones connect by scanning a QR code from the admin.

Unlike folder-scanning media servers, Berth treats its database as the source of truth: books are entities you manage in the admin, and the audio can be delivered straight from object storage or a CDN through short-lived signed URLs.

How Pier deploys it

Pier uses the official ghcr.io/joveptesg/berth image (amd64 and arm64). Port 8080 internally, behind Traefik. One persistent volume — /data — for the SQLite database, automatic pre-migration backups, local storage and secret.key.

There are no default credentials. After the first start open the service logs in Pier and follow the one-time setup link to create the admin. Attach a custom domain, then set it under Settings → Internet address so the QR codes your listeners scan point at the public HTTPS URL. Keep a copy of secret.key outside the backups.

When NOT to use Berth

If you want podcasts and ebooks in the same app, or a library built by scanning an existing folder tree, use Audiobookshelf. For video, use Plex or Jellyfin. Berth is in early development — keep backups.

Key features

Web admin for books and users

Upload audiobooks, manage the library and invite listeners from a browser. The database is the source of truth — books are entities, not scanned folders.

Android and iOS apps

Listen in the Berth mobile app. Phones connect to your server by scanning a QR code from the admin, no URL typing.

Local, S3 or Google Drive storage

Keep files on the server disk or in any S3-compatible bucket — AWS, Cloudflare R2, Backblaze B2, MinIO, Yandex Object Storage — or in Google Drive.

Signed-URL delivery

Audio can be served straight from object storage or a CDN through short-lived signed URLs. The server only authorizes access, so it stays small.

Built-in backups

Before every schema migration Berth backs the database up automatically (last 3 kept). Download, upload and restore backups from Settings → Backup.

JSON API

Versioned JSON API (v1) with an OpenAPI contract for scripting and integrations.

Use cases

Family audiobook library

One server for the household — upload once, everyone listens on their own phone.

Audiobooks in cheap object storage

Keep a large collection in R2 or B2 and run the server on a small VPS — playback goes directly from the bucket.

DRM-free books you own

A private shelf for audiobooks bought DRM-free or produced yourself, with no subscription and no third-party account.

Small ARM boxes

The image is built for amd64 and arm64, so it runs on a Raspberry Pi or an ARM NAS as well as on a VPS.

Code examples

What Pier runs yaml
# Pier auto-generates this — illustrative only
services:
  berth:
    image: ghcr.io/joveptesg/berth:latest
    volumes:
      - berth-data:/data
    # port 8080, published through Traefik on your domain
Find the one-time setup link text
Berth has no default credentials.
Open the service → Logs in the Pier panel and follow the
one-time setup link printed on first start.
Point the phone QR codes at your domain text
Admin → Settings → Internet address:
  https://books.example.com
QR codes shown to listeners will now include this address.

How it compares

vs Audiobookshelf Audiobookshelf scans folders on disk and also covers podcasts and ebooks. Berth is audiobook-only, keeps books as database entities and is built around remote storage (S3, Google Drive) with signed-URL delivery. Pick Audiobookshelf for a folder-based multi-media library, Berth for a lean audiobook server backed by object storage.
vs Audible Audible is SaaS with DRM. Berth hosts files you own on a server you control.
vs Plex / Jellyfin General media servers treat audiobooks like music albums. Berth is purpose-built for listening to books on a phone.

Frequently asked questions

What are the default credentials?
There are none. On first start Berth prints a one-time setup link to its log — open the service logs in Pier and follow it to create the admin.
Which volume do I need to back up?
/data — it holds the SQLite database, automatic backups, local storage and secret.key. Keep an extra copy of secret.key outside the backups; storage keys in the database can't be read without it.
Can I keep /data on NFS or SMB?
No. Berth uses SQLite, which can corrupt over network shares. Keep /data on local disk and put the audio itself in S3 or Google Drive if you need remote storage.
Does it need HTTPS?
Berth serves plain HTTP on port 8080. Attach a domain in Pier and Traefik terminates HTTPS in front of it.
How do I upgrade?
Redeploy the service in Pier — it pulls the newest image. Berth backs the database up to /data/backups before migrating.
How do I roll back?
Restore the pre-update backup from Settings → Backup in the admin (or with berth admin restore).

Related services

Deploy on your VPS

Berth is an open-source audiobook server written in Rust. Upload books through the web admin, store the files on local disk, S3-compatible storage or Google Drive, and listen in the Berth app on Android and iOS — phones connect by scanning a QR code.

Deploy this service →