Routing
Traffic routing based on domain, path, or upstream health. Configured from the Iceslab panel, not from YAML files on each server.
Iceslab v0.1.1 - open-source operator panel under AGPL-3.0. First publish 2026-05-19, v0.1.1 patched 2026-05-20.
Open Iceslab →icecompany.tech/Iceproxy
/ Reverse proxy|Early / planning
Iceproxy is the reverse proxy layer for incoming traffic - routing, TLS termination, upstream management. Long-term goal: a more predictable and self-contained alternative to Nginx, Caddy, and Traefik for operators running Iceslab infrastructure. This is direction and ambition, not a ready product.
What it does
Iceproxy sits at the edge of the stack - the first thing traffic hits on the way in. It handles TLS, routes to upstreams, and integrates with the Iceslab panel to make node configuration less manual.
Routing
Traffic routing based on domain, path, or upstream health. Configured from the Iceslab panel, not from YAML files on each server.
TLS
Certificate management without the footgun. Automatic provisioning, renewal, and rotation integrated into the operator workflow.
Upstreams
Health-aware upstream pools. Iceproxy knows which protocol nodes are live and routes accordingly - no manual failover scripts.
At a glance
Honest stage
Iceproxy is planned, not built. The gap it fills is real - operators running Iceslab today deal with Nginx and Caddy configs that live outside the panel. Iceproxy closes that gap. When we have something testable, we'll say so.
Interested early?
If you run self-hosted VPN infrastructure and have friction with your current proxy setup - write to us. Your use case shapes what Iceproxy prioritises.
Write to
hello@icecompany.tech