Buyer guide · Licensing
Code access and open-source licensing are different decisions.
Reward Loyalty includes application source under a commercial license. This guide explains what that permits and where open-source software follows another model.
- Reward Loyalty
- Commercial source-available license
- Code access
- Included for the license holder
- Key restriction
- No source redistribution
Short answer
Start with the operating model.
Open source describes license rights, not whether code is visible or software has a price. Reward Loyalty is source-available under a commercial license: the license holder receives the application source and may modify the licensed installation, while redistribution remains restricted. Compare the exact rights, the completeness of the shipped product, and who will fund maintenance after deployment.
Connect those license rights to the day-to-day responsibilities of owning the installation.
Rights and cost
Do not treat source access as a free operating model.
A license can grant useful control while the installation still needs infrastructure, security, testing, and maintenance.
See the study’s measured license line and separate labor assumptions for one way to keep a public software price apart from the work needed to operate it.
Use the current source-access and installation terms before relying on modification, deployment, update, or redistribution rights.
Then place those rights inside how deployment control changes the SaaS comparison. A managed vendor may still be the better fit when the buyer lacks operating capacity or needs a named integration.
Decision criteria
What the decision changes.
These choices affect configuration, staff work, economics, support, and the customer promise.
License rights
Read modification, deployment, redistribution, derivative-work, and separate-installation terms instead of relying on “open” in a product name.
Product completeness
Compare a maintained application with repositories, libraries, or headless engines that need more customer and operator interfaces.
Maintenance source
Decide who funds updates, security work, framework changes, documentation, and support after deployment.
Definitions
Use the right term for the right promise.
Clear licensing language prevents buyers from assuming rights the contract does not grant.
Open-source software
An OSI-approved license grants defined rights to use, inspect, modify, and redistribute under its terms.
Source-available software
The buyer can inspect and modify source under a commercial license that may restrict redistribution or other uses.
Managed proprietary SaaS
The customer uses a vendor-operated service. The vendor keeps the application source.
Procurement
Review more than the repository.
A codebase still needs a usable product and a sustainable maintenance path.
-
1
Read the current license
Confirm installation scope, source rights, restrictions, renewal, and what happens when renewal lapses.
-
2
Review the shipped application
Check the member, staff, partner, and admin workflows required by the project.
-
3
Assess extension cost
Identify the changes that fit the architecture and the work that would turn the product into a different system.
-
4
Plan maintenance
Name the owner of updates, custom merge work, testing, security, and deployment.
Maintenance model
Price the path after the first deployment.
Source rights matter most when the team can keep the resulting application secure and supportable.
Upstream maintenance
Check who publishes releases, security fixes, migration notes, and current documentation, and what continued access costs.
Local changes
Record each source change, its tests, its data impact, and the merge work future releases will require.
Exit and continuity
Confirm what the organization may keep running, modify, export, or redistribute if support, renewal, or the vendor relationship ends.
Product and operating limits
Keep the recommendation inside the product boundary.
- Source access does not grant open-source redistribution rights.
- An open-source license does not guarantee a complete product, support service, active maintenance, or low implementation cost.
- Commercial license terms can change. Use the current purchase and legal pages before relying on a right or restriction.
Implementation guides
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.