What problem does it solve? Railway-hosted services expose public .up.railway.app URLs by default, leaving internal tools unprotected. This Skill guides the migration of those services behind Cloudflare Access zero-trust authentication using Cloudflare Tunnels, private Railway networking, and per-project cloudflared connectors. ## Core Features & Use Cases - Tunnel and Connector Setup: Create Cloudflare Tunnels per Railway project, deploy cloudflared connector services, and configure tunnel ingress routing to private railway.internal origins. - Access App and DNS Configuration: Create Cloudflare Access applications with reusable SSO policies, proxied CNAME records, and path-based bypass rules for webhooks and OAuth callbacks. - Gating Strategies: Choose between gating the root domain with webhook bypasses or gating only UI paths for API-heavy services like LiteLLM, plus service tokens for machine-to-machine access. - Use Case: Move an internal N8N instance from n8n.up.railway.app to n8n.example.xyz gated behind Cloudflare Access SSO, while keeping /webhook paths open for external integrations. ## Quick Start Ask the AI to gate a Railway service behind Cloudflare Access by creating a tunnel, deploying cloudflared, and configuring the Access app, DNS, and ingress rules.