A marketing label is not a network design
A reverse proxy forwards client requests to another server, as the NGINX documentation explains. A supplier calling a software offer a “proxy” or “shared” licence does not establish that network design or define the rights being sold. Ask what licence arrangement applies to your specific product and server.
Verify the right to supply the licence
Check the seller, the contracting supplier and the applicable manufacturer agreement. The cPanel legal documents distinguish licensing rights and conditions. A reseller login, product logo or successful supplier API response does not by itself demonstrate manufacturer authorisation. Request written confirmation of the permitted server, account limits, verification route and who provides support. A low price proves neither legitimacy nor illegality.
Ask what happens when the service changes
Before relying on the licence, ask how software updates, IP changes, interruptions and renewal are handled. Establish what happens if the supplier stops providing the service and how you could move to another licence arrangement. Keep independent backups and record the accepted package conditions. Do not treat a shared-licence label as a security guarantee or permission to bypass software checks.
For example, a package may have a clear price but no written licensing authority, supplier-dependent updates and no exit procedure. Mark those three points as unresolved and request evidence before choosing a term. A second offer with documented answers can be compared on scope rather than its label.
Make the purchase decision on documented scope
Compare the product catalogue with the written answers, the terms of sale, renewal conditions and refund policy. Confirm compatibility before paying. If authority or scope remains unclear, ask support before ordering; an activation message alone does not resolve those questions. This guide is written by the store and does not certify any supplier as a manufacturer partner.
