Miss Glitch?
Vibecodr is the remix-and-share playground, rebuilt.
If you loved the loop of making tiny web apps, remixing them, and sharing a link that actually runs, Vibecodr is designed for that: a social feed of playable vibes that execute client-side, plus Pulses when you need server-side capabilities.
Not affiliated with Glitch or Fastly. Glitch is a trademark of its respective owners.
What happened
The Glitch timeline
July 8, 2025
Glitch ended project hosting and profiles.
End of 2025
Dashboards and code downloads were previously available. It is now February 2026.
Through end of 2026
Glitch project subdomain redirects intended to remain active.
Now
glitch.me redirects to glitch.com during shutdown messaging.
How it works
What Vibecodr is (in one minute)
01. Vibes
A vibe is a small, runnable web experience you publish and share. People don't just see a repo — they click and it runs. Vibes execute client-side inside a sandboxed iframe.
02. Pulses
When you need backend power — secrets, OAuth connections, storage, automation triggers — you add a Pulse: a server-side function running on Cloudflare Workers for Platforms.
Share a link that runs
Playable posts, not screenshots. Great for demos, portfolios, and teaching.
Remix what you find
Remix is first-class: lineage matters and publishing creates immutable artifacts.
Embed anywhere
Dedicated embed surfaces with sandbox isolation and origin policy controls.
Comparison
Glitch vs Vibecodr: what maps cleanly, what's different
Feels similar
- Remix culture: browse, fork, publish
- Small projects you can share quickly
- Community discovery loop (feed + profiles)
Intentionally different
- Vibes are client-side runnable (sandboxed iframe), not a hosted Node server
- Backend via Pulses (Workers runtime), with quotas and safer secret handling
- Embedding is a first-class surface (oEmbed + origin policies)
Migration
Pick your migration path
Client-only project
If your Glitch project was mostly HTML/CSS/JS, migrate it into a vibe and publish it as a runnable link.
API keys needed
Move keys into Pulse secrets and call your Pulse from the vibe when you need privileged work.
Express app
Convert backend routes into Pulses. Keep your UI as a vibe and call your Pulse endpoints.
Safety
Why Vibecodr is safer (without killing the fun)
Sandboxed by default
Vibes run in sandboxed iframes, isolated from Vibecodr's cookies and storage.
Privileged work is explicit
Pulses are the boundary for secrets and server-side execution — with quotas, rate limits, and telemetry.
Plans
Plans snapshot
Free
$0
1 GB storage
10 MB bundle limit
3 Pulses
Creator
$9/mo
5 GB storage
50 MB bundle limit
15 Pulses
Pro
$39/mo
25 GB storage
100 MB bundle limit
50 Pulses + D1
FAQ
Common questions
Is Glitch shut down?
Glitch ended project hosting and profiles on July 8, 2025. If you still have old Glitch URLs, some project subdomain redirects were intended to stay active through the end of 2026.
Why does glitch.me go to glitch.com now?
During the shutdown transition, glitch.me redirected to glitch.com. If you were using a project subdomain, you may be hitting a redirect rather than an actively hosted app.
Can I still download my Glitch projects?
Glitch indicated dashboards and code downloads were available through the end of 2025. It is now February 2026, so you should assume downloads may no longer be available unless Glitch announces otherwise.
Does Vibecodr run backend code like Express?
Vibes run client-side in a sandboxed iframe. When you need backend capabilities (secrets, OAuth, storage, automations), you add a Pulse: a server-side function running on Cloudflare Workers for Platforms.
Can I keep my Vibecodr work private or unlisted?
Yes. Vibecodr supports public sharing plus private/unlisted visibility modes depending on your plan and feature gates.
What is the simplest way to migrate from Glitch?
If your project was mostly HTML/CSS/JS, migrate it into a Vibecodr vibe (runs in-browser). If you had a server, move the server endpoints into Pulses and call them from the vibe.