The KeyAuth alternative

What PWF Auth is

A licence server for desktop programs you sell. You make keys in the panel, your program signs in with the key the customer typed, the key locks to that PC, and every running copy checks in every 30 seconds. Ban, pause or end a key and the app closes on its next check-in. Every request and reply is encrypted, and every reply is signed by the server and checked inside your app, so a fake server cannot unlock it

Seven lines in your app

C# with the PWFAuth NuGet package. Python (pwfauth), C++ work the same way, and the SDK generator writes a client for VB.NET, JavaScript, Java, Kotlin, Android, PHP and Dart

var client = new PwfClient(AppSecret);
client.SessionEnded += (s, e) => Application.Exit();   // banned, paused, expired: the app closes

PwfResponse login = await client.LoginAsync(licenseKey);
if (!login.Success) { ShowError(login.Message); return; }

client.StartHeartbeat();                                // checks in every 30 seconds

PWF Auth vs KeyAuth

PWF Auth's column is what it does today. KeyAuth's column is limited to widely known, public facts as of October 2026; plans and features change, so check KeyAuth's own site for its current offer. KeyAuth is a trademark of its owner; PWF Auth is not affiliated with it

Why developers pick PWF Auth

• Every feature open todayKeys, customer accounts, resellers, updates, texts and the Telegram bot are open to every account today. Paid plans will come later, and you will hear about them well in advance
• A kill switch that really closes the appEvery copy checks in every 30 seconds. Refund, chargeback or a key posted in a group: ban it and the app closes on that PC, with your own message
• Replies nobody can fakeRequests and replies are encrypted with AES-256 and HMAC, and every reply carries the server's RSA signature, checked inside your app. An emulated server is refused
• Resellers with their own portalGive resellers credits and their own prices; they make keys in their own portal, and you see every sale
• Telegram, built inApprove sign-ins from your phone, get alerts, and give each app its own bot where buyers claim keys and your team manages them
• Ready for your languageNuGet PWFAuth for C# and VB.NET, pwfauth on PyPI, a C++ client, and an SDK generator for JavaScript, Java, Kotlin, Android, PHP and Dart

Moving over from KeyAuth

Your customers keep the keys they bought. Most apps move in an afternoon

1. Create your appMake an account, add your application and copy its secret
2. Bring your keysIn Licences → Import, paste the keys your customers already have, one per line, in any format. Pick their length and how many PCs each may use; each key starts on its next sign-in
3. Swap the SDKReplace the KeyAuth calls with LoginAsync(key) and StartHeartbeat(), and close the app in SessionEnded. See Getting started.
4. Ship the updatePublish the new build in Updates and make it required, so older builds ask for it

KeyAuth alternative: questions