Architecture overview
Products
Features or tiers within apps
App users
Your application's end-users
Applications
An application represents your software project (e.g., a game, tool, or service). Each application has:
| Property | Description |
|---|
| Unique API key | Prefix ap_. Used by your client to identify the app. |
| Authentication mode | Choose between key-based or username/password. |
| Security settings | HWID binding, session timeout, max concurrent sessions. |
| Team members | Collaborate with others on your project. |
Products
A product is a feature, tier, or module within your application. Users need a subscription to access product resources.
Example structure
My App (application)
Basic Version (product)
Premium Version (product)
VIP Version (product)
Each product can have its own files, folders, and configuration variables.
App users
App users are your application's end-users (different from dashboard users).
Key-based mode
Users authenticate with a unique key (e.g., MYAPP-1234-5678-ABCD-EFGH).
- Simple distribution
- No email required
- Perfect for simple licenses
Username and password mode
Users register with email/username and password.
- Traditional login flow
- Password recovery
- Email change capability
- Better for customer accounts
Subscriptions
A subscription links an app user to a product, granting them access.
Subscription properties
| Property | Description |
|---|
| Status | active, expired, paused |
| Expiry date | Set an expiration or leave empty for lifetime access. |
| Pause feature | Temporarily freeze subscriptions (time left preserved). |
| Download tracking | Monitor file download counts. |