Overview
A snapshot of your application.
Products
The things you sell. Each product can have several pricing tiers.
Your products
A license key always unlocks exactly one product.
Builds
The actual file customers download — your DLL or EXE. Upload a new one and it replaces the live build instantly.
Builds are encrypted the moment they arrive and never stored in the clear. Each download is re-encrypted under a one-time key, so a captured file is useless without that download's key.
Pricing tiers
How long access lasts, and what it costs. "1 Month", "Lifetime".
License keys
Generate keys to sell. A customer redeems one to unlock a product.
Issued keys
Keys are stored hashed — shown once at creation and never again.
Customers
People who redeemed a key and can log into your software.
Accounts
Each account locks to one machine on first login.
Active access
Who currently has access to what, and when it runs out.
Live sessions
Clients running right now. One session per customer — a second login kicks the first, which is how key sharing becomes visible.
Activity log
Every login, key redemption and admin action. Append-only.
Connect your app
What your client software needs to talk to this server.
Connection details
Paste these into your client.
—
—
This is an identifier, not a password. It ships inside your binary and anyone can extract it — that is expected and safe. Your customer's password and their license key are the secrets.
—Desktop clients must send a matching version or the server refuses the login. That is your forced-update switch.
Login request
What your client sends to authenticate a customer.
How it fits together
- Application — your software business. Holds the keys. You need one.
- Product — a thing you sell. A key unlocks exactly one.
- Tier — duration and price. "1 Month", "Lifetime".
- License key — what you sell. Redeemed once, then dead.
- Customer — an account in your software, locked to one machine.
- Access — what a customer unlocked, and its expiry.
- Session — a client running right now.