Everything PWF Auth does, explained

Getting started From a new account to a protected app in six steps How protection works Sessions, the heartbeat, machine binding and how fast a ban reaches the app

Dashboard Getting started, alerts, the cards, who is online and what happened lately Applications One app per program you sell: its secret, version, trial and rules Licences Generate, import, search, extend, pause, ban and export keys Users Customer accounts: sign-in with a username and password, sign-up and its settings Sessions Who is running your app right now, and how to sign anyone out HWID resets Customers moving to a new PC: requests, approvals and self-service Rules Refuse an address, a range, a machine, a country, a network or VPNs before the key is even looked at Team Let people help with an app from their own account: roles, permissions, a daily limit and an activity log Resellers People who sell your keys: credits, prices, refunds and their portal Reseller portal For resellers: make keys, add time, credits and your account Telegram bot Your own bot for your app: customers claim keys, your team manages them, a buyers' group Discord bot PWF Auth's bot in your Discord server: customers claim keys, your staff manage them, a buyer role Stores SellAuth, Stripe, Shoppex or your own site: paid orders get their keys at once Texts & slides Words and announcement slides your app shows, changed without a new build User variables Small values your program keeps on the server for each customer: settings, progress, flags Updates Ship a new build: upload, publish, roll out and make it required Your account & security Profile, two-step sign-in, the Telegram bot and signed-in browsers

SDK generator One ready client file in C#, VB.NET, Python, JavaScript, Java, Kotlin, Android, PHP, Dart, C++ or Delphi C# and VB.NET Add licensing to a .NET app with the PWFAuth NuGet package Developer API API keys for your own bot, store or server: make, look up, reset, ban and delete keys Webhooks Your server or a Discord channel hears about keys, sign-ups and orders the moment they happen API reference Every endpoint, the encrypted envelope and signed replies, for writing your own client Error codes Every code the API answers with, and what to tell the customer