Glitch made coding feel like play. Who paid for the playground?

Steve Anderson needed a barcode generator. The service his company depended on was failing, so he built a replacement prototype on Glitch. He later told the company he “had it up and running in an hour or so.” He moved it to a work server. Then a data-center problem interrupted his clients’ invoice and delivery-note printing. The prototype, still on Glitch, became the temporary fallback.

It is an unglamorous little story, which is precisely its charm. No grand platform strategy, no committee convened to discuss transformation. Someone needed a thing. He made the thing. Glitch shortened the distance between those two sentences.

A working app beats a blank page

Glitch came from Fog Creek Software, founded in 2000 by Joel Spolsky and Michael Pryor. That business had a habit of producing tools developers actually used: FogBugz, Kiln, and Trello belonged to its history. The project that became Glitch emerged from Creek Week, an internal hackathon. A company accustomed to organizing work began asking why starting work required so much ceremony.

In May 2016, Spolsky introduced the public beta as HyperDev. Visit the site and a website was already running, with a URL you could share. Edit the page and the change appeared online. Modify the Node.js server and the platform handled restarting it. Invited collaborators could edit together. The tedious preliminaries had been bundled into the service.

This was real code: HTML, CSS, JavaScript, and server-side Node.js. Its accessibility came from taking infrastructure decisions off the beginner’s desk. A newcomer could alter something visible before learning deployment vocabulary. An experienced developer could test a modest idea without spending the afternoon preparing its accommodation.

“The default state of a project should be a functional, running app or site or bot”

Glitch’s social-coding argument, 2018

The names changed from HyperDev to Gomix to Glitch. In 2017, Slack helped the team reuse the name of its earlier online game. There is a pleasing circularity here: a workplace software company donated a game’s name to a developer tool that wanted work to feel more playful.

The classroom had a remix button

Remixing made this more than an online editor. A working project could become the beginning of another project. That changed the social unit of learning: an example was something you could inhabit, alter, and pass along. GitHub organized repositories; Glitch emphasized the running result and the invitation to change it.

Educators and developer advocates found practical uses. Glitch announced collaborations with Slack’s live-coding sessions, the youth nonprofit Mouse, and freeCodeCamp’s curriculum. Its 2021 survey of organizational uses included Slack workshop materials and Bolt examples, alongside Postman API training resources. These were occasions when getting everyone to the same starting line mattered.

The audience also included artists, students, and people making peculiar little amusements. Virtual-reality experiments sat beside utility apps. Glitch In Bio, launched in 2021, offered a customizable link page built from ordinary web code. The platform’s expertise lay in joining editor, deployment, examples, and community closely enough that the seams became less distracting.

The free playground acquires a price tag

In September 2018, Fog Creek renamed itself Glitch, Inc. The experiment had become the company’s organizing purpose. Its public employee handbook and emphasis on inclusion expressed an ambition that reached beyond shipping an editor: the company wanted the people making the web to feel welcome there.

After nearly twenty years of bootstrapping, it took institutional capital. A $30 million Series A from Tiger Global closed in November 2018 and was announced in July 2019. The company said it delayed the announcement to show what the investment had enabled. Financing arrived with a familiar obligation: a generous community still needed a durable business.

A paid tier launched in April 2020 at $10 a month or $96 annually. Free users could create; paying users could boost apps with additional resources and keep them running continuously. The offer sold relief from operating limits. Anderson’s barcode prototype illustrated why that relief could matter after an experiment became useful.

Fastly acquired Glitch in May 2022 for $34.9 million in cash. Its announcement described a community exceeding 1.8 million developers. The fit was understandable: Glitch helped people get started, while Fastly supplied infrastructure for delivering applications. Later tutorials used remixable Glitch projects to introduce developers to Fastly services.

The machinery interrupts the magic

The machinery had already announced itself. On November 4, 2019, a release broke Glitch’s API servers, producing a roughly seven-hour outage. Reverting the code did not restore service. Aggressive proxy retries kept the servers overloaded; a suspected crash loop complicated recovery. A fresh proxy fleet helped traffic resume. The team subsequently revised its incident process and identified observability gaps.

The lesson is uncomfortable for any product promising instant results. Work removed from the user has to be performed somewhere. Collaboration and automatic deployment depend on systems that must recover when they fail. A delightful first minute cannot settle the engineering bill for every minute afterward.

In May 2025, Anil Dash announced the end of project hosting and profiles on July 8. He cited growing maintenance costs and misuse, alongside alternatives that had improved app creation and hosting. The company judged its older architecture less distinctive. Exports and redirects became the transition tools; the team published its farewell that July.

A lesson you can take elsewhere

Glitch’s design lesson remains copyable: begin with a working example, let people make a small change, and make sharing easy. For classrooms, workshops, and prototypes, that sequence gives curiosity something concrete to hold. Its business lesson is harder: budget for the infrastructure and support that easy entry attracts.

The approach fits less comfortably where strict release controls, extensive language support, or dependable production operations dominate. Spolsky’s original introduction acknowledged the limits of continuously deploying edits. Today, builders need another host. Glitch leaves a useful question for its successors: how much administrative work can you remove before the person with the idea loses interest?