Our own stack, top to bottom
from the memory allocator to HTTP/3
We write the foundation of networked software ourselves: I/O engines, protocols, cryptography, data parsing, memory management. From scratch, following the text of the standards, as a single whole — and every layer is measured against the reference implementation of its field. Russian platforms — Elbrus, GOST, domestic operating systems — get first-priority support.
Three levels, each standing on its own
Our products are not assembled from other people's libraries — they stand on our own foundation. At the bottom is what is meant to become an operating system for that foundation.
Russian platforms come first
ANYKS's main goal is fully domestic technology that a state's sovereignty can rest on: code written here, to open standards, with no foreign backdoors and no foreign decisions about what happens to it tomorrow. That is why everything domestic — processors, algorithms, operating systems — gets first-priority support from us, not a place at the end of the list.
Elbrus processors
AWH and A-NTS are being ported to Elbrus-8C2 right now, and the results are already good. A-NTS builds with the lcc compiler and runs in full. In AWH the memory allocator, fibers and system modules run on Elbrus, and the regex code generator speaks the e2k instruction set — something no library we know of does.
GOST algorithms
Kuznyechik, Magma, Streebog, GOST R 34.10-2012 signatures and VKO are part of A-NTS, not a separate provider to install and maintain. And faster than the GOST references: encryption up to 3.4×, signing 2.6–2.8×.
Our order of work is simple: domestic platforms go first. Our own networking, cryptography, memory and data handling are what technological independence is made of — not a logo on someone else's code.
Open it and use it
ACU
Converts data between XML, JSON, YAML, INI, CSV, CEF, SysLog and Grok, computes hashes, converts number bases, bytes, seconds and dates. In the browser at acu.anyks.com or locally with a single tool.
Crisper
Ten compression algorithms to choose from, AES encryption, its own container format and search inside. A desktop application and a command-line version for servers.
The foundation everything else stands on
These projects already work and are tested on twelve systems, but they are still growing. Each has its own page with design notes, measurements and an honest account of weak spots.
AWH
One library instead of forty: kqueue, epoll, io_uring, IOCP and event ports engines, HTTP/1.1, HTTP/2, HTTP/3 and QUIC, WebSocket, SOCKS5, DNS, NTP, codecs, process cluster — on twelve operating systems.
A-NTS
TLS 1.3 and 1.2, DTLS, QUIC, ECH and HPKE, GOST (Kuznyechik, Magma, Streebog), post-quantum ML-KEM. Builds with one compiler, no Perl or Go. Will replace BoringSSL in AWH.
awh::alloc
Replaces the system allocator for the whole process. Fault address analysis, guard pages, a secrets store, control over returning memory. Beats jemalloc on every system compared.
awh::regex and Grok
Our own PCRE2 replacement with machine code generation for ARM64, x86-64 and Elbrus: faster than PCRE2 in 37 of 41 scenarios. On top of it, Grok for log parsing with 307 built-in patterns.
What will be built on this foundation
Projects with a finished description and work plan. Each uses what is already written in the foundation instead of starting from zero.
AWF
A platform for websites and portals: code is written in Lua, TCL or Python, modules in different languages call each other directly, and the finished project ships to the client as a single encrypted application.
ABS
Industrial backup with live synchronisation: file system changes are tracked by subscription, and data lands in a smart container with deduplication and encryption.
Smart container
Not an archiver but a store: snapshots, deduplication, post-quantum encryption, per-file rights and signatures, and a read-only mode for handing over confidential documents.
ANYKS OS
Our own kernel with persistent memory instead of yet another Linux distribution: data centres, then workstations, native Elbrus support and mobile devices.
Four rules you can see in the code
From the standard, from scratch
Protocols are written from the text of RFCs and GOST standards. Other implementations serve only as references to compare results against.
Measured, not claimed
Every layer is benchmarked against the reference of its field: nghttp2, ngtcp2, OpenSSL, PCRE2, jemalloc. Reports live next to the code.
Weaknesses in plain sight
Where we fall behind, we say so directly — by how much and why. Sell what actually exists.
Decisions are recorded
Every deliberate departure from the obvious is described in the header with its reasoning and pinned by a test.