Shipping

Iceslab v1.0 panel - multi-core VPN infrastructure for operators.

Open Iceslab →

icecompany.tech/iceslab

/ Operator panel|Available — v1.0

Iceslab

Multi-protocol operator panel that runs protocol binaries natively. No Docker wrappers, no proxy shims, no third-party orchestrators. One dashboard for keys, telemetry, and rotation across seven protocols.

curl -fsSL get.iceslab.tech | shView on GitHub →

Why Iceslab

Four things other panels
get wrong.

If you currently run Marzban, X-UI, 3X-UI, or Hiddify — this is the short version.

/ 01Execution model

Other panels wrap binaries in Docker.

Iceslab runs them as native processes.

Zero container overhead, real PIDs, native logs, predictable resource limits.

/ 02Protocol coverage

Other panels manage one or two protocols well.

Iceslab handles seven in a single dashboard.

Hysteria2, XRay, AmneziaWG, NaiveProxy, MTProto, Shadowsocks 2022, MieRu — first-class, not bolted on.

/ 03Maintenance

Other panels live as a tangle of forks and patches.

Iceslab is one upstream, versioned cleanly.

One repo, semver, changelog. No "which fork has the fix" guesswork.

/ 04Operator footprint

Other panels need five tools to actually operate.

Iceslab ships as a single binary with a built-in UI.

No nginx-proxying, no separate dashboard service, no bot framework dependency.

Install

One curl, one binary,
seven protocols.

Single static binary. No Docker, no compose, no separate database service for the metadata layer.

Read the docs · soonView on GitHub →
~/iceslab
$ curl -fsSL get.iceslab.tech | sh
↳ Downloading Iceslab v1.0.0 (linux-amd64, 18 MB)…
↳ Verifying signature… ok
↳ Installed to /usr/local/bin/floe
✓ Done in 4.2s

$ iceslab init
↳ Creating ~/.floe/config.toml
↳ Registering protocols: hy2 · xray · awg · naive · mtproto · ss22 · mieru
↳ Generating admin token…
✓ Iceslab is ready. Visit https://localhost:9000

$

Protocol matrix

Seven protocols.
Each pinned to a known version.

Architecture

A supervisor,
not a wrapper

Iceslab is a single Rust binary that spawns and supervises protocol runners as native child processes.

Control plane

iceslab (single binary)

HTTP API · operator UI · CLI · auth · billing hooks

↓

Process supervisor

native spawn · health checks · log capture

↓
PID 1234hysteria2
PID 1235xray
PID 1236awg
PID 1237naive
PID 1238mtproto
PID 1239ss22
PID 1240mieru
↓

outbound network

Migration

Switching from Marzban,
X-UI, 3X-UI, or Hiddify?

We do it manually right now. An automated importer is on the Iceslab roadmap.

  1. 01Email operators@icecompany.tech with your current panel + rough scale (users, nodes).
  2. 02We schedule a 30-minute call to walk through your data.
  3. 03Together, we export your inbounds, users, and traffic counters.
  4. 04Iceslab imports them via a one-off script we keep in a private repo.
  5. 05We stay on the line until your old panel is fully decommissioned.

Typical migration takes a few hours. Plan a migration →

Coming next

A white-label Mini App
in your repo.

An Icepath-shaped Telegram Mini App you can drop on top of Iceslab and re-brand. Free.

  • •Drop-in Mini App template (TypeScript / Telegram Web App)
  • •Theming via CSS variables — your colors, your name
  • •Subscription, region picker, config installer — built-in
  • •Payment hooks for Telegram Stars and Cryptobot
  • •Distributed via `floe miniapp init` — one command, your bot is live
  • No timeline yet. We're shipping when the first three external operators ask for it.
    Get notified →

Specs

Honest numbers from a real test deploy.

OS
Linux (kernel 5.10+) · macOS 13+
Architecture
x86_64 · aarch64
Memory
256 MB minimum · 1 GB recommended
Disk
~50 MB binary + protocol runners
Network
1 public IPv4 or IPv6 · UDP open
Dependencies
None. Single static binary.

Pricing

Open core. Pay for the
things a business needs.

Open core · MIT

Free

Self-host. All seven protocol runners, the execution engine, the CLI.

  • · `floe` binary + CLI
  • · Seven protocol runners
  • · Single-tenant operator UI
  • · Community support on GitHub

Commercial license

Contact us

For operators running Iceslab as a business — multi-tenant, audit, white-label.

  • · Multi-tenant key issuance + billing hooks
  • · Audit trail + compliance exports
  • · White-label for client-facing deployments
  • · Priority response + migration support
Talk to us about pricing →

Lane 02 — Operators & resellers

Deploying Iceslab for
your own VPN business.

If you already run nodes — or want to — we'll help with deployment, migration, and reseller setup. Replies usually within a working day.

Write to

operators@icecompany.tech

Compose mail →