Every integration below maps to a drag-and-drop canvas node. Pick the ones your stack uses — mobile, web, backend, cross-platform. RailRun doesn't care which, your runbook decides.
Pick a stack tab — the canvas palette, starter templates, and verification runners reshape to what your team actually uses.
Start a Run Task by picking a ticket from a connected source. Recent tickets are pre-loaded. Search across projects. Or enter a ticket manually with AI-enhanced descriptions.
RailRun is an MCP server. Your engineers keep the agent they already use — Claude Code or Cursor. Paste one RailRun key into their mcp.json and every template is available from day one. The agent calls its own LLM with its own key — RailRun never sees the model, the key, or your source code.
mcp.json.mcp.json.Testing (CI) and Distribution (CD) are separate phases with distinct node types. Run tests locally or trigger remote pipelines. Deploy to any app distribution channel.
Extract design tokens from Figma. Create PRs on GitHub or GitLab. Post summaries back to tickets. Notify the team on Slack.