Deploy and Host Kellojo Asset Library on Railway

A private asset library with tags, uploads and persistent SQLite.

Draft status: Configuration and upstream documentation reviewed. Container startup, Railway application workflows, restart behavior, backup restoration and costs remain unverified.

About Hosting

A private asset library with tags, uploads and persistent SQLite.

Service	Role	Persistent path
`core`	Private application or dependency	`/app/data`
`asset-library`	Public owner gateway	`None`

Why Deploy

Run this application in your own Railway project, with explicit configuration and storage under your control.

Common Use Cases

Personal design assets
Private media library

Dependencies for Kellojo Asset Library

Deployment Dependencies

The application images are pinned by registry digest. Database services, when included, stay on the private network. One replica is supported for each volume-backed service.

First use

Open the asset-library service's HTTPS domain. Sign in to the owner gateway with username admin and its generated ACCESS_PASSWORD. Complete the application's own setup afterward.

API calls must also send X-Template-Key with that owner password. The gateway forwards native Bearer tokens, strips Basic Authorization, and limits requests to 32 MiB. Browser sessions receive a secure owner cookie. Native clients, webhooks and public sharing require specific compatibility checks before use. Gateway /healthz only checks the proxy, not application readiness.

Use the owner gateway, upload a small asset and add tags.

Scope and limitations

No native authentication; keep full owner gateway enabled.
Gateway requests are limited to32MiB. AI tagging is optional and no external model key is included.
The rolling upstream image is frozen by digest.

Acceptance checks before use

Verify anonymous requests cannot view/download assets.
Upload, tag, filter and download an asset; restart and confirm persistence.
Confirm generated credentials are distinct on a second fresh deployment.
Back up every listed persistent path and database, then restore into a separate test project.
Measure Railway usage with representative data and workload before estimating operating costs.

Backups and upgrades

Back up databases, file volumes, encryption keys and configuration together. Keep a copy outside the running project. Review upstream migration notes before changing a digest; rollback can require restoring a compatible database and files, not just selecting an older image.

Sources and selection evidence

Upstream documentation: Official GHCR image, /app/data SQLite and uploads, origin and upload settings.
Upstream documentation: Production image listens on3000.
Upstream project

Product and alias searches found no matching public Railway listing during this research. This is a bounded search result; private, unindexed or differently named listings may exist. It is not evidence of demand or revenue.

Upstream software retains its own license and edition restrictions. This deployment draft does not imply upstream endorsement.