Torhole

The description states that Torhole is a self-hosted DNS privacy gateway. It uses:

• Pi-hole for local DNS blocking
• dnscrypt-proxy to encrypt resolver traffic
• Tor to route queries through the Tor network
• A Docker Compose platform for deployment

It ships with two capability profiles:

• Home: Provides a guided installer, lightweight dashboard, live verification, and safe everyday controls.
• Advanced: Adds VLAN operation, telemetry, SSO, backups, metrics, logs, alerts, and container operations.

The system enforces privacy structurally through firewall and container rules. It does not act as a full VPN; it only protects DNS requests that actually use Torhole.

Inference The product is a self-contained, open-source tool for individuals or small networks to protect their DNS queries via Tor.

The description states that Torhole takes a narrower, verifiable approach to privacy compared to tools like full-tunnel VPNs. It aims to make one precise guarantee visible and testable: DNS handled by Torhole is filtered locally, encrypted to the resolver, and sent through Tor so the resolver sees a Tor exit rather than the public IP.

It explicitly does not promise anonymity, nor does it hide normal browser traffic or control applications that bypass DNS.

Inference The positioning is focused on verifiable DNS privacy, not broad network anonymity. It positions itself as a tool for users who want to see proof of their DNS protection, not just trust a badge.

The description states that Torhole ships with two capability profiles:

• Home profile targets households and first-time self-hosters.
• Advanced profile targets users needing single-LAN or Trusted/IoT VLAN operation.

It also mentions support for Raspberry Pi hardware validation, router-specific setup guides, and public read-only demo environments — indicating a focus on technical users with some infrastructure knowledge.

Inference The ICP is likely tech-savvy individuals or small teams who want to self-host DNS privacy tools and understand the trade-offs involved. No evidence of enterprise or B2B customers.

The description does not state any pricing, monetization, or business model. It only describes a self-hosted tool with two capability profiles (Home and Advanced), both of which are part of a Docker Compose platform.

Inference No evidence of a commercial business model. The tool appears to be open-source or freemium in nature, but no pricing or revenue data is provided.

The project was built using:

• Docker Compose
• Pi-hole, dnscrypt-proxy, Tor
• React/TypeScript for UI
• Python for control and recovery services
• Prometheus, Grafana, Loki, Alertmanager
• Caddy, Authelia

It includes:

• Guided web installer
• Live verification of Tor circuit and DNS path
• Topology-aware dashboards
• Automated CI/CD (shell/config CI, TypeScript build/typecheck, Playwright tests)
• Disposable staging VMs for validation

Inference The tool is built with modern infrastructure and observability practices. It emphasizes operational transparency, distinguishing between confirmed failures and inconclusive verifier outages.

The description states that the project was submitted to a hackathon (OpenAI 2026), and includes:

• Fresh staging deployments validated end-to-end
• Automated backend characterization and tests
• Public documentation stating exactly what Torhole protects and does not protect

However, there is no evidence of revenue, customers, or real-world usage beyond the author's own development.

Inference The project is in a development or early-stage prototype phase, with no traction or adoption data available.

The description contrasts Torhole with:

• Pi-hole: Blocks domains but does not hide where queries originate.
• Full-tunnel VPNs: Change the path of all traffic and transfer trust to an operator.

Torhole is positioned as a narrower, verifiable DNS privacy tool, not a general-purpose privacy solution.

Inference Torhole competes in the DNS privacy and self-hosted security tools space. It does not appear to directly compete with full VPNs or general-purpose privacy suites.

• No evidence of real-world usage or adoption, only a hackathon submission.
• Self-hosted tool: Not suitable for non-technical users, limiting scalability.
• No commercial model or monetization strategy described.
• Limited team size (1 person): May limit development speed and support.
• Dependency on Tor network: Vulnerable to Tor infrastructure issues or outages.

Inference The project is not yet a product with traction, but rather an experimental tool. Risks include lack of adoption, scalability, and commercial viability.

1. What is the actual user base or adoption rate beyond the hackathon?
2. Are there any plans to monetize or commercialize this tool?
3. How does Torhole handle edge cases like transient TLS failures or Tor circuit instability?
4. What are the long-term maintenance and support plans for a self-hosted tool?
5. Has the tool been tested in real-world environments beyond staging VMs?