If you're looking for a browser-based proxy with more functionality than a basic web proxy, Holy Unblocker is worth understanding beyond its name. Its LTS project continued under the InvisiProxy name, and the current project combines several technologies designed for browser-based proxying, website compatibility, transport flexibility, privacy-oriented browsing and self-hosting.
Depending on the deployment and version, you can get multiple proxy engines, different transport options, privacy features, self-hosting and compatibility tools. This guide explains the major features and what each one does.
What Is Holy Unblocker?
Holy Unblocker was an open-source browser-based web proxy project. Unlike a traditional VPN application, a browser proxy works through the browser, rewriting and processing website resources so a remote site can be displayed through the proxy interface.
The LTS project now continues as InvisiProxy LTS, which its documentation identifies as formerly Holy Unblocker LTS, listing Scramjet, Ultraviolet, Wisp, Bare-Mux, EpoxyTransport and LibcurlTransport. Some current functionality belongs to this newer generation. See Holy Unblocker vs InvisiProxy for the full story.
Features at a Glance
- Browser-based web proxying and clientless browsing
- Scramjet and Ultraviolet proxy support
- Wisp, Bare-Mux, Epoxy and Libcurl transports
- Hidden history and Tor/Onion routing
- Region selection in supported deployments
- Self-hosting and an open-source architecture
- Browser compatibility work and ongoing updates
Not every public deployment exposes every feature. Configuration, version and server setup affect what you can access.
1. Browser-Based Web Proxy
The most fundamental feature. Instead of installing a desktop VPN client, you use the proxy through a browser interface, and it processes the requested site through its own infrastructure. It is not a VPN: a VPN generally works at the network level, while a browser proxy focuses on web traffic handled through the proxy environment.
2. Scramjet Support
Scramjet is an interception-based web proxy that uses rewriting and sandboxing to process sites inside the browser. InvisiProxy lists it as a web proxy and recent releases keep updating the integration. It matters because modern sites rely on JavaScript, dynamic requests and APIs, so a proxy has to do more than download HTML. Read more in Holy Unblocker vs Scramjet.
3. Ultraviolet Support
Ultraviolet is another browser-based proxy that uses service-worker techniques. Having it next to Scramjet is useful because sites behave differently, and if one implementation has problems, another may do better. That is why the project doesn't rely on a single proxy technology.
4. Multiple Transport Options
Transport is the layer that carries proxy requests between the browser and the proxy infrastructure. The project includes EpoxyTransport and LibcurlTransport, which can differ in compatibility and performance. One may suit a particular browser while another offers broader compatibility.
5. Wisp Integration
Wisp provides proxy communication infrastructure used by technologies such as Scramjet. The architecture has several layers:
This design lets individual components be updated without replacing the whole application. You can see the basic flow in how Holy Unblocker works.
6. Bare-Mux Support
Bare-Mux lets browser applications manage and switch between proxy transports. Rather than hard-coding one connection method, a transport-management layer helps the proxy pick an appropriate one, which gives developers extra flexibility.
7. Clientless Browsing
No dedicated VPN client or desktop app is needed. The interface runs inside a modern browser, which makes the concept accessible, but it also makes browser compatibility an important part of the experience.
8. Privacy-Oriented Features
The v7 line added features such as hidden history and protections against certain tab leaks, which reduce some kinds of exposure through the browser interface. They don't make a proxy anonymous. Depending on architecture, destination and configuration, the proxy operator can still see certain traffic.
9. Tor and Onion Routing
In supported deployments, Tor/Onion routing sends traffic through multiple relays rather than a single proxy connection, which can add privacy characteristics. It also adds latency, so it suits cases where privacy matters more than speed. Combining technologies still doesn't guarantee complete anonymity.
10. Region Selection
Some deployments let you choose between proxy regions, which can affect latency, speed, website behavior and geographic routing. A closer server can sometimes reduce latency. Available regions depend on the deployment: a self-hosted install may have one location, a larger one several.
11. Self-Hosting
A key feature for developers: rather than relying on a public instance, you can deploy the software on your own server, following the project's documented requirements. See our self-hosting section for the steps.
- Greater control over the server and configuration
- Ability to customize the interface
- A clearer view of where traffic is processed
- Your own deployment to maintain
It also means you are responsible for dependencies, security, updates, networking and server resources.
12. Open-Source Architecture
The InvisiProxy repository is public, so developers can inspect the code, study the architecture and contribute. Unlike proprietary proxy services, you can see how it works, and it doubles as a learning resource for browser proxying, transports and web rewriting.
13. Multiple Proxy Engines
The architecture doesn't depend on one engine. Scramjet and Ultraviolet have different implementation details and compatibility characteristics, so there is an alternative when a site misbehaves through one, and developers can experiment without rebuilding the platform.
14. Website Compatibility
The design targets modern sites, which commonly use:
- JavaScript, APIs and dynamic requests
- WebSockets and cookies
- Client-side routing
- Embedded content and browser storage
Engines like Scramjet process these resources so sites keep working. No browser proxy can guarantee compatibility with every website, though, and changes to site code and security policies mean compatibility shifts over time.
15. Browser-Based Gaming
Because it runs in the browser, compatible HTML5 and browser games can potentially be played through the proxy. Performance depends on server distance, transport, browser, game architecture, JavaScript workload, latency and server resources. Fast multiplayer games are especially latency-sensitive, so a proxy that suits ordinary browsing may not suit them. See Holy Unblocker Games.
16. Customizable Proxy Configuration
Developers and self-hosters can configure proxy and transport selection, server settings, application and interface settings and deployment options. Options vary between versions and deployments, so use the documentation for your release rather than an outdated tutorial.
17. Mobile Compatibility
You can reach browser-based deployments from mobile browsers, but compatibility depends on browser, operating system and transport. The roadmap includes mobile improvements, and mobile browsers have different limitations from desktop Chromium. Test the browser and deployment you plan to use.
18. Firefox and Cross-Browser Development
Chromium, Firefox and mobile browsers differ in service workers, APIs, networking and security restrictions. The roadmap includes better Firefox support, a sign that compatibility is treated as ongoing engineering rather than something solved once.
19. Developer-Friendly Ecosystem
The project connects to Scramjet, Ultraviolet, Wisp, Bare-Mux, Epoxy, Libcurl and browser APIs. Someone learning about browser proxies can study each component and then see how they combine into a complete application.
20. Ongoing Updates
The current project is InvisiProxy LTS v7.x.x, with newer dependencies, proxy updates and a roadmap beyond v7. This matters because websites adopt new frameworks, browsers change APIs and security restrictions evolve, and an actively maintained project can adapt in ways an abandoned one cannot.
Holy Unblocker vs a Basic Web Proxy
| Feature | Basic Web Proxy | Holy Unblocker / InvisiProxy |
|---|---|---|
| Browser-based access | Yes | Yes |
| Multiple proxy engines | Usually no | Yes |
| Scramjet / Ultraviolet | No | Yes |
| Multiple transports | Limited | Yes |
| Wisp / Bare-Mux | Usually no | Yes |
| Self-hosting | Sometimes | Yes |
| Open source | Varies | Yes |
| Privacy-oriented features | Limited | Yes |
| Tor/Onion options | Usually no | Supported in relevant deployments |
| Developer customization | Limited | Extensive |
| Modern web compatibility | Varies | Designed for modern web applications |
The main difference is architecture and flexibility. A basic proxy simply forwards requests, while this ecosystem combines proxy engines, Wisp, Bare-Mux and transports, so components can be updated individually.
Are All Features Available Everywhere?
No. There is a difference between the project's capabilities and the features enabled on a particular instance. A public deployment may disable options, and self-hosted installs differ by server resources, version, browser and settings, so don't assume every documented feature appears on every Holy Unblocker-related site.
Is It a VPN? Is It Anonymous?
It is not a VPN. A VPN works at the network level for multiple applications, while a browser proxy focuses on web traffic in the proxy environment. If you need network-wide protection, that is a different kind of solution.
No proxy should be described as completely anonymous. Privacy depends on the proxy server, operator, browser and website behavior, logging policies, connection architecture and your own account activity. Be careful with credentials on public instances. Self-hosting gives more control but makes you responsible for securing the server. See our disclaimer too.
Frequently Asked Questions
What are the main Holy Unblocker features?
Browser-based proxying, Scramjet and Ultraviolet support, multiple transports, Wisp and Bare-Mux integration, self-hosting, privacy-oriented functionality and an open-source architecture.
Does it use Scramjet and Ultraviolet?
Yes. The current InvisiProxy project, which continues Holy Unblocker LTS, includes both as web-proxy technologies.
Can it be self-hosted?
Yes. Self-hosting is an important, documented part of the project for developers who want their own instance.
Does it work on mobile?
Browser-based deployments can work on mobile browsers, but compatibility varies by browser, operating system, transport and deployment.
Can it be used for games?
Compatible browser games can work, but performance depends on latency, server resources, browser compatibility and the game.
Does it hide my IP address?
A proxy can change the network path to a destination, but exact privacy depends on the deployment and architecture, and it is no guarantee of anonymity.
What are Wisp and Bare-Mux?
Wisp is proxy communication infrastructure used by technologies such as Scramjet. Bare-Mux is a transport-management component that helps proxy apps work with different transports.
Is Holy Unblocker still being developed?
The LTS project continued as InvisiProxy, with a v7.x line and an ongoing roadmap.
Final Thoughts
Holy Unblocker is more than a simple proxy website. Scramjet and Ultraviolet handle proxying, Wisp provides communication infrastructure, Bare-Mux manages transports, and Epoxy and Libcurl provide transport options, all continuing under the InvisiProxy LTS name.
For users, that means a flexible browser-based proxy with multiple engines, transports, self-hosting and privacy-oriented functionality. For developers, it is an open-source environment where each component of modern browser proxy technology can be studied, configured and developed further.