Set up a complete, production-grade CitrineOS infrastructure on Railway following the architecture described in the official docs at:

https://citrineos.github.io/latest/

For more info, CitrineOS has YouTube videos on local installs. I have been able to get this running locally, but want to have a cloud version within Railway to begin production development. CitrineOS also has an active Discord server for developer questions.

The following is based on my interpretation of the recommended architecture. Follow the docs and each CitrineOS repo’s README as the source of truth.

Requirements

Deploy and integrate the following:

• CitrineOS Core
  Repo + docs: https://github.com/citrineos/citrineos-core

• Public gateway for Core HTTP + OCPP WebSocket

• Everest OCPP server for testing/simulation
  Repo + docs: https://github.com/EVerest/everest

• OCPI service
  Repo + docs: https://github.com/citrineos/citrineos-ocpi

• Payments service
  Repo + docs: https://github.com/citrineos/citrineos-payment

• Operator UI
  Repo + docs: https://github.com/citrineos/citrineos-operator-ui

• PostgreSQL - timescaledb

• RabbitMQ with persistent volume and secure credentials

• Redis

• Hasura GraphQL Engine
  Docs: https://hasura.io/docs

• Directus with persistent uploads
  Docs: https://docs.directus.io

Use private networking where appropriate, pin container versions (avoid using latest), and follow security and scaling best practices recommended in the CitrineOS documentation.

Extensions Service (Required)

Create a separate service where custom logic lives outside of Core, including a minimal working example demonstrating:

• consuming messages/events (e.g., from RabbitMQ), and/or

• making calls to Core APIs

Document where extensions should be placed and how they are deployed without modifying CitrineOS Core.

Acceptance Criteria

• All services deployed and healthy

• Public endpoints reachable via domains

• Core, database, cache, and broker remain private

• OCPI, Payments, Hasura, Directus, Everest verified working

• No modifications to CitrineOS Core source

• README covering architecture overview, env vars, deployment steps, and how to extend the platform safely

Constraints

• Infrastructure and platform setup only

• No product feature or UI work beyond basic verification