FAQ
OsDot Solutions currently offers three standard commercial software license tiers, each with different deployment, resale and activation rights. The Single Site Personal / Business license is intended for one production installation for your own personal or business use and does not include standalone resale rights. The Multi-Site Commercial license covers multiple permitted installations up to a finite activation limit and may support eligible client deployments, but it does not include reseller rights. The Non-Transferable Resell Rights + White-Label license provides the broadest standard branding and resale permissions, subject to the applicable product and license restrictions.
Activation links an OsDot installation to the license you purchased: install the product according to its documentation, open its licensing or activation area, enter the license information for your purchase and confirm that the product reports a successful activation. Production activations count against a finite limit for your license tier: 1 for Single Site Personal / Business, 5 for Multi-Site Commercial and 25 for Non-Transferable Resell Rights + White-Label. Unless a product states otherwise, this limit applies to licensed production installations, not to the number of users, customer accounts, transactions or database records inside the application. Exact screens and steps differ between products, so follow the documentation for the software you purchased.
Moving a licensed OsDot installation to a new production domain, server or host should be handled so the replacement installation stays within the limits of your purchased license. The recommended sequence is to prepare the new environment, back up your application and data, deactivate or release the license on the old production installation where supported, move or install the product, activate the license on the new installation, and verify it before retiring the old environment. Moving does not change your license rights or activation limit, and an automatic license reset or domain transfer should not be assumed. If you can no longer access the old installation, contact OsDot Support for guidance.
Approved local, staging or test installations may be treated differently from counted production activations where the OsDot licensing configuration for the product and environment permits it. This is not a guarantee that every test domain, subdomain, server or publicly accessible installation will be excluded from the production count. Staging or testing environments must not be used to bypass production activation limits, and if you are unsure how an environment will be treated, contact OsDot Support with the product and environment details.
A valid purchased OsDot software usage license does not automatically expire after one year. Standard OsDot commercial software uses a one-time perpetual software usage license, and the purchase normally includes one year of updates and support; these are separate entitlements. After the included updates and support period ends, continued updates or support may require renewal where applicable, but that alone does not terminate an otherwise valid usage license. Perpetual usage is not a promise of lifetime updates, lifetime support, guaranteed future compatibility or unlimited production activations.
Sign in to the same OsDot account you used for the purchase or membership, then look in the area of your account where purchases, orders, downloads or license information are shown for that product. Exact labels can change, so follow the options currently shown in your account and use the license information for the specific product and license tier you bought. Keep license keys confidential and never post them publicly or include them in public screenshots. If something is missing, confirm you are signed in to the correct account, then contact OsDot Support with your order details.
There are three membership levels. Free Member is a no-cost level that gives access to products OsDot Solutions has intentionally included in its Free Downloads offering, such as selected free, lite, trial or promotional products. The OsDot Pro Annual Membership is a paid membership that renews annually unless cancelled, while the OsDot Pro Lifetime Membership is a one-time paid membership with no recurring membership fee; both include Free Member benefits plus 50% off eligible OsDot software products. Membership is separate from software licensing, so it does not grant a license for every OsDot product or change the rights of any license you buy.
Members with an eligible OsDot Pro Annual Membership or OsDot Pro Lifetime Membership receive 50% off eligible OsDot software products while their membership is applicable; Free Member does not include this discount. The discount does not automatically apply to professional services or add-ons such as installation, customization, branding, Android or iOS deployment, app or payment gateway configuration, migration and hosting assistance, which remain full price unless explicitly stated otherwise. To confirm eligibility, sign in with your active Pro membership and rely on the price shown on the product page or at checkout. A discounted price does not change or expand the rights of the software license you buy.
Reseller rights are available under the Non-Transferable Resell Rights + White-Label license; the Single Site and Multi-Site Commercial licenses do not include reseller rights. Under that tier, where the product and license allow it, you may resell the resulting software, apply permitted white-label branding and deploy it commercially within a finite limit of 25 production activations, subject to product-specific restrictions. The reseller entitlement itself is non-transferable, so your customers do not automatically gain the right to resell, and white-labeling does not transfer ownership or authorship of the underlying OsDot intellectual property.
OsDot Solutions provides a structured support path: start with the OsDot Documentation, use the OsDot AI support assistant if the documentation does not fully answer your question, and escalate unresolved issues through the OsDot Support ticket system where your purchase or support entitlement includes support. Standard product support covers matters such as documented installation issues, licensing or activation questions, configuration problems and product troubleshooting. Professional services such as installation, branding, deployment or migration assistance are separate and may have separate charges, and substantial changes such as custom features or third-party integrations are handled through a Request a Quote process. When asking for help, never send passwords, private keys, API secrets or other authentication credentials.
Because OsDots.com offers non-tangible digital goods with immediate access, all sales are final and refunds are not issued once the order is completed and the product download link is sent. Refund requests are honored where a specific product explicitly states full or partial refund terms, for non-delivery of the product, and for download or unzipping problems; non-delivery claims must be submitted within 7 days of placing the order, and download or unzipping claims within 7 days. Refunds are not given for incompatibility with third-party software other than what is specified as compatible on the product’s sales page. If you have questions about whether a product is right for you, email mail@osdots.com before purchasing.
Requirements vary by product, so always check the System Requirements and Installation documentation for the specific software you purchased; there is no single PHP version, database version or server specification for every OsDot product. A typical OsDot PHP/MySQL web application may need a supported PHP version, a compatible MySQL-family database where required, HTTPS/SSL for production, the required PHP extensions, sufficient resources, and cron support if the product uses scheduled jobs. Shared hosting may suit some products if it meets all of their requirements, while a VPS, cloud or managed server may be more appropriate when more resources or server-level configuration are needed.
