Discord authentication system - Sell Project

You host one Python process. It runs the Discord bot and the API together and stores everything in a SQLite file on the same machine. No separate database. You create an application, upload a build, and generate keys with a duration. A customer redeems a key in Discord. The Windows loader sends the key and a hardware id, downloads the build, checks the hash, and starts it. If the key is revoked, expired, or bound to a different machine, the session stops. Resellers get their own commands. You turn an app on for a reseller and set how many keys they can make per day. Customers can see their licenses and reset a hardware id. Owners can ban a user, pull a key, upload a new build, and read an audit log. Replies that contain keys or hardware ids are only visible to the person who ran the command. The loader is a small C++ library. It talks to the API over HTTPS, verifies an Ed25519 session token, and keeps the build encrypted at rest with AES-256-GCM. A build can be an exe or a dll. There is a web dashboard that signs in with Discord. What you get: the bot, the API, the service layer, the C++ loader, the dashboard, tests, and deploy notes. You bring a Discord bot token and a host that stays on and has a disk. There are no customers and no revenue.