Loading…
Everything you need to know about RuneSpoke Hub
Run the app you're building in an isolated sandbox and interact with it in your browser - click through it, hit its API, sign in, test it - before you push, open a PR, or deploy. Verify by using, not just by reading a diff.
The sandbox app is never exposed. Instead, a tiny agent inside it dials outbound to RuneSpoke over HTTPS (the same 443 every website uses), and your browser reaches the app through that connection. There is no inbound port to open - nothing for IT to approve, no firewall changes, no port ranges.
It's the same model as ngrok, Cloudflare Tunnel, and GitHub Codespaces port-forwarding - outbound-only, so it passes corporate proxies.
Paste a repo URL and RuneSpoke reads its package.json to fill in the right command and port - Next.js, Nuxt, Remix, Astro, Vite/SvelteKit, Angular, Create React App, Vue CLI, or plain Node. Private repo? Detection runs again inside the sandbox after clone, so it still gets it right. You can always override by hand.
Navigate, submit forms, sign in, hit your API - it’s the live app.
In-app WebSockets are tunnelled, so HMR and live updates work against a real dev server.
Each preview has its own address - run a few branches side by side and compare.
Finished a Cloud Agent run? Click "Preview this branch"on it to spin up a preview of the agent's work branch, pre-filled. Click through exactly what the agent built - then approve its PR with confidence. Agents build; previews let you verify by using.
Open Preview Environments, paste a repo + branch, and hit start - the running app loads right in the dashboard.