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:
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 does not mean every service works identically through both, since compatibility depends on the website, browser, transport and the current version of the underlying technology.
Is InvisiProxy Better Than Old Holy Unblocker?
- Updated dependencies: the 2026 releases include numerous upgrades.
- Newer Scramjet integration: browser integration adapted to newer versions.
- Updated transports: Epoxy and Libcurl alongside Wisp and other components.
- Continued development: v7 work and future plans are documented.
Newer software can also introduce regressions. The v7 releases document known issues, including problems with certain search engines and transport errors, so newer does not mean every feature works perfectly.
What Is Planned for the Future?
The roadmap points beyond v7, with a future v8.x.x line considered the production direction. Planned areas include:
- Improved Firefox support
- Better search handling
- Improved mobile support
- Additional sandboxing techniques
- More proxy configuration options
- Improved onboarding
- Further Scramjet updates
- More privacy and fingerprinting protections
- More language support
Should Existing Users Be Concerned?
No. Recognize the new branding and check current documentation before following an old tutorial (our guides section is kept up to date), which may reference old repository names, configuration files, dependency versions, transport defaults, earlier Scramjet versions or previous branding. For setup and self-hosting, prefer current InvisiProxy documentation.
Is InvisiProxy a VPN? Is It Safe?
No, it is a web proxy platform. A VPN creates a network-level tunnel for multiple applications, while a browser-based proxy focuses on web traffic handled inside the proxy environment, so do not assume equivalent protection.
Safety depends on deployment and use. On a public instance you are trusting its operator, and the official application advises against logging into primary accounts. Technically experienced users can self-host and review the source and configuration. Either way, a web proxy is not a guarantee of anonymity or security. See our disclaimer and privacy policy for more.
Final Verdict
The biggest change in 2026 is not that a new project replaced Holy Unblocker. Holy Unblocker LTS evolved into InvisiProxy LTS, with new branding alongside substantial technical work: the v7 generation, updated Scramjet, changed transport and dependency stacks, and continued improvements to compatibility and self-hosting.
Holy Unblocker LTS did not simply vanish. Its LTS project continued under the InvisiProxy name, and for current documentation, features, releases or self-hosting information, InvisiProxy LTS is the name to look for.
Frequently Asked Questions
Is InvisiProxy the new Holy Unblocker?
Yes. InvisiProxy LTS is officially described as formerly Holy Unblocker LTS, the continuation of that project under new branding.
Why did Holy Unblocker change its name?
The project was rebranded during the v6.9.x development period and continued as InvisiProxy LTS.
What version is InvisiProxy on in 2026?
The v7 series, with v7.0.0 and v7.0.1 documented in the official repository.
Does it still use Scramjet and Ultraviolet?
Yes. Scramjet is an important component with updates in the 2026 releases, and Ultraviolet remains listed, though compatibility can vary between technologies and releases.
Can InvisiProxy be self-hosted?
Yes. The official repository provides self-hosting documentation and setup information.
Should I follow an old Holy Unblocker tutorial?
Only with caution. Older tutorials may reference outdated dependencies, configurations or names. Current InvisiProxy documentation is preferable.
Is Holy Unblocker still being developed?
The LTS project continued under the InvisiProxy name, with v7 releases and an ongoing roadmap.