AccessCORE License Studio

AccessCORE License Studio is built for software vendors issuing and operating licenses. The catalogue defines what can be sold, contracts record each customer’s terms, and signed tokens carry those terms to installed products.

Selecting a product opens its overview, releases, features, quotas, plans, and prices in one detail area. The product list stays on the left, while topic counts make the contents and scope of each product visible.

Each product is either sold in the store or by contract only. Turning store sales on checks for a public plan, a price, and a payment route for every priced currency. If anything is missing, the save is refused and the reason appears beneath the switch.

A contract records the customer, product, plan, features, quotas, seats, term, grace period, and release ceiling. Once a contract is saved, its product key can be issued from the same detail panel without leaving the page, and the panel’s tabs list the issued keys and the installations running on them.

Suspension preserves keys and seat assignments so the contract can resume with its existing allocations. Scheduled termination keeps the contract active until the chosen date. Maintenance renewal, suspension, and termination require confirmation of their impact.

The contract’s history tab lists suspensions, resumptions, terminations, and maintenance renewals newest first, each with the acting account, time, and stated reason. When a customer asks why a license stopped, the record provides the answer. The seat allowance cannot drop below the installations in use; surplus installations must be released or revoked first.

The store compares public plans by features, quotas, term, and price. Direct customer orders and operator-created contracts share the same product catalogue and sales definitions.

Each currency and payment-method pair maps to one payment route. PortOne V2 integration and direct bank-transfer settlement are supported, with gateway credentials configured separately from the routes used for sales.

Orders move through payment pending, deposit pending, paid, declined, expired, and cancelled states, with refunded orders gathered in their own list. Operators record bank-transfer deposits by hand, while virtual-account deposits are applied automatically from the information the payment gateway provides. Each paid order links to its contract, product key, and outgoing mail.

Private signing keys are managed by the issuing server; public verification keys are embedded in the customer product’s build. Setup can create the issuing identity and key, or use an existing key. Persisted private keys are encrypted.

Rotation begins by deploying products that contain the new public key. The previous key remains available for verification, and the console tracks installations still holding tokens issued under it.

Verification bundles, public-key files, and issuer certificate chains serve distinct purposes. Compromise reporting is paired with old-key installation tracking; reporting a leak does not itself immediately shut down legitimate existing licenses.