Deploy Openfront Collectibles
Opensource collectibles store based on Next.js and Keystone.js
openfront-collectibles
Just deployed
Just deployed
/var/lib/postgresql/data
Storage
Bucket
Just deployed
Deploy and Host Openfront Collectibles with Railway
Openfront Collectibles is a self-hostable catalog and discovery application for unique physical specimens. Operators can organize inventory, condition, grading, provenance, and listing records, while collectors browse published items and follow merchant-owned detail handoffs. Collectible checkout, bidding, offers, payouts, and settlement are not launch-ready.
About Hosting Openfront Collectibles
This template provisions the application from its GitHub repository, PostgreSQL, and a private native Railway Bucket named Storage. The database starts empty; no demo records or reusable credentials are included. Initialize the application using the repository's onboarding instructions after deployment.
DATABASE_URL references Postgres and the five S3_* variables reference the Storage bucket. Generated per deployment: SESSION_SECRET.
The app gets a Railway-generated public domain. No custom domains are included.
Admin Dashboard
Manage collectible commerce, gift cards, regions, currencies, collectors, products, product categories, evidence, price lists, invoices, catalog, discounts through dedicated dashboard workspaces and permission-controlled data screens.
Storefront
Country-scoped storefront pages expose catalog browsing and collectible handoffs at /[countryCode]/collectibles/handoff/[listingId]. Public observation projections preserve evidence sources and review states rather than presenting provenance or grading as a software guarantee.
Catalog & Specimens
Separate catalog definitions from individual specimens, identifiers, custody, inventory units, locations, condition observations, and media.
Grading & Provenance Evidence
Maintain grading-company references, reported grades, certificate references, provenance events, and valuation observations with source and confidence information.
Listing Preparation & Discovery
Prepare specimens, manage collectible listing records, and publish read-only discovery projections. Auction, consignment, buylist, and offer records are not evidence of completed money movement or active bidding.
Common Use Cases
- Catalog & Specimens
- Grading & Provenance Evidence
- Listing Preparation & Discovery
Dependencies for Openfront Collectibles Hosting
The app needs a PostgreSQL database and S3-compatible object storage. Both are provisioned by this template.
Deployment Dependencies
Implementation Details
Next.js and Keystone 6 with a GraphQL API, Prisma, and PostgreSQL. Payments, email, and other external providers need their own operator configuration; this template does not activate them.
Why Deploy Openfront Collectibles on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Openfront Collectibles on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
openfront-collectibles
openshiporg/openfront-collectiblesStorage
Bucket