{"slug": "show-hn-railcode-secure-cloud-for-internal-software", "title": "Show HN: Railcode – Secure cloud for internal software", "summary": "Yakko launched Railcode, a secure internal deployment platform for company software, on Hacker News' Show HN. Railcode places company authentication in front of every deployed project, replaces shared API keys with permissioned data connectors, and adds centralized audit logs and role-based access control, addressing the sprawl that occurs when employees build tools with Claude Code or Codex and deploy them to services like Vercel. The platform supports static frontends and serverless JavaScript functions, including Tanstack, Hono, Vite, React, and Next.js via OpenNext, and ships a skill and CLI for agents to manage configuration.", "body_md": "Hey HN, Yakko here from Railcode.\n\nRailcode is like an internal Vercel for your company.\n\nWe built it after speaking to dozens of engineering leaders at various companies where employees were given access to Claude Code or Codex and started to build little tools (apps, agents) locally, but then struggled to share it with coworkers securely.\n\nTypical scenarios are:\n\n1. Employees can't share what they've built because of internal policies\n\n2. Agents find the path of least resistance and deploy things on e.g. Vercel, leading to a sprawl of software that's a nightmare to manage (disjointed auth or no auth, API keys handled insecurely, no centralized management, etc.)\n\n3. Companies set up templates to ensure some standardization but still require engineers in the loop to review and deploy code\n\nNeither of these options felt great, so we built Railcode to be the place to deploy and manage internal software inside a company, ensuring projects are deployed securely, follow the same patterns, and can be easily managed from one place.\n\nThe goal is to unblock users to deploy and share what they've built while removing the burden on Engineering/DevOps to review and manage it all.\n\nHow we do this:\n\n- Company auth in front of everything that's deployed\n\n- Permissioned connectors to access data instead of shared API keys\n\n- Infrastructure building blocks that make it easy to store data or use an LLM but allows admins to oversee everything (via a simple SDK)\n\n- Centralized audit logs\n\n- Unified design system (optional)\n\n- Role-based access control with granular permissions that can be inherited by the projects themselves\n\nThe platform is built to be really low friction for agents and to not require folks changing their workflows. We support static frontends and serverless JS functions for the backend, meaning Tanstack, Hono, Vite, React, etc will all work. Even Next.js with OpenNext though that has some quirks :D\n\nProjects run locally and everything Railcode-specific comes from an optional SDK. We ship a skill and a CLI and that's all you need to build and deploy projects or have agents manage configuration.\n\nKeen to hear feedback!\n\nComments URL: [https://news.ycombinator.com/item?id=49999322](https://news.ycombinator.com/item?id=49999322)\n\nPoints: 1\n\n# Comments: 0", "url": "https://wpnews.pro/news/show-hn-railcode-secure-cloud-for-internal-software", "canonical_source": "https://railcode.dev/", "published_at": "2026-10-07 21:55:52+00:00", "updated_at": "2026-10-07 22:19:34.261017+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "ai-products"], "entities": ["Railcode", "Yakko", "Claude Code", "Codex", "Vercel", "Hacker News", "Tanstack", "Next.js"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/show-hn-railcode-secure-cloud-for-internal-software", "markdown": "https://wpnews.pro/news/show-hn-railcode-secure-cloud-for-internal-software.md", "text": "https://wpnews.pro/news/show-hn-railcode-secure-cloud-for-internal-software.txt", "jsonld": "https://wpnews.pro/news/show-hn-railcode-secure-cloud-for-internal-software.jsonld"}}