Iceslab v0.1.8 - open-source operator panel under AGPL-3.0. First publish 2026-05-19, latest v0.1.8 on 2026-06-20.
Open Iceslab →Icecompany builds Ice - an ecosystem of infrastructure tools for the modern internet. A VPN operator panel, its native client, a consumer service, a proxy protocol engine, and a reverse proxy layer.
- The Ice ecosystem
Iceslab and Iceshard are a closed pair. Icepath is our own consumer service on top. Icecore is the protocol engine underneath. Iceproxy is the reverse proxy layer.
closed pair
runs on top - Iceslab + Iceshard
protocol layer
Open-source operator panel for self-hosted VPN deployments. Spawns seven protocol runtimes on each node and gives operators one dashboard for keys, traffic, and billing.
Open /iceslabNative client built for Iceslab-powered services. Zero-config for users, real-time control for operators. Hand-built in C++/Qt, Windows first.
Open /iceshardOur own consumer VPN service running on top of Iceslab + Iceshard. Telegram Mini App for purchase, native client for connection.
Open /icepathProxy core and protocol engine. One runtime, many protocols - the low-level layer that Iceslab nodes run on top of. Direction: multi-protocol engine like Xray and sing-box, built for predictability and observability.
Open /icecoreReverse proxy layer for incoming traffic - routing, TLS, upstreams. Long-term goal: a more predictable alternative to Nginx, Caddy, and Traefik for self-hosters. Honestly early stage right now.
Open /iceproxyHow it fits together
Each product sits on the one below it. Icecore is the protocol engine. Iceproxy handles the reverse proxy layer. Iceslab is the operator panel. Iceshard is the native client. Icepath is our own consumer service running on everything.
Protocol engine
Icecore
Multi-protocol runtime - the base layer
Reverse proxy
Iceproxy
Routing, TLS, upstreams at the entry point
Operator panel
Iceslab
Open-source panel - any operator can run it
Native client
Iceshard
Dedicated app for Iceslab-powered services
Consumer service
Icepath
Our own VPN service on top of the full stack
Now · week of 15 May
Hysteria2 obfuscation profile shipped to beta channel. Reduced detection on three test ISPs.
ShippedEarly spec work on the multi-protocol runtime. Reviewing Xray and sing-box internals, mapping what a unified engine needs.
In progressMulti-core scheduler pre-alpha running on a 3-node test cluster. Real PIDs, real logs, real numbers.
Shippedicecompany.tech umbrella is live. Five products, one public roof.
MilestonePrinciples
- 01
No always-on drivers, no scope creep, nothing that survives uninstall. The machine belongs to the user. We are a guest.
- 02
Networking software should be predictable, observable, recoverable. Excitement belongs in the product, not the plumbing.
- 03
Roadmaps, postmortems, architecture notes - public by default. The most useful docs we write are for ourselves.
Working with us
Pick whichever fits. Replies come from a real person, usually within a working day.
Lane 01·For infrastructure operators
Both are in R&D and planning stage. If you run nodes and want a heads-up when early builds are ready - or want your use case to shape what gets built - write.
Write to
hello@icecompany.tech
Lane 02·For operators & resellers
If you already run nodes or want to start - Iceslab gives you native execution, multi-tenant keys, and observable infrastructure.
Write to
operators@icecompany.tech
Press, partnerships, anything else - just write directly.
hello@icecompany.tech