Why was the platform built this way?
Many licensing solutions are either built for a single store only, or are generic platforms that do not visually or technically separate merchant data. We believe "multi-merchant" means more than user accounts: it means clear boundaries for every API request and decision space for each merchant over their products, customers, and licenses—without one merchant ever seeing another's data, even by mistake.
That is why we explicitly separate the central platform admin interface (infrastructure, plans, onboarding approvals, public site settings) from the merchant dashboard, which always operates within your store's fixed scope in every session and secure call.
What do we offer technical merchants?
- A clear licensing path for digital products, including scenarios such as FiveM servers where verification must be tied to the server IP address.
- Discord integration as an operational channel: announcements, product-linked roles, support tickets, loyalty, and release alerts—depending on what your store plan allows.
- Documented HTTP interfaces for the storefront and license verification, with the principle that every sensitive operation carries the correct store context before execution.
How do we handle support and education?
The homepage summarizes the idea for new visitors; the blog and long-form guides are where operators find the details they need—from configuring scripts on the server to understanding request headers during license checks. We update these articles when important product behaviors change.
Privacy and terms for users
Whether you are a merchant or an end customer, our privacy policy and terms and conditions explain how data is processed and what is expected of you when using the service. For specific questions, use the contact or support channels shown on the site.