A few months ago I built a small flight simulator with an LLM in about an hour. It was genuinely fun — but I didn’t have a good place to share it where people could actually play it (not just see a screenshot or clone a repo). Glitch used to be the closest thing to “publish weird little web apps and share a link”, but after hosting went away I couldn’t find a replacement that felt lightweight. CodePen is great for snippets, and Vercel/Netlify/Pages are great for real deploys — I wanted the in-between: publish → share → instantly playable. So I built Vibecodr: a place to publish and share playable web apps (“vibes”). You can write code in the browser or import from GitHub, hit publish, and share a link. Try the flight sim that kicked this off: https://vibecodr.space/player/04ef1473-b0da-4c79-a34f-3ea40f... (fullscreen: https://flight-sim.vxbe.space) How it runs (security-first): user code executes inside a locked-down, cross-origin sandbox iframe (untrusted bundles don’t execute on the vibecodr.space origin). There are runtime budgets/limits to prevent runaways. Backend (“pulses”): if your project needs server-side logic (webhooks, API calls, cron-style tasks), you can add a “pulse” that runs on Cloudflare Workers for Platforms. Pulses are quota’d and rate-limited. One thing I’m experimenting with: a secrets-backed fetch model where pulses can call third-party APIs without the plaintext secret ever being exposed to user code (the platform injects secrets server-side and proxies the request). This is not enterprise hosting — it’s for the “I made a thing, try it” workflow. Free tier: unlimited public frontend vibes; backend pulses are limited (e.g. small number of pulses + monthly run quota). Paid tiers bump limits. Feedback I’d love from HN: What would make you use this instead of your current “share a demo” workflow? Is the Workers-based backend model useful, or would you rather keep backend out entirely? |