Migration guide / verified shutdown timeline

Hosting ended July 8, 2025. Redirects were intended through end of 2026.

Rebuild the part people can run, then move backend work into explicit Pulses.

Vibecodr keeps the part people actually miss: small web apps you can publish, open, remix, and embed. Rebuild the browser UI in Studio, publish it on vibecodr.space, and move backend work into Pulses only where the project truly needs server trust.

Start in Studio See how it works View plans

Not affiliated with Glitch or Fastly. Timeline based on the publicly announced shutdown details available as of March 7, 2026.

How the rebuild works

Rebuild in Studio, publish a vibe on vibecodr.space, and split backend work into Pulses when the old app depended on a backend.

The fastest recovery path is usually to restore the runnable interface first, then decide which backend capabilities belong together in one or more Pulses and which should stay in another system you control.

UI first Get a live runnable replacement online before you untangle every server dependency.

Pulse split Secrets, OAuth, storage, and scheduled work become explicit backend edges.

Share loop People can still run the project from a link instead of arriving at a legacy Glitch URL that no longer behaves like the original app.

Studio

Rebuild the interface first, while it is still visible and testable.

Move the front-end into Studio, preview it live, and ship a working public version before you untangle every backend dependency.

Vibes

Publish a runnable replacement instead of a static migration note.

The new public page can actually run, remix, and embed instead of only pointing people back to an archived Glitch project.

Pulses

Secrets, APIs, cron jobs, and storage become explicit backend edges.

Backend capability stops hiding inside one full-stack Glitch container and becomes easier to understand, secure, and scale.

Continuity

Keep the remix-and-share loop that made Glitch fun in the first place.

Vibecodr preserves the fast loop: build something small, publish it, BUMP IT as it improves, let people run it, and let the next person remix from there.

What changed

The old recovery window closed, but the project itself can still come back to life.

These dates matter because migration advice changes once the original host is no longer a reliable place to depend on for code, assets, or runtime behavior.

July 8, 2025

Glitch project hosting and profiles ended.

That was the hard cutoff for the original hosted-product experience.

December 31, 2025

The published dashboard and download recovery window ended.

As of March 2026, it is safer to plan from your own exports and backups rather than count on Glitch as the recovery path for code you did not already save.

Through end of 2026

Previously configured project redirects were intended to remain active.

Redirect continuity helps with legacy links, but it does not restore hosting, editing, or project runtime.

Pick the rebuild path

The right replacement depends on what kind of Glitch app you had.

Some Glitch apps were mostly front end. Some leaned on secrets and APIs. Some were really long-lived Node servers. The recovery path is different for each.

Static or mostly static

HTML, CSS, JS, canvas toys, landing pages, demos

Port these straight into a vibe. This is the fastest win and gets your public URL back online with minimal translation work.

Frontend plus APIs

Fetch calls, third-party APIs, auth flows, rate-limited tools

Keep the browser UI in a vibe and move anything that needs secrets or server trust into Pulses.

Server-heavy app

Express routes, background jobs, webhook handlers, stateful logic

Use Vibecodr for the runnable front-end and edge-friendly server slices. If you still need a long-lived Node process, keep that backend separate and call it from the vibe.

What stays and what changes

Keep the fast publishing spirit. Trade the blurry runtime boundary for a clearer one.

Vibecodr is not trying to recreate the old Glitch hosting model one-to-one. It is trying to keep the part people loved while being much clearer about what runs in the browser, what runs at the edge, and where secrets belong.

What feels familiar

Small runnable projects, remix culture, and shareable links stay intact.

The core loop still rewards speed and iteration: make something interesting, publish it, and let the next person fork the idea.

What changes

The runtime boundary is clearer and safer than the old one-box model.

Client code runs in a safe browser environment. Backend work lives in Pulses. That split is deliberate, and it keeps private capability away from the part people openly share.

What gets stronger

Public pages, embeds, and premium vxbe.space links extend the same work.

You can keep the same vibe on vibecodr.space, BUMP IT future versions onto that same app, embed it elsewhere, or point a premium link at it without inventing a second product surface.

Where to go next

Follow the rebuild through the parts of the product you would actually use.

If you are seriously comparing Glitch replacements, the real question is not just “can it host a page?” It is “where do I rebuild, publish, extend, and share this thing now?”

Rebuild Rebuild in Studio Move the browser UI into Studio, preview it live, and publish from the same place. Add backend Pulses Handle secrets, APIs, cron jobs, AI calls, and server-side logic at the edge. Learn the model How it works See how vibes, Pulses, BUMP IT, embeds, cuts, and public pages fit together. Infrastructure Edge backend guide Understand the runtime model behind the backend boundary. Capability map Power of Pulses Compare what should stay client-side versus what belongs behind a Pulse. Broader framing Social Runtime See the wider product story around runnable posts, embeds, and remixable distribution.

FAQ

Common migration questions

These answers are written for people trying to recover real projects and decide how to rebuild them.

Did Glitch hosting really end?

Yes. Glitch announced that project hosting and user profiles ended on July 8, 2025. Their published shutdown plan said dashboard access and code downloads would remain available through December 31, 2025.

Do old Glitch links still redirect?

Glitch said project redirects configured before shutdown were intended to stay active through the end of 2026. That helps with stale links, but it is not the same as keeping an app live or editable.

Can Vibecodr replace a Glitch project?

Usually yes, especially if the part people care about most is still the interactive front end. Put the UI into a vibe, then move secrets, APIs, or scheduled jobs into one or more Pulses where they make sense.

Does Vibecodr run Node or Express directly?

No. Vibecodr is browser-first. Vibes run client-side in a safe browser environment, and Pulses run server-side on Vibecodr's edge backend when you need trusted backend capability.

What if my old Glitch app mixed frontend and backend together?

Start by moving the UI into Studio so the app is runnable again. Then decide which backend pieces belong together in a Pulse and which should stay in another system you control, depending on how stateful the original app was.