Glitch is discontinuing its web hosting services for user-created apps, effective immediately for new projects and by August 9, 2024 for existing projects. Users are encouraged to migrate their projects to other platforms and are provided with export tools and guides to facilitate this process. This decision was made to focus resources on Glitch's core strength: collaborative web development tools. While project remixing and the in-browser editor will remain, the ability to directly host and share apps via glitch.me URLs will no longer be supported.
Glitch, a platform beloved by many for its simplified web application hosting and collaborative coding environment, has announced the sunsetting of its web hosting services for user projects. This significant alteration to Glitch's functionality will take effect on August 9, 2024. After this date, users will no longer be able to directly host web applications on the Glitch platform. This decision, while undoubtedly impactful for the existing user base, stems from Glitch's strategic refocusing on its core strengths: providing a collaborative browser-based coding environment optimized for rapid prototyping, learning, and experimentation.
While web hosting will be discontinued, Glitch emphasizes that project files will not be deleted. Users will retain access to their code and associated assets. To facilitate the transition for those who rely on Glitch for hosting, the platform will be introducing export options. These options will allow users to download their projects and migrate them to alternative hosting providers. Specific details about these export functionalities will be communicated to users closer to the August 9, 2024 deadline.
Glitch acknowledges that this change represents a departure from their previous offerings and may disrupt existing workflows for many users. The company states that this decision was made after careful consideration and is driven by a desire to concentrate resources on improving the core code editing and collaboration features that distinguish Glitch. They believe this focus will ultimately provide a more refined and enhanced experience for users in the long term, particularly in the realms of educational initiatives and rapid prototyping. The company expresses its gratitude for the community's understanding and support during this transition.
Summary of Comments ( 102 )
https://news.ycombinator.com/item?id=44064230
Hacker News users reacted to Glitch's announcement with disappointment and concern. Many lament the loss of a beloved free-tier platform for quick prototyping and hobby projects, questioning the viability of the new subscription model for small, non-commercial projects. Several commenters expressed skepticism about Glitch's justification for the changes, viewing it as a betrayal of the platform's original ethos. Alternatives like Replit, Fly.io, and self-hosting were suggested, but many felt none truly replicated Glitch's ease of use and beginner-friendly environment. Some also questioned the long-term viability of Glitch under the new pricing model. A few users pointed out the difficulty of migrating existing projects, highlighting potential data loss and workflow disruption.
The Hacker News post titled "We’ll be ending web hosting for your apps on Glitch" (linking to a Glitch blog post announcing the end of their free static site hosting) generated a substantial discussion with a mix of disappointment, understanding, and speculation.
Many commenters expressed sadness and frustration at the loss of a free, easy-to-use platform, particularly for hobby projects, prototypes, and small personal sites. Several highlighted Glitch's unique collaborative and remixing features, lamenting the lack of comparable alternatives. The sentiment that Glitch filled a specific niche and its demise leaves a void in the free hosting landscape is a recurring theme. Some users voiced concern about the migration process and the future of their existing projects.
A few commenters offered alternative hosting suggestions, including Vercel, Netlify, Cloudflare Pages, and GitHub Pages, acknowledging that none perfectly replicate Glitch's distinctive features. Discussions around these alternatives often revolved around their respective learning curves, pricing models, and suitability for different types of projects.
Some commenters, while disappointed, expressed understanding of Glitch's decision from a business perspective, acknowledging the costs associated with maintaining a free hosting service. There was speculation about the potential reasons behind the change, including the possibility that the free tier was being abused or that the company is shifting its focus to more profitable ventures.
A thread emerged discussing the nature of "free" services and the inherent risks involved in relying on them. Commenters debated the trade-offs between convenience and control, with some advocating for self-hosting or paid solutions for long-term projects.
Several comments also focused on the broader implications for the web development ecosystem, with some expressing concern about the increasing centralization of hosting services and the potential loss of creativity and experimentation due to the decline in free, accessible platforms.
Finally, there was some discussion about Glitch's communication regarding the change. Some commenters appreciated the advance notice and the provided migration tools, while others felt the communication could have been more detailed or offered more options for existing users.