Glitch, the carefree space where developers could instantly spin up and remix web apps, is losing its magic trick: free hosting. In a blog post published May 22, 2025, CEO Anil Dash revealed that as of July 8, 2025, Glitch will stop hosting projects and shut down user profiles—though it won’t disappear entirely…yet.

Since its 2017 debut under Fog Creek Software, Glitch has been the digital equivalent of a magic sandbox: code in the browser, click “remix,” and voilà—a shareable, live app. It grew to 1.8 million monthly users before Fastly swooped in to acquire it in May 2022, promising to bolster its edge-cloud chops. Yet hosting small apps at scale, Dash explained, has become prohibitively expensive—and increasingly prone to abuse by bad actors.

Still, Glitch isn’t packing up shop completely. Users will retain dashboard access and can download their code through December 31, 2025. A forthcoming redirect feature will let you point your old project URLs elsewhere, a small grace period to migrate your digital babies. Pro subscriptions are also on hold: no new sign-ups, but existing members can bask in Pro until the July cutoff.

Dash credits two culprits: rising hosting costs and platform misuse. Edge hosting—Fastly’s bread and butter—helps here, but Glitch’s model of “always-on,” containerized development environments is inherently resource-heavy. Multiply that by millions of projects, and the tab spikes. On top of that, “bad actors try to misuse the platform,” creating spammy or malicious apps that drive up support and security overhead.

The turning point appears to be a fiscal squeeze at Fastly. Over the past year, the company has been under pressure to streamline operations and focus on profitability, even as its core CDN business grapples with stiff competition. It’s not that Fastly lacks faith in Glitch’s community—it’s more that Glitch’s overhead no longer aligns with Fastly’s bottom-line goals.

Beyond hosting and profiles, details are sparse. Dash told The Verge that, post-July, the only guaranteed features are dashboard access, redirect URLs, and code downloads; “anything else…would come in a future update,” he said. That leaves open questions about comments, community galleries, and collaboration tools that many glitched pioneers relied on.

Glitch’s leadership insists the story isn’t over. Dash and his small team are “still figuring out what plans might be possible for Glitch and its community going forward.” Some insiders speculate on a pivot toward a paid, enterprise-grade development environment—leveraging Fastly’s edge network to offer low-latency previews and hardened security.

What developers should do now?

1. Export your work: Log in and download ZIPs of all your projects before the end of 2025.
2. Set up redirects: Once the redirect tool launches, point your old *.glitch.me URLs to new homes.
3. Evaluate alternatives: Platforms like Replit, Netlify, Vercel, and Fly.io offer free tiers and seamless git integration.
4. Preserve collaboration: If you use Glitch for teams, consider migrating to GitHub Organizations or GitLab groups for version control and code review.

Glitch’s imminent hosting shutdown marks a bittersweet milestone for a platform that democratized web development with a single click. While the community may survive in forks and alternative hosts, the end of Glitch as we know it reminds us of the delicate balance between free-wheeling creativity and the realities of cloud infrastructure economics. As Dash and Fastly weigh the next chapter, developers everywhere are dusting off migrations plans—and savoring the last lines of code living, remixed, on Glitch’s servers.