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/about

/ Studio|Est. 2026|Remote · RU/EU

A studio,
not a startup.

Icecompany is a small group of people who like building boring infrastructure. We make Iceslab, Iceshard, Icepath, Icecore and Iceproxy - five products, one network stack.

Why this exists

The recurring
observation.

In late 2025 we kept reaching for tools that were already broken in the same way. The VPN panel forked from a fork from a fork. The reverse proxy that needed a wall of config to do anything. The native client that parsed any URL it found. Each one made the same trade - short-term ship velocity for long-term operator pain.

We thought we could do better on a small set of these. Not because we're smarter - because we're slower. A studio that ships five tools across three years can pay attention to each one in ways a startup chasing one product market fit can't.

«Most of what we publish is what we wished existed when we started.»

Who is here

One person.
For now.

Icecompany is a solo studio. The name isn't a team - it's the work. Trail is public on GitHub, the rest stays private.

The studio

Solo · everything

Code, infrastructure, copy, design, support - all from one bench. Anonymous on purpose; the public GitHub trail is the resume.

Go · TypeScript · C++github.com/icecompany-tech
+

Collaborators

Per-project · when needed

For scoped chunks - a design review, a security audit, a port to a new platform - we'll bring someone in and credit them on the deliverable. Nobody on retainer right now.

Open to good fits

Operating principles

What stays cold,
even under pressure.

- 01

Respect the user's machine.

No always-on drivers, no scope creep, nothing that survives uninstall. The machine belongs to the user. We are a guest.

- 02

Ship boring infrastructure.

Networking software should be predictable, observable, recoverable. Excitement belongs in the product, not the plumbing.

- 03

Show the work, not the wrapper.

Roadmaps, postmortems, architecture notes - public by default. The most useful docs we write are for ourselves.

Reach out

Four lanes,
one inbox.

All four emails route to the same place but help us route inside. Pick the closest one - we'll read it within a working day.