Before You Build
Web AppShut Down

Glitch Developer Platform

Glitch was a browser-based developer platform for creating, remixing, and hosting web apps. Its 2025 hosting shutdown shows how loved developer tools can become fragile when hosted runtime, free usage, and owner strategy no longer line up.

View original story

Product snapshot

What it was

Glitch let people build, remix, publish, and share web apps directly in the browser.

Who it was for

individual developersbeginner web developerseducators and workshop leaderscommunity builderssmall teams building prototypes, bots, tools, and lightweight sites

Problem / value

It reduced setup friction by bundling an online editor, hosted project URLs, remixable examples, and community discovery.

Core workflow

Create or remix a project in the browser, publish it to a hosted URL, share it through a profile or community surface, and optionally use paid features for more capability.

Core dependency

The model depended on sustainable hosting economics, paid durability, owner commitment, and practical migration paths.

Product form

browser IDE and project editorhosted web app projects and public project URLsremixable templates and examplesuser profiles and community discoverypaid Glitch Pro subscription before cancellation

Pricing model

Glitch offered a free creation and hosting experience and later a paid Pro subscription. Public sources confirm new Pro subscriptions stopped and active subscriptions were canceled, but do not disclose revenue, paid subscriber count, gross margin, or hosting cost.

Competitors or alternatives

ReplitCodeSandboxGitHub PagesNetlifyVerceldirect cloud hostingfree static hosting

What happened

Summary

Glitch ended hosted projects and user profiles after years as a low-friction browser-based coding and hosting platform.

Outcome

Hosted projects and user profiles were discontinued, while users were directed toward export, download, and alternate hosting paths.

Core risk

Hosted developer platform lost runtime sustainability.

Timeline

  • Glitch became known as a creator community for browser-based app development and hosting.
  • Fastly acquired Glitch in 2022 and described the community as more than 1.8 million developers.
  • Glitch announced in 2025 that hosted projects and user profiles would end on July 8, 2025.
  • Glitch stopped accepting new Pro subscriptions and canceled active subscriptions around the hosting shutdown.

Before you build

Why it matters

Developer platforms can earn love and usage while still carrying expensive hosting obligations, weak paid conversion, migration risk, and owner-strategy dependency.

Primary check

Before building a hosted developer platform, prove users will pay for durability, model infrastructure cost, and give builders export and migration paths before public projects depend on you.

Checklist

  • What does each hosted project cost when idle and active?
  • Which users will pay for durability rather than convenience?
  • Can users move projects without breaking public identity?
  • What happens if the owner or strategy changes?
  • Model hosting cost by active project, not only by registered user.
  • Measure paid conversion for durability and production reliability.
  • Create export and migration paths before shutdown pressure appears.
  • Avoid making user identity depend only on platform-owned URLs.
  • Communicate which promises survive ownership or strategy changes.

Relevant if

  • You are building a hosted tool, browser IDE, AI demo platform, template gallery, coding community, or free developer utility.
  • Users publish public projects or profiles on your infrastructure.
  • Your free tier creates ongoing runtime or storage costs.

Less relevant if

  • Your product is local-only or export-first and does not host user projects.
  • You already have clear paid durability economics and migration commitments.

Pre-build tests

  • Run a paid durability tier before scaling free hosting.
  • Measure migration success in a small cohort before any hosting cutoff.
  • Test whether teams pay for reliability, privacy, or collaboration rather than only free prototypes.

Transferable lessons

  • Do not make free hosting the main promise unless unit economics are visible and stress-tested.
  • Separate creation value from deployment guarantees so users can keep working if hosting changes.
  • Offer export, custom domains, and migration paths before users build public identity on your platform.
  • Test whether users pay for durability, collaboration, privacy, or production reliability, not only convenience.
  • If a larger platform acquires your tool, communicate early which user promises remain durable.