

Proxera
- Outbound-only connectivity
- Multi-domain + path routing
- Live topology & route logs
- Ingress resource management
Proxera is a self-hosted reverse tunnel for HTTP services in a private network, the Cloudflare Tunnel alternative that keeps your traffic off a third party's data centers.
Scroll to exploreReach private services without punching holes in your firewall.
Reaching a home lab or internal service means opening inbound ports
The Proxera agent connects outbound to your server, so the firewall in your network stays closed.
Managed tunnels route your traffic through someone else's network
You run the server yourself. Traffic only passes through infrastructure you operate.
One tunnel per service does not scale
A single agent connection carries many public domains and path prefixes, and Redis lets the server scale across pods.
You cannot see what passes through the tunnel
A live topology view, per-route request logs and Prometheus metrics show what is connected and what is being requested.
Tunnel topology at a glance
The agent initiates an outbound connection. No inbound firewall rules, ever.
Key insight: the agent connects outbound to the server, so your LAN firewall stays completely closed.

Early alpha. Proxera is under active development. Breaking API changes may be introduced at any time until a v1 release.
Why choose Proxera
Everything you need to securely expose private services, and nothing you do not.
WebSocket reverse tunnel
A persistent outbound connection from the agent in your LAN to the server in the cloud.
Multi-domain routing
Assign one or more public domains, with optional path prefixes, to any local service through a single agent connection.
Topology dashboard
An interactive live graph of pods, connected agents and active routes.
Live request logs
A per-route access log streamed in real time, plus route-level request visibility.
One-time token registration
Admins create a named agent slot and generate a one-time registration token, consumed on first connect, in the style of GitLab runners.
Horizontal scaling
Redis Pub/Sub carries tunnel frames across pods. Without Redis, an in-memory bus keeps single-pod setups simple.
Show all 12 features
Admin UI and REST API
A Bootstrap admin panel and REST API on the same port as the proxy, with Swagger UI.
Prometheus metrics
Metrics are exposed at /actuator/prometheus.
Ingress management
Create, edit and delete Kubernetes Ingress resources from the topology view when running in-cluster.
Helm charts
Production-ready charts for server and agent, with RBAC, a service account and an admin ingress.
Home Assistant add-on
Run the agent as a native add-on. Install it from the add-on store and expose Home Assistant without port forwarding.
Agent binaries and images
Binaries for Linux and Windows on amd64 and arm64, plus a container image. Releases ship checksums, cosign signatures and an SBOM.
Built secure by design
Security and operational control are first-class concerns, not afterthoughts.
Token-based agent registration
Admins create named agents and issue one-time registration tokens. Tokens are consumed at first connect for controlled, auditable onboarding.
Route-level request visibility
Inspect route logs and active requests in near real-time to understand traffic patterns and troubleshoot routing issues quickly.
Horizontal scale support
Use Redis Pub/Sub in multi-pod mode, or run in-memory messaging for small single-pod deployments without extra infrastructure.
Private-network first model
Proxera agents initiate outbound connections only — minimizing attack surface and eliminating inbound pinholes entirely.
Built for your infrastructure
From home labs to production clusters, Proxera adapts to your setup.
Home Lab Access
Expose Grafana, Home Assistant, Uptime Kuma, or dashboards from your LAN over a secure tunnel — no port forwarding needed.
Secure Internal APIs
Publish selected internal APIs without opening inbound ports or placing services directly on the public edge.
Preview Environments
Route temporary domains to staging apps running inside private clusters or local developer environments.
Edge & IoT Services
Connect industrial or remote-site services back to a central Proxera deployment using outbound-only agent links.
Dev Team Tools
Share internal portals, Git mirrors, and tools across distributed teams without VPN complexity or overhead.
Zero-Inbound Enterprise
Maintain strict firewall posture while enabling public ingress for selected internal web workloads with full audit trails.
Up and running in minutes
Deploy the server, create an agent, start it in your network and add a route.
Full installation guide
Step-by-step setup, configuration options and troubleshooting for Proxera.
DNS first. Point a hostname for the admin UI and tunnel (for example admin.proxera.example.com) and a hostname for routed traffic (for example app.intranet.example.com) at Proxera before connecting an agent. A wildcard record such as *.intranet.example.com saves you a new DNS entry for every service.
Deploy Proxera Server
Install with Helm on Kubernetes, or run the container for local testing. The embedded H2 database needs no extra services.
Log in to the admin UI
Open /admin. Default credentials are admin and admin. Create a new admin account and remove the defaults right away.
Create an agent and token
Under Agents, create a named agent and generate a registration token. It is shown only once, so copy it.
Start the agent in your network
Run the Helm chart, the container, the binary or the Home Assistant add-on with the server URL and the token.
Add routes and go live
Map a public domain and optional path prefix to a local service. Traffic is tunnelled to it immediately. On Kubernetes you can also create the Ingress from the topology view.
helm repo add wenisch-tech https://charts.wenisch.tech
helm repo update
helm install proxera wenisch-tech/proxera \
--set ingress.admin.enabled=true \
--set ingress.admin.hosts[0].host=admin.proxera.example.com \
-n proxera --create-namespacedocker run -d --name proxera -p 8080:8080 ghcr.io/wenisch-tech/proxera:latesthelm upgrade --install proxera-agent wenisch-tech/proxera-agent \
--namespace proxera --create-namespace \
--set config.serverUrl="wss://admin.proxera.example.com/tunnel" \
--set secret.apiKey="<registration-token>"docker run -d --name proxera-agent \
-e PROXERA_SERVER_URL=wss://admin.proxera.example.com/tunnel \
-e PROXERA_API_KEY=<registration-token> \
ghcr.io/wenisch-tech/proxera-agent:latestcurl -LO https://github.com/wenisch-tech/proxera-agent/releases/latest/download/proxera-agent-linux-amd64
chmod +x proxera-agent-linux-amd64
./proxera-agent-linux-amd64 \
--server-url wss://admin.proxera.example.com/tunnel \
--api-key "<registration-token>"# 1. Add the repository in Home Assistant
# Settings → Add-ons → Add-on Store → ⋮ → Repositories
# Add: https://github.com/wenisch-tech/proxera-agent
# 2. Find "Proxera Agent" in the store and click Install
# 3. Configure the add-on (Configuration tab):
server_url: wss://proxera.example.com/tunnel
api_key: "your-api-key-here"
log_level: info
# 4. Go to the Info tab and click Start
# The add-on starts automatically on every HA boot.Or use the one-click button: Add the repository to Home Assistant.
A route
| Field | Example | Description |
|---|---|---|
| Agent | home-lab | The agent that handles requests for this route |
| Domain | myapp.proxy.example.com | Public hostname Proxera matches incoming requests against |
| Path prefix | / | URL path prefix to match, use / for all paths |
| Target URL | http://192.168.1.10:3000 | The local service URL the agent forwards requests to |
Configured with environment variables
Start with the defaults, add PostgreSQL and Redis when you need them.
| Variable | Default | Description |
|---|---|---|
DB_HOST | (unset) | PostgreSQL host. When unset, the embedded H2 database is used. |
DB_PORT / DB_NAME | 5432 / proxera | PostgreSQL port and database name |
DB_USER / DB_PASSWORD | proxera / (empty) | PostgreSQL credentials |
REDIS_HOST | (unset) | Redis host. When unset, the in-memory message bus is used. Set it for multi-pod scaling. |
REDIS_PORT / REDIS_PASSWORD | 6379 / (empty) | Redis port and password |
SERVER_PORT | 8080 | One port for the admin UI, the reverse proxy and the tunnel WebSocket |
Frequently asked questions
Is Proxera a Cloudflare Tunnel replacement?
Proxera is a self-hosted alternative with a similar operational model: outbound tunnel agents and routed traffic from public domains to private services. Unlike Cloudflare Tunnel, you retain full infrastructure ownership and routing control.
Do I need to open inbound firewall ports?
No. The Proxera agent establishes outbound WebSocket connectivity to the server and receives proxied traffic through that tunnel. Your LAN firewall stays completely closed — no inbound pinholes required.
Can I run Proxera in Kubernetes?
Yes. Proxera provides Helm charts for both server and agent, supporting environments from home lab single-node clusters to production-grade Kubernetes deployments.
How does agent registration work?
Admins create named agents and issue one-time registration tokens via the admin UI or API. The token is consumed on first agent connect — enforcing a controlled, auditable onboarding flow.
Can Proxera manage Kubernetes Ingress resources?
Yes. Proxera includes built-in Ingress resource management — you can create, update, and delete Kubernetes Ingress resources directly from the admin UI. This lets you wire up public routes to in-cluster services without leaving the Proxera interface or editing YAML manually.
Where does the Proxera agent run?
The agent runs inside your private network (LAN, home lab, edge site, or private Kubernetes cluster) and opens a persistent outbound WebSocket tunnel to the Proxera server. No cloud dependencies in your private network.
Is Proxera production ready?
Proxera is in early alpha and under active development. Breaking API changes may be introduced at any time until a v1 release, so evaluate it before relying on it for critical services.
Start tunneling today, for free
Proxera is open source under the GNU AGPLv3 licence and fully self-hosted. No cloud account, no per-tunnel fees, no vendor lock-in.