Sigil Gate Project Blog

Five principles for building a detection-resistant network: from protocol selection and client configuration to rotation, layer isolation, and horizontal scaling.

A short busy week with no time for the project, support still silent, the network on pause — and some thoughts about eggs, baskets, and diversification.

Unexpected trouble with hosting after migration: servers in Japan suspended without explanation.

Yesterday I launched the subscription microservice and wrote ‘deployed itself, without a single manual action.’ This morning users couldn’t connect. Not a single one.

Ten days ago I wrote ’the scheme is ready, all that’s left is to implement it.’ Today the subscription microservice is live.

The support system I’d been dreaming of since February is finally built — in a single evening. Tickets, bot-mediated dialogue, handoffs between admins, and broadcasts.

A prophetic article from Habr I couldn’t find again — and the arms race it predicted. From OpenVPN to statistical invisibility.

Today was a cleanup day. No new features, no forward movement on the map. But now several things work the way they were supposed to from the start.

People often ask about the security of our network and what guarantees we offer. Here’s an honest answer — no marketing promises, no fine print.

A microservice task — and a long-overdue reason to finally try Go in practice. Especially since our project is already soaked in it.