Predictability
One runtime, one config surface, one set of logs. Operators know what's running and why.
Public alpha
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.tech/Icecore
/ Proxy core|R&D - early stage
One engine,
many protocols.
Icecore is a multi-protocol proxy runtime. One binary, many protocols running side by side - the low-level layer that Iceslab nodes sit on top of. Direction: a unified engine in the spirit of Xray and sing-box, built for predictability and observability. Honestly early R&D right now.
CurrentlyArchitecture & spec
What it is
Multi-protocol,
single runtime.
Today Iceslab orchestrates seven protocol runtimes as separate processes. Icecore is the path toward one unified runtime that runs all of them together - one binary, one process tree, one place to look when something goes wrong.
Observability
Metrics, traces, and health checks from a single source. No stitching together output from six different processes.
Protocol breadth
Multiple proxy protocols in one engine - the same direction Xray and sing-box took, but built ground-up for the Iceslab node model.
At a glance
- Surface
- Proxy core / runtime
- Audience
- Operators · Iceslab nodes
- Approach
- Multi-protocol engine
- Milestone
- R&D · early stage
Honest stage
This is direction,
not a shipped product.
Icecore is where we're going, not where we are. Iceslab today orchestrates protocols as separate processes. Icecore is the long-term architecture: one engine below all of them. We're not shipping betas or promising dates. If you run infrastructure and this interests you, write.
What we won't claim
Benchmarks against Xray or sing-box
Those are mature, battle-tested tools. Icecore is in R&D. Comparisons come after something runs in production, not before.
Shipping dates
Research doesn't have a calendar. The direction is clear; the timeline is not. We'll post to field notes when there's something real.
Feature-complete scope
We know what we're building toward. We don't know which protocols make the first cut. That gets decided by what Iceslab operators actually need.
Interested early?
Shape it before
it ships.
If you run VPN infrastructure and want to be in the loop on Icecore R&D - or want your use case to influence what gets built first - write to us. No obligations, no timeline promises.
Write to
hello@icecompany.tech