← Templates · Applications
LI

LibreChat

Verified

2 services

LibreChat's web/API process and the MongoDB it requires — the one datastore it can't share with Railyard's Postgres/Redis addons.

Deploy LibreChat

Runs2 services
Stack librechatlibrechat-mongo
Provisioned for itNothing, it's self-contained
VerifiedYes, deployed end to end by the Railyard team

Why deploy on Railyard

Railyard provisions all 2 services in this stack together — librechat, librechat-mongo — wired to reach each other over the private network, on a server you already pay for.

Deploying LibreChat is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.

Good to know

  • Registration is open by default (ALLOW_REGISTRATION) — without it LibreChat's own validateRegistration middleware returns 403 on every sign-up attempt and there is no other way to create the first account, since social login is off by default too
  • CREDS_IV must be exactly 16 bytes — LibreChat's AES-CBC credential encryption throws 'algorithm.iv must contain exactly 16 bytes' on any other length, which is why it's generated separately from the other 32-byte secrets here

Project docs ↗