Holy Unblocker vs Scramjet: What’s the Difference?
HUHoly Unblocker What It IsHow It WorksFeaturesSupported SitesDownloadGuideFAQ Get it on GitHub Home / Guide / Holy Unblocker vs Scramjet GUIDE · TECHNOLOGY EXPLAINED Holy Unblocker vs Scramjet: What’s the Difference? They look like competing proxies, but they sit at different levels. One is a platform, the other is an engine inside it. Updated 20268 min readProxy technology Holy Unblocker is the platform, Scramjet is one engine inside it A large platform box labelled InvisiProxy, formerly Holy Unblocker LTS, containing Scramjet highlighted in gold, plus Ultraviolet, Wisp, Bare-Mux, Epoxy and Libcurl Platform InvisiProxy LTS, formerly Holy Unblocker LTS Scramjetengine: intercept, rewrite, sandbox Ultravioletengine: fallback proxy Wisp + Bare-Muxprotocol and transport switching Epoxy transportoptimized for Chromium and Apple Libcurl transportcross-browser option Holy Unblocker was the platform. Scramjet is one of the engines behind it. If you have been researching browser-based proxies, you have probably come across two names repeatedly: Holy Unblocker and Scramjet. At first glance they look like competing services, but they are quite different. The simplest way to see it: Holy Unblocker was a web-proxy platform that used multiple proxy technologies, while Scramjet is a web-proxy technology that can be integrated into platforms such as Holy Unblocker. In 2026 the distinction matters more, because the project formerly known as Holy Unblocker LTS continues as InvisiProxy LTS (we cover that in Holy Unblocker vs InvisiProxy). It includes Scramjet alongside Ultraviolet, Wisp, Bare-Mux and different transport systems. What Was Holy Unblocker? Holy Unblocker was an open-source, browser-based web proxy platform. It offered a clientless way to reach websites: instead of installing a conventional VPN app, traffic was processed through proxy technologies running inside the web application. It was designed as a broader platform rather than a single engine, incorporating: Scramjet Ultraviolet Wisp Bare-Mux Rammerhead in earlier configurations Different transport systems Its continuation, InvisiProxy LTS, lists Scramjet and Ultraviolet as its web proxies and Wisp, Bare-Mux, EpoxyTransport and LibcurlTransport as supporting components. What Is Scramjet? Scramjet is a web-proxy technology that intercepts, rewrites and sandboxes web content inside the browser. Its documentation calls it an experimental interception-based web proxy. Holy Unblocker = the platform. Scramjet = one of the engines used by the platform. That is why comparing them as identical products is misleading. Holy Unblocker vs Scramjet at a Glance Feature Holy Unblocker Scramjet Type Web-proxy platform Web-proxy technology Main purpose A complete browser proxy experience Process and proxy websites Uses Scramjet Yes N/A Uses Ultraviolet Yes No Uses Wisp Yes Works with Wisp-based infrastructure Browser-based / Open source / Self-hosting Yes Yes Multiple proxy engines Yes No Transport options Multiple Integrates with transport infrastructure Current relationship Continued as InvisiProxy LTS Core proxy technology in InvisiProxy The biggest difference is scope. Holy Unblocker was a complete project, while Scramjet is a component that projects like it can use. How Are They Connected? The InvisiProxy repository, which identifies itself as formerly Holy Unblocker LTS, says the project is hosted locally with Scramjet and Ultraviolet built in. It names both as its web proxies, with Wisp and Bare-Mux providing supporting proxy and transport functionality. So Scramjet is not a rival website. It is part of the stack powering a Holy Unblocker-derived platform. Why Did Holy Unblocker Use Scramjet? Modern websites are far more than simple HTML. They may rely on: JavaScript and APIs WebSockets Dynamic URLs and cookies Cross-origin requests Service workers Embedded resources and browser storage A simple URL-forwarding proxy often can’t keep such sites working. Scramjet works inside the browser using interception, rewriting and sandboxing, which lets proxy applications handle complicated sites that traditional proxies cannot. Why Scramjet Became Central The v6.9.8 release described Scramjet as the main proxy for the project and added Libcurl and Epoxy transport support for Scramjet and Wisp. It also adapted apps such as Reddit, YouTube and Discord to use Scramjet. The project increasingly built its experience around it rather than treating it as an optional component. What changed in the v7 era InvisiProxy v7.0.0 updated Scramjet to v2.0.67-alpha and moved to scramjetFrame, along with changes to tooling and transport infrastructure. v7.0.1 updated Scramjet to v2.0.67-alpha.2 to address regressions and also fixed Ultraviolet regressions. Is Scramjet the New Holy Unblocker? No, and this is one of the most common misunderstandings. Scramjet did not replace Holy Unblocker. It is a proxy technology used within the Holy Unblocker LTS lineage. Holy Unblockerplatform / projectScramjetproxy technologyInvisiProxycurrent continuation of Holy Unblocker LTS Is Scramjet Better Than Holy Unblocker? That is like asking whether a car engine is better than the car. Technical comparisons make sense between engines, for example Scramjet vs Ultraviolet, Scramjet vs Rammerhead, or Scramjet vs traditional web proxies. Comparing it with the whole platform mixes two levels of technology. Scramjet vs Ultraviolet This is the more direct comparison. Scramjet is interception-based, built around rewriting, sandboxing and browser integration. Ultraviolet is another browser-based proxy from TitaniumNetwork, described as using service workers, and it names Scramjet as its successor. InvisiProxy still includes both, and its Ultraviolet page describes Ultraviolet as a fallback when Scramjet doesn’t support a site. That is the practical reason to ship more than one engine: different websites behave differently depending on the proxy technology used, and the setup is more flexible than relying on a single implementation. The Layers: Wisp, Epoxy and Libcurl Wisp is not a user-facing website. It is part of the communication infrastructure the proxies use, and Bare-Mux lets the transport be switched. The layers stack like this: Websitethe destinationScramjet / Ultravioletbrowser-side proxyingWispprotocol infrastructureTransportEpoxy or LibcurlProxy connectionto the open web Epoxy is described as optimized for Chromium and Apple environments, while Libcurl is a cross-browser option. These are transport mechanisms, not replacements for Scramjet. Scramjet handles browser-side proxying and rewriting, Wisp supplies protocol infrastructure, Epoxy or Libcurl handle transport, and InvisiProxy provides the user-facing platform. See how a request flows through the proxy on the homepage. Does Holy Unblocker Still Use Scramjet in 2026? The original name is no longer the main name of the LTS project, but its continuation, InvisiProxy
Holy Unblocker vs InvisiProxy: What Changed in 2026?
HUHoly Unblocker What It IsHow It WorksFeaturesSupported SitesDownloadGuideFAQ Get it on GitHub Home / Guide / Holy Unblocker vs InvisiProxy GUIDE · PROJECT UPDATE Holy Unblocker vs InvisiProxy: What Changed in 2026? InvisiProxy LTS is the renamed, continued form of Holy Unblocker LTS. Here is what changed in 2026 and what existing users and self-hosters should know. Updated 20267 min readProject history Holy Unblocker LTS becomes InvisiProxy LTS Diagram showing Holy Unblocker LTS v6.9.5 passing through a rebrand into InvisiProxy LTS v7.x HU Holy Unblocker LTS · v6.9.5 Rebrand InvisiProxy LTS · v7.0.0 → v7.0.1 Scramjet · UltravioletWisp · Bare-Mux Scramjet (updated) · Epoxy · LibcurlTor routing · Region selection Holy Unblocker LTS continued as InvisiProxy LTS, moving into the v7 line. If you have searched for Holy Unblocker recently, you may have noticed a new name: InvisiProxy. So what happened? Is InvisiProxy a completely different project, or the next version of Holy Unblocker? The short answer: InvisiProxy LTS is the renamed and continued form of Holy Unblocker LTS. The official documentation describes it as “formerly Holy Unblocker LTS.” It is more than a cosmetic rename, but it is not an unrelated proxy project. The 2026 releases also introduced technical changes, including updates to Scramjet, transport systems, dependencies, project tooling and overall architecture. What Is Holy Unblocker? Holy Unblocker was a web-based proxy project providing browser-based access to websites without requiring a traditional VPN application. It became known for combining multiple web-proxy technologies and transport systems, including Scramjet, Ultraviolet, Wisp, Bare-Mux and different transport options. It is not a conventional VPN. A web proxy processes browser traffic through a remote service, while a VPN generally operates at the network level and can route traffic from multiple applications. The project also focused heavily on self-hosting, so users could deploy their own instances rather than rely on a single public website. What Is InvisiProxy? InvisiProxy LTS is the continuation of Holy Unblocker LTS under a new name. Its documentation calls it an experimental web proxy service, formerly Holy Unblocker LTS, and it continues to focus on browser-based proxying, self-hosting, privacy features and multiple proxy technologies. Listed technologies include: Scramjet Ultraviolet Wisp Bare-Mux Epoxy Transport Libcurl Transport The interface also exposes region selection, Tor routing, hidden history and different transport options. Holy Unblocker vs InvisiProxy: The Basic Difference Feature Holy Unblocker LTS InvisiProxy LTS Project relationship Original LTS branding Continued project Name Holy Unblocker LTS InvisiProxy LTS Development Earlier LTS releases Current development Scramjet Supported Updated and actively integrated Ultraviolet Supported Still present for compatibility Transport options Multiple Expanded/updated Self-hosting Supported Supported Tor-related functionality Supported in later releases Continued Mobile support Developing Still being improved Version direction v6.x / transition toward v7 v7.x Why Did Holy Unblocker Become InvisiProxy? The release history shows Holy Unblocker LTS in earlier releases, followed by the move to InvisiProxy LTS. Version 6.9.6 specifically listed a project rebrand among its changes, and later releases are published under the InvisiProxy name. Projects rename for reasons such as: Establishing a new project identity Separating the LTS project from older branding Preparing for future development Distinguishing it from other proxy projects What matters for users is that the project did not disappear. The LTS line simply continued under a new name. What Changed in 2026? The v7.0.0 release introduced updated dependencies, a newer Scramjet version, changes to how Scramjet frames are handled, and newer tooling including pnpm and Node.js changes. It also removed Rammerhead from that particular configuration. v7.0.1 then updated dependencies, moved to Scramjet v2.0.67-alpha.2 and addressed regressions involving Scramjet and Ultraviolet. 1. The move to v7 Development continued with substantial changes to the underlying architecture rather than maintaining the old codebase indefinitely. Old Holy Unblocker guides may therefore no longer match the current project. 2. Scramjet became more important Earlier releases already used Scramjet, but later ones updated it and made it more central. v7.0.0 switched to scramjetFrame to match the newer Scramjet version. Compatibility depends heavily on the underlying rewriting and browser-integration technology, and websites keep getting more complicated. 3. Transport systems were updated InvisiProxy supports Epoxy and Libcurl. The documentation describes Epoxy as optimized for Chromium and Apple environments and Libcurl as a cross-browser option. Multiple transports matter because websites can behave differently across browsers. 4. Wisp infrastructure evolved The v6.9.8 release replaced wisp-js with mrrowisp, citing additional features and performance and security improvements. These changes are not obvious when opening the site, but they affect reliability and compatibility. 5. Privacy and browsing features expanded Earlier releases added hidden history and protections against certain tab leaks, and the documentation now describes Tor routing, region selection and different transports. These are not a guarantee of anonymity. A browser-based proxy is not a full privacy solution, and the application itself warns users not to log into primary accounts on a public proxy. 6. Self-hosting remains central The repository provides instructions for deploying on your own server and documents dependencies such as Node.js, Git, curl and Nginx. Self-hosting gives developers more control than relying on an unknown public proxy. Is InvisiProxy the Same as Holy Unblocker? In terms of lineage, yes. But the branding changed, the codebase evolved, dependencies and proxy components were updated, and the project entered the v7 line. Holy Unblocker LTS → rebranding and continued development → InvisiProxy LTS What Happened to the Old Versions? Older releases remain part of the project history. v6.9.5 was still branded Holy Unblocker LTS, v6.9.6 introduced the rebrand, and later v7 releases appeared as InvisiProxy: v6.9.5Holy Unblocker LTSv6.9.6Project rebrandv7.0.0InvisiProxy LTSv7.0.1Scramjet update, regression fixes Is Holy Unblocker Still Available? It depends on what you mean. The original name has moved to InvisiProxy branding, but the project and its technology continue under InvisiProxy LTS. Older pages, guides and repositories may still use the Holy Unblocker name, so you may see both while researching the same lineage. Scramjet and Ultraviolet Holy Unblocker evolved to use Scramjet extensively, while Ultraviolet remains supported. The current application lists both (see how the proxy engines work). Support