Deploy and Host COREY on Railway

COREY helps project teams review, validate, and edit IFC model data in a browser-based 3D workflow. This template also includes the COREY MCP companion so approved AI clients can inspect model data through the authenticated MCP endpoint.

About Hosting COREY

This template provisions a connected five-service stack:

COREY — the web application, pinned to ghcr.io/jhjhjhjh/corey:0.1.0.
MCP — the Streamable HTTP and browser-bridge companion, pinned to ghcr.io/jhjhjhjh/corey-mcp:0.1.0.
Postgres — model metadata, validation rules, drafts, and MCP settings.
MinIO Bucket — S3-compatible storage for server-backed IFC model files.
MinIO Console — browser administration for the object store.

Railway generates the MCP bridge secret during deployment and wires it between COREY and MCP through reference variables. Both application images are public GHCR images; no GitHub repository deployment is required.

Common Use Cases

Validate IFC model data before CORENET X or IFC-SG submission.
Review models with the 3D viewer, spatial tree, property inspection, and rule-based validation.
Export IFC data to Excel, batch-correct repeated property issues, import corrections, and validate again.
Let authenticated MCP clients inspect projects and model data through COREY.

Dependencies for COREY Hosting

PostgreSQL for application and MCP settings data.
MinIO for server-backed IFC model storage.
Public domains for the COREY app and MCP endpoint.
Private Railway networking between COREY, MCP, PostgreSQL, and MinIO.
A generated 64-character bridge secret shared through a reference variable.

Deployment Dependencies

COREY listens on port 4000 and uses healthcheck /api/health.
MCP listens on port 4001 and uses healthcheck /health.
The browser bridge uses the MCP public WebSocket endpoint and restricts browser origins to the generated COREY domain.
Image versions are intentionally pinned. Future releases require an explicit template update.
COREY source
COREY documentation
Deployment guide

After Deployment

Open the generated COREY public domain and confirm /api/health is healthy.
In COREY, select MCP to open MCP access.
Enable deployment access.
Generate an API key and copy it immediately; it is only shown once.
Copy the Streamable HTTP endpoint and the provided Codex or Claude configuration.

The MCP service exposes /mcp for authenticated clients. MCP access can remain disabled until it is needed.

Why Deploy COREY on Railway?

Railway provisions the application, MCP companion, database, and object storage as one connected stack with generated domains, private networking, health checks, and reference variables.