Why RoAuth is closing
I have decided RoAuth is closing down due to over £100 (roughly $130) in refunded Stripe payments from users in the last 3 days.
I am not willing to operate RoAuth at a loss, so I will be closing it down.
If someone would want to cover the lost expenses then I would keep it up, but I am not willing to cover it myself as I am frustrated by it.
Timeline
RoAuth shuts down on 26 June 2026. You have until then to collect your data and move to another auth provider.
After shutdown, the dashboard, API, loaders, and bot will stop working. Export everything you need before the deadline.
Export your data
If you are signed in, use the buttons below to download JSON files or a single ZIP with all projects, keys, users, stats, and settings.
What is included
Each export contains the following for every project you own:
- License keys (key string, Discord ID, HWID, expiry, ban state, notes, execution counts)
- Users (Discord IDs tied to keys and usage)
- Project stats (execution totals if you need historical counts)
- Settings (project configuration such as HWID reset cooldown)
Public API (optional)
Prefer automation or integrating with your own tooling? Create a read key on Public API and call https://www.roauth.co/api/v1 with Authorization: Bearer YOUR_API_KEY. Full reference: Public API documentation.
Example: list keys for a project (paginate with limit and offset):
curl -s "https://www.roauth.co/api/v1/projects/PROJECT_ID/keys?limit=100&offset=0" \ -H "Authorization: Bearer YOUR_API_KEY" > keys.json
Migrate to another service
Import keys and users into your new auth provider using the JSON you exported. Map fields as closely as possible: Discord ID, HWID, expiry timestamp, and key string (or issue new keys and DM customers).
Update your Discord bot panels and any automation that pointed at RoAuth. Test on a staging key before you cut over.