Technical assessment
Review of the architecture, critical path and constraints.
- risk and bottleneck map
- solution options and trade-offs
- validation and next-stage plan
- written findings
KernelSoft is Maxim Lyadvinsky’s independent practice. I personally build critical systems components and conduct independent reviews of R&D, architecture and technical intellectual property.
Where to start
This reduces risk before assigning a critical module or an entire project.
Review of the architecture, critical path and constraints.
Reproducible measurement, profiling and first changes.
A working prototype of the riskiest part of the solution.
Crashes, races, memory corruption or a release-blocking defect.
Minimum paid engagement: 3 business days, from RUB 200,000 or the equivalent in another currency. After a short introductory call, scope, deliverables, validation method and price are fixed.
Engineering services
Drivers, high-performance networking, storage and data protection — dedicated development areas with concrete problems and project results.
GTP, DPI, UPF/PGW, CGNAT, NUMA, NIC offload and measurable performance.
Open direction →02 · KERNELLinux, Windows and macOS device, block, file and endpoint components.
Open direction →03 · DATABIO, RAID/EC, snapshots, encryption, access control and recovery.
Open direction →Dedicated pages for distinct engineering needs, from a new device to a rare system failure.
WDM, KMDF, UMDF, PCIe, USB, DMA, PnP, and release preparation.
→Kernel modules, devices, block and network paths, and kernel-version maintenance.
→Minifilters, storage filters, WFP, and system-level policy enforcement.
→Crash dumps, Driver Verifier, WinDbg, races, memory corruption, and lost I/O.
→FREE TOOLS
PPS, GTP-U and XDP calculations, NIC/NUMA/IRQ analysis, FIO benchmark sanity checking and startup technical assessment. Data is processed locally in the browser.
Technical advisory
For investors, boards and founders: what R&D can really deliver, where deal risks sit and which technologies should be protected.
Team, product, architecture, delivery, QA, support, innovation and IP tested through evidence and confidential interviews.
Review the method → FUNDRAISING / EXITCode ownership, licensing, core-technology map, patent coverage, protection gaps and technical data-room readiness.
Review readiness →Environment setup, documents, chunking, retrieval, the augmented prompt, local generation through WebGPU or CPU/WebAssembly, and source-support checks—all visible and browser-local.
25 questions, AAA–C rating, spider chart and HTML report.
Carrier-grade network virtualization, a BI platform, AI developer tooling and an IT-infrastructure digital twin. Each report covered rating, red flags, product, architecture, engineering quality, innovation and recommendations.
Review the anonymized track record →Within three months the team learned to own the patent process, filed several applications and built a pipeline of additional ideas.
Open recommendation ↗Project examples
Confidential customer information is omitted; test configuration and methodology can be discussed technically.
Initially, the mobile-core user plane processed about 16 Gbit/s through one port of a dual-port Mellanox ConnectX-6 adapter. The task was to optimize the software data path and scale processing across all network interfaces in the server.
GTP-U data-path optimization included per-CPU state, NUMA-local memory, RX/TX queue affinity, cache-line separation, batching, lock-free exchange and NIC offload. The second port on the first adapter was then enabled, and a second dual-port ConnectX-6 was installed on the other NUMA node, with memory, queues and workers kept local to each adapter.
16 → 400 Gbit/s aggregate
One server and the same GTP-U traffic profile; validation through application counters, per-port NIC counters, CPU and NUMA load distribution, and repeated runs. The final configuration used four 100GbE ports across two adapters.
Existing components did not fit the data model, resilience requirements or performance target.
Virtual block devices, BIO mapping, RAID/EC, metadata, thin provisioning, copy-on-write snapshots, SSD/NVMe write path, recovery and rebuild flows.
Architecture and critical low-level components for distributed storage.
Failure recovery, metadata integrity, degraded reads and writes, throughput and latency measurements.
Three platform implementations diverged in behavior, interfaces and release timing.
Shared C++ core, thin OS adapters, common memory, synchronization, I/O and event abstractions, versioned interfaces and a common test matrix.
One architecture for drivers, kernel modules and system services with localized platform differences.
Automated builds and regression tests across platforms, interface compatibility and upgrade scenarios.
Protection and access policies had to apply independently of application and user behavior.
File and disk filters, policy cache, transparent encryption, asynchronous auditing, bypass protection and fail-safe behavior.
OS-level policy enforcement and auditing integrated into an existing product.
Negative tests, bypass attempts, dependent-service failures, audit coverage and data-integrity checks.
PUBLICATIONS
Driver, legacy-code, storage and engineering-method analyses — not generic documentation summaries.
Professional background
The professional background can be checked through public work, patents, profiles and client recommendations.
Technical Fellow, systems engineering and leadership of an R&D initiative focused on storage and data protection.
Open publication ↗ Client recommendationWithin three months the team learned the patent process, filed several applications and created a pipeline of further ideas.
Open recommendation ↗ Patents and citationsMore than 2,400 citations and an h-index of 32 on the author's Google Scholar profile.
Open profile ↗GitHub, systems and R&D articles, an early technical footprint in OSR.
Senior Vice President, Acronis: Maxim was described as essential to the company’s growth from a small startup into an international software vendor, while remaining a hands-on product contributor and leading hundreds of engineers.
Chief Strategy and Operations Officer, Acronis: their work included international R&D-center strategy and innovation priorities for sustainable company growth.
Project outcome
Deliverables and acceptance criteria are defined before the stage begins.
Constraints, risks, bottlenecks and a justified scope.
Components, interfaces, data path, concurrency model and failure modes.
Validation of the riskiest assumption before full implementation.
Source, review, profiling and integration into the customer repository.
Regression tests, build instructions, architecture decisions and knowledge transfer.
Integration, lab diagnostics, stabilization and further optimization.
Engagement stages
A large project starts only after the critical assumptions are validated.
Platform, current implementation, failure point, target load and acceptance criterion.
Code, diagrams, profiles and measurements when required.
Validate the highest-risk area with an agreed outcome.
Code, tests, profiling, documentation and integration in milestones.
Knowledge transfer, production launch and issue resolution.
Accountability
Systems architect and C/C++ kernel engineer
This is an independent expert practice. I personally own the architecture, critical code, diagnostics and final technical review. For larger scopes, additional engineers or domain specialists are involved only after roles, access and accountability are agreed with the customer.
More than 28 years in systems engineering, including 14 years at Acronis. Work has covered drivers, storage, information security, virtualization, high-speed packet processing and cross-platform systems infrastructure.
Co-author of more than 60 patents. Led Acronis Labs, an R&D initiative focused on storage, performance and data-protection technologies.
Discuss the project
Include the platform, what already exists, where the problem occurs, the target load and the acceptance criterion. This is enough to choose a sensible first stage and validation method.