Applications
Owner ID
API v1
About Owner ID
Your public account identifier. Use it with the application name in your library configuration.
| Application | Status | Open |
|---|
No applications found.
Application settings
Application ID:Invites
Active invitations
0
Workspace owners
0
Active workspaces
0
Invitations
| Recipient / label | Status | Expires |
|---|
No invites yet.
Invite code
Copy it now. The code cannot be shown again.
Ask the recipient to choose Create an account and enter this code. It is not included in a URL.
Workspace owners
Workspace owners
Separate databases| Workspace / owner | Access |
|---|
Owners appear here after they redeem an invitation.
Select an owner to manage their permissions.
Profiles
Community Discord notifications
Author names are supplied by uploaders and are not verified identities. Hiding a profile removes it from community browsing and loading.
Products
Products
0
Subscription-based access
Live releases
0
Available to eligible customers
Stored files
0 MB
0 retained versions
Your products
Customers need a valid licence, matching HWID and an active subscription allowed for the product. Encrypted delivery uses your managed authentication.
Loader updates
Publish a loader
Published version
—
No loader published yet
Download size
—
Verified before installation
Current release notes
No release published.
Loader version history
Choose the active version here. Customers see the selected release in their normal update screen, including when you restore an older version. Previous EXEs are kept for 14 days from their original upload; the active EXE is always kept. Restoring does not reset the upload date. Automatic rollback requires the updated updater in both EXEs; older compiled builds cannot gain rollback support remotely.
Licences
Active licences
—
Average daily logins
—
Successful logins · Last 30 days
Keys created
0
Permanent register
Unused keys
0
Duration starts on activation
Banned / archived
0
Access blocked
Created this week
0
During the last seven days
About these counts
Counts activated keys with at least one unexpired, unpaused subscription, including lifetime. Unused, banned, archived and held keys are excluded; customers do not need to be online. Daily averages include zero-login days since tracking began.
ONE LOGIN · MULTIPLE PRODUCTS
Checking signing configuration
Application access
Your EXE signs into this application once. The VPS returns only products allowed by the key's active subscription names, then rechecks access when the customer selects one.
Menu numbers are display choices. Access uses exact subscription names, with no numeric level hierarchy. Saving settings revokes existing application sessions.
Application flow
Sign in once
Login(key)
Build the numbered menu
Result.products
Verify the chosen product
SelectProduct(productId)
Use Check() periodically. Sessions last at most 15 minutes. Managed keys authorize encrypted customer downloads.
Product-specific sign-in
Enable managed clients that sign into one product directly. Application sign-in uses the product selection above. Both use the same managed authentication and encrypted downloads.
Keys
0 selected
| Licence key / reference | Status | Subscriptions / duration | HWID |
|---|
No keys yet
One-hour trials Loading
Pause new and resumed trials and end current trial sessions. Paid licences and shared trial keys stay active. Trial expiry times keep running.
Network access VPN CHECKS
Check customer connections for VPNs, proxies and Tor. The server checks sign-ins, registrations, redemptions and protected requests, including DLL downloads and decryption-key release. Your admin panel and loader updates remain accessible.
Device binding HARDWARE CHECKS
Choose which identifiers keys are locked to. When you enable another check, its missing value is enrolled on the next successful sign-in with the updated library. Collected values are retained when a check is disabled.
Recent batches
1–100 KEYS EACHKey receipts can be recovered for 10 minutes in the owner session that created them.
Licence activity
Generated and imported licences share this permanent register.
Statistics
Preview data · These example counts are not live customer traffic.
Loading statistics…
ACTIVE LICENCES
0
Successful downloads
0
Completed server transfers
Failed requests
0
Denied or interrupted attempts
Success rate
—
Share of selected outcomes
Total attempts
0
Across all products
Average daily logins
—
Successful logins per tracked day
Keys used · all time
0
Generated and imported licences
Downloads over time
No matching attempts recorded yet. Try another date range or product.
By product
| Product | Successful | Failed | Success rate | Active licences |
|---|
Failure reasons
By subscription
| Subscription | Successful | Failed | Success rate | Active licences |
|---|
Select Logins to see countries. Trials have their own country breakdown.
Top 10 countries
Countries
Hover or focus a country for details.
The daily login average follows the selected dates and products (and subscriptions in Logins), includes zero-login days, and always counts successful logins regardless of the outcome or download-stage filter.
Counts each generated or imported key once after activation or account redemption, including expired, banned and archived keys. Shared and one-hour trials are tracked separately. This all-time count ignores date, product and subscription filters.
Counts represent requests, not unique customers. Success means the server finished sending the file. All stages includes failed authorization checks; successful authorizations are not counted as downloads.
Current count uses the applied product and subscription filters, regardless of date or outcome. Customers do not need to be online. Unused, banned, archived and held keys are excluded. Each key counts once overall; product and subscription rows may overlap.Share of distinct licences with successful logins in the selected dates, products and subscriptions. Each key uses its latest matching login country. The outcome filter does not apply; shared trial keys count as one licence.
Highlighted countries have users in this selection; grey countries have no recorded users. Coverage is a share of 249 ISO countries and territories, not land area or population.
IP locations are estimates and may reflect VPNs. IP Geolocation by DB-IP. Map: Natural Earth.
Trials redeemed
0
All time · one per device
Redeemed in period
0
Selected UTC dates
Active now
0
Unexpired and allowed
Expired
0
All time
Average per day
—
Since first redemption
Countries reached
0
Selected period · IP estimate
Shared trial keys
PCs on active shared trials
0
Distinct PCs across active shared keys
Active shared keys
0
Unexpired and allowed
| Shared trial | Status | Distinct PCs recorded | First seen in period |
|---|
New trials over time
Hover or use arrow keys for exact counts.
No trials were redeemed in this period.
Top 10 trial countries
Each redeemed trial device counts once in the selected period. The latest recorded successful login location in that period is used; unknown locations remain in the percentage denominator.
Trial reach
Hover or focus a country for details.
Countries are estimates from IP addresses and may reflect VPNs. Map: Natural Earth. IP geolocation: DB-IP.
Logs
Saved URLs remain on the VPS. DLL auth notifications send without screenshots or credentials. Loader authentication and delivery logs attach matching, consented screenshots when available. Authentication logs include the full attempted key when supplied; people who can read a Discord channel can read that key. If no screenshot arrives, the log says so.
Bans
Countries are estimated from recorded IPs or the latest successful login. IP Geolocation by DB-IP.
False-positive reasons
Only debugger reports can be suppressed. Matching is exact and case-sensitive, for everyone. Re-enable reports here at any time. Existing bans remain active.
Pending debugger reports
Global reason rules
Activity
Account
Change password
Enter your current password to choose a new one. Updating it signs out all admin sessions.
Loader account recovery
Search by username, then generate a one-time code to give to that customer after checking proof of purchase. The code has no time limit, works once, and is replaced if you generate another. The customer enters it in the loader with a new password.
Discord licence bot
Not configuredManage licences from your Discord server. Server members can use /reset with a full licence key. /licence and /account recovery commands are restricted to your owner user ID. Replies are private.
Connect Discord
- Create an application in the Discord Developer Portal. Save its details above. In Discord, enable Developer Mode to copy your user and server IDs.
- Install in the saved Discord server Save an application and server ID to get your install link. Use a server you own or administer. The bot needs Manage Channels, Manage Roles and Manage Server for /setup. Put its role above reseller roles. Do not grant Administrator.
- In General Information, save this as the Interactions Endpoint URL:
- Paste the token from the Developer Portal's Bot page below, then register commands. The token is used for this request and is not stored.
- Enable licence commands above, save, then try
/licence lookupin the saved server.
/reset key: lets any server member reset an activated licence using its full key. Keys are not linked to Discord identities; anyone possessing a key can reset it. /licence (owner only): lookup · reset (HWID) · ban · unban · extend · pause · resume · revoke · delete · restore. Extend, pause and resume target one named subscription on an activated licence. Delete archives the key and revokes access; restore makes it available again. Hours and duration multipliers are supported.
Automatic reseller channels
Enable Server Members Intent in Developer Portal → Bot. Save the bot token below to keep join handling and update announcements connected. This token is encrypted on the VPS until removed; it is never returned to the page.
Owner-only /setup creates a private admin channel and posts the complete deletion list there. You must confirm before old channels, threads and their history are permanently deleted. It revokes existing invites and removes invite creation from editable roles. Community servers, vanity invites and other administrators must be resolved first.
After setup, existing members and new joins each get a private reseller channel, visible to that member, you and the bot. Every published product update is sent there using the product’s embed/plain-text setting. Other Discord administrators always bypass channel privacy; do not grant reseller accounts Administrator.