Iceslab v0.2.0 is out. Self-host the operator panel under AGPL-3.0.

Icecompany

Quiet tools for loud problems

Five infrastructure products for the private internet, built in the open by one studio.

See the ecosystemRead the roadmap
50Users on a panel we do not run
232Cloners in fourteen days
v0.2.0Released 14 August 2026
AGPLNo keys, no phone-home
Install

One command, one node

A clean Ubuntu server is enough. The script installs Docker, brings up the panel with Postgres and Caddy, issues the certificate and starts seven protocol runtimes. No config files to write.

Walkthrough
04The domain the certificate is issued for. This is the only value you have to decide.
06One line does the whole install: Docker, panel, database, reverse proxy, TLS.
11Adding a node is one more command. Runtimes come up on their own.
1# iceslab · single node install
2# ubuntu 22.04+, 2 vcpu, 4 gb ram, ports 80 and 443 free
3
4export PANEL_DOMAIN=panel.example.net
5
6sudo bash <(curl -fsSL \
7  https://raw.githubusercontent.com/icecompany-tech/iceslab/main/scripts/install-iceslab.sh)
8
9# panel ready at https://panel.example.net
10# postgres, caddy and 7 runtimes are up
11
12iceslab node add fra-01 --region eu

Five parts, one stack

The panel and the client only talk to each other. Everything else either sits on that pair or holds it up.

The pairIceslabOperator panel: nodes, keys, traffic, billing. Self-hosted under AGPL.Public alphaIceshardNative client that talks only to that panel. Windows first.PlanningOn topIcepathOur own consumer service. A Telegram Mini App: subscription in, connection out.Public betaUnderneathIcecoreProtocol engine the nodes will eventually run on. Research.R&DIceproxyReverse proxy for inbound traffic: routing, TLS, upstreams. Specification only.Planning

About Icecompany

Right now Icecompany is building one thing: the operator panel. Everything else on this page is either already running or still ahead of it.

What we do
01 · Today

We are building the panel

Iceslab is the whole focus of the studio right now. It runs the nodes, the keys, the traffic and the billing from one place, on the operator's own server. Public, AGPL, in daily development.

02 · Ahead

Three more products after it

Iceshard, the native client for that panel. Icecore, the protocol engine the nodes will run on. Iceproxy, the edge that handles inbound traffic. In that order, each one only when the previous is standing.

03 · Already running

Icepath is a web service

A Telegram Mini App where people buy a subscription and get a connection. It runs today, brings in revenue, and keeps the studio honest about what operators actually need.

Where we are going
NowThe panel
NextThe client
LaterEngine and edge

Ten panels we did not run

The only product with a target attached to it. Ten operators outside the studio, with real users, on servers we never touched. Not downloads, not stars.

Progress1 of 10

One operator runs the panel in production for around fifty users. Nine to go before the licence question gets asked.

What we will not do

Sell licence keys

No keys, no activation, no counting how many people use your panel. It runs on your server, so it is yours.

Charge too early

Money before ten working deployments would buy polite silence instead of the bug reports we actually need.

Close the pair

The panel and the client stay under AGPL. If the studio disappears tomorrow, the operators keep working.

The studio in numbers

Small numbers, and real ones. Nothing here is rounded up or borrowed from someone else's press release.

Products in flight5
Public releases9
Cloners in 14 days232
Deployments outside1
People in the studio1

What lands on your server

Nothing exotic. Seven pieces you can name, all of them running as containers you can stop, inspect and restart by hand.

EdgeCaddyTerminates TLS, renews the certificate, routes the panel and the subscription endpoint:80 :443
The panelIceslabOne Go binary: web interface, API for the nodes, scheduler, billingv0.2.0
$ docker compose ps iceslabiceslab-panel running 0.0.0.0:8080->8080/tcpmemory 148 MB cpu 0.4% uptime 41dno outbound connections outside your nodes
Written by usThe only line in this stack that is ours. Everything above and below is standard.
StatePostgresKeys, limits, invoices, audit log. Backed up by one command, restored by another16
CacheValkeySessions, rate limits, the queue that pushes config to the nodes8
On each nodeSeven runtimesvless-reality, trojan, shadowsocks, hysteria2, vmess, tuic, wireguard7 pids
WrapperDocker ComposeOne file you can read. No hidden supervisor, no agent phoning anywherev2
YoursUbuntu 22.04+Any provider, any country. We never see the machine and never ask for accessroot
Minimum server
CPU2 vCPU
Memory4 GB
Disk20 GB
Ports free80, 443
Install timeunder 10 min

Two ways to reach us

Operators

You want to run the panel

Deploying Iceslab, moving from another panel, or something broke and you need a person rather than an issue tracker.

operators@icecompany.techWriteStudios and partners

You are early to the engine work

Icecore and Iceproxy are research. If you build infrastructure and want a say in the shape, this is the door.

hello@icecompany.techWrite