Founder Story

My name is Constantine Diunov, and I am a software engineer in Florida. The idea for WolfP2P came from two sudden, practical needs. On the same summer day, my wife and daughter independently asked me for help with some “computer stuff” that had no easy answer.

My wife had just completed an accounting webinar and screen-recorded several lectures. She needed to move the recordings from her Windows PC to her Mac. Then my daughter called from New Jersey: “Pa, do you still have our old music library? I couldn’t resist buying the same vintage iPod I had as a kid. Now I need my music—please send it to me.”

A series of two- to three-hour recordings, roughly 2.5 GB each, needed to move from a Windows computer to a Mac. Uploading everything to temporary cloud storage and downloading it again would have been slow and needlessly cumbersome. Setting up network sharing between the two computers required more configuration than a one-time transfer should, while every flash drive I had nearby used USB-A and could not connect to the MacBook.

What I wanted was much simpler: keep both computers online, connect them without fussing with network setup, and move the original recordings directly. Uploading them to cloud storage first felt ridiculous when both machines were sitting on the same desk, connected to the same Wi-Fi. That experience became the basis for transferring complete course-recording collections.

The family music library still existed: roughly 8,000 files and 16 GB, all organized into folders. Moving it through an ordinary cloud-storage workflow would have been awkward for a one-time handoff.

The library needed to arrive as a library—not as thousands of disconnected files. Its artist and album folders mattered, and there was no reason to leave another complete copy with a storage provider after the transfer. That need shaped the resulting music-library transfer workflow.

I realized I was probably not the only person who needed to move large files and complete folders while preserving the original file bytes, avoiding an unnecessary middle copy, and retaining enough progress to make a long browser transfer practical. Within a few days, I had built the first WolfP2P proof-of-concept around those needs.

Why the wolf? Ask a Gen Xer to name a peer-to-peer application, and eMule may come to mind. But a mule did not fit this product. It must be another animal—one that communicates directly, coordinates efficiently, and covers distance without unnecessary effort. A wolf felt right. WolfP2P it was.