Deployment · HealthClaw

Where HealthClaw runs

Where HealthClaw runs Production is one Railway project: the engine at app.healthclaw.io, the token-locked MCP server and its open demo twin on a separate host, the CareAgents web and worker at careagents.cloud (build stamped in /healthz and equal to main on 2026-09-05), and two Postgres databases, one per app, so the no-PHI app never shares the engine's store. Smart Health Links also runs there and is omitted. The home gateway reaches the MCP server with a bearer token (verified 2026-07-30). CareAgents calls the engine through Railway's internal hostname, not the public one. The iMessage relay is staged, not live (2026-07-16). A legacy VPS at 187.77.4.50 still answers nginx but serves nothing in production, and a Vercel copy of the site exists for demos; neither is drawn. Seven nodes is one over the type's budget, kept so both databases show. HOME LAN RAILWAY · PRODUCTION HTTPS BEARER RELAY STAGED INTERNAL HOST HTTPS 5432 5432 MAC Mac mini · home openclaw gateway :18789 ollama :11434 WEB app.healthclaw.io flask + site v1.10.0 MCP mcp-server agent-orchestrator LOCKED MCP mcp-demo orchestrator OPEN · SYNTH APP careagents.cloud web build = main worker railway up MANAGED postgres · engine railway postgres managed MANAGED postgres · careagents railway postgres managed LEGEND Locked MCP (focal) Service Managed store Self-hosted host Bearer call Staged, not live In-zone call

Production is one Railway project: the engine at app.healthclaw.io, the token-locked MCP server and its open demo twin on a separate host, the CareAgents web and worker at careagents.cloud (build stamped in /healthz and equal to main on 2026-09-05), and two Postgres databases, one per app, so the no-PHI app never shares the engine's store. Smart Health Links also runs there and is omitted. The home gateway reaches the MCP server with a bearer token (verified 2026-07-30). CareAgents calls the engine through Railway's internal hostname, not the public one. The iMessage relay is staged, not live (2026-07-16). A legacy VPS at 187.77.4.50 still answers nginx but serves nothing in production, and a Vercel copy of the site exists for demos; neither is drawn. Seven nodes is one over the type's budget, kept so both databases show.