Reachability
Circuit Relay v2 keeps peers reachable through NAT, firewalls, and mobile network churn.
Private systems · public proof
I build software
that can be owned.
I’m Adrian Atanasov. I work where product, infrastructure, security, and AI collide—building systems that stay useful when the network, device, or assumption fails.
SYSTEM MAP / 01
Private systems atlas
Paths, not fake telemetry
01Your deviceIdentity + interface
02Private coreTools · memory · keys
03KantP2P messaging
04StormlabsProxmox · containers
05EdgeRelays · remote devices
A map of the work, not a dashboard pretending everything is measurable.
00 / POSITION
Not “full-stack” as a badge.
Full-stack because the problem crosses boundaries.
01 / FLAGSHIP
Serverless · end-to-end encrypted · peer-to-peer
Kant
Messaging where the relay moves ciphertext—not trust.
Kant is built around libp2p, libsodium, deterministic peer identity, and stateless circuit-relay infrastructure. It is designed for real peers behind NAT, firewalls, and unreliable mobile networks.
MESSAGE ROUTE relay-assisted
APeer
encrypted frame
STATELESSRELAYforwards ciphertext
circuit v2
BPeer
NO message storeNO plaintextYES self-hosted relay
Cryptography
X3DH-style session setup, ratcheting, encrypted groups, files, and optional onion routes.
Control
Run the relay yourself. Inspect health, readiness, metrics, and reservation behavior.
02 / SYSTEMS
The rest of the machine.
Each layer exists because the product above it needs somewhere real to run.
Agent infrastructure
Hermes stack
A private multi-channel AI environment with tools, memory, automation, mobile access, and infrastructure-aware workflows.
Self-hosted cloud
Stormlabs
Proxmox hosts, containers, private services, reverse proxies, remote access, monitoring, and test infrastructure.
Security engineering
Test labs
Repeatable web, Windows, Android, and network environments made for testing systems—not staging screenshots.
03 / METHOD
How I work.
Control the critical path.
Dependencies are explicit. Failure modes are visible. Infrastructure stays operable.
The interface is the product.
A clever backend is unfinished until a real person can use it without a manual.
Proof before confidence.
Build it, exercise it, inspect the result, and only then call it done.
04 / CONTACT
Bring me the problem
that crosses boundaries.
Product, networking, agents, infrastructure, security—the interesting work rarely fits one box.