Two-way file transfer
A two-panel window: send or fetch, folders included, by drag and drop. Progress and errors are reported item by item.
Remote support for Windows
Connect to your customer's screen. Let the server in between see nothing.
End-to-end encrypted remote desktop, two-way file transfer, chat and voice. Keys are generated only at the two ends; the rendezvous server cannot decrypt what it carries — even though it is our server.
One file · no installation · version 1.3
deskwarp
While this window is open, people can connect to you.
This computer
Your number
548 882 541
Password
cygki3
Ready to connect
Remote computer
Number
Password
Connect
Architecture
The server in between is a postman, not a reader.
Both sides sit behind a router, so something has to introduce them. We run that middleman — but we cannot decrypt what it carries either: keys are generated only at the endpoints.
encrypted data flow
where the keys are known
One application, both directions: every install can connect and be connected to.
How it works
Three steps, no installation.
-
STEP 1
Your customer opens the app
A single file, no installer. On launch it shows a 9-digit number and a 6-character password. The password is regenerated at every launch and never written to disk.
-
STEP 2
They read you the number
You type that number and password into the right-hand side of the same app. There is no separate "customer edition"; every install can connect and be connected to.
-
STEP 3
The session opens
Keys are generated at both ends and the session is encrypted. A banner naming whoever connected appears on the customer's screen and stays there for the whole session. While it runs you can chat and, if you want, talk — no need to keep a phone line open.
Security
Encryption is a specification here, not a marketing line.
The app is written in .NET 9 and uses no external cryptography library. The methods, stated plainly:
Key exchange
ECDH on the NIST P-256 curve. The shared secret exists only at the two ends.
Data encryption
AES-256-GCM. A separate key per direction and a counter-based nonce.
Password verification
A key derived with PBKDF2 and an HMAC over the handshake transcript. A party that does not know the password cannot produce a valid confirmation, so the relay cannot put itself in the middle.
Replay attacks
Counter order is mandatory; a repeated or out-of-order packet is rejected.
Password lifetime
Regenerated at every launch, never written to disk, refreshed with one click.
What the relay sees
Only the session number and encrypted bytes. Screen images, keystrokes, file contents, chat and voice — all of it is meaningless data to the relay.
Transparency
We do not try to hide that you are connected.
Features
The things a support session actually needs.
Clipboard sharing
Text you copy crosses over. It stops the moment the permission is turned off.
Adjustable quality
Low, medium, high. Choose smoothness on a weak link, sharpness on a good one.
Full screen and screenshots
F11 for full screen, one key for a PNG capture. Run the Task Manager shortcut on the far side.
Permanent installation
Install it as a Windows service; the computer can be reached with a fixed number even with no window open. The banner still appears.
No dependencies
No external libraries, a single executable. Easy to audit, easy to hand out.
Turkish and English
The interface language follows Windows and can be set by hand. Each side sees its own language; new languages are added with a single JSON file.
Connection history
The numbers you connected to stay in a list and can be named. If you choose to store the password, Windows' own encryption protects it.
UAC and the lock screen
The image does not go dark when an administrator prompt or the lock screen appears. Installation and settings work do not stall halfway.
Text chat
Type to each other during the session — a number, an error message, an address — without hanging up the phone; messages travel through the same encrypted channel.
Voice
Push to talk or always on. On a weak link the audio quality drops by itself and climbs back when the link recovers. No need to keep a phone line open.
The far side's own sound
Hear what comes out of the customer's computer too: error beeps, video, music. Some faults are not visible on screen but are audible.
Business
We run the server. We cannot see your traffic either.
That is not a promise of trust but a consequence of the design: the session key is generated at the two ends and never reaches the server. All the rendezvous server holds is a support number and encrypted bytes it cannot open.
Under your own name. When you connect, the banner on the customer's screen shows your company name, not DeskWarp.
No server to run. Setup, certificate renewal and updates are ours. On your side there is a single file.
No installation needed. You send the customer one file; they double-click it and read out the number. If you need permanent access, it can be installed as a Windows service.
Old builds do not linger in the field. When a build is withdrawn it is refused server-side; installations that were never updated cannot connect.
For business licensing and pricing, write to info@eneryazilim.com.
Download
Try it on your next support call.
Download one file, double-click it, share the number. No installation, no sign-up, no account.
Windows 10 and later · 64-bit · version 1.3
If it does not run, or you need a different build: all versions and architectures
To verify that the file you downloaded came from us, the SHA-256 digests: Get-FileHash DeskWarp.exe