Self-hosted loyalty software with full source.
Run your loyalty programs on infrastructure you choose. Reward Loyalty includes the customer wallet, staff tools and business dashboards, with a one-time license and full Laravel source.
- You control
- Source, hosting, data location
- You operate
- Mail, backups, security, updates
- Best fit
- Agencies and capable operators
What you own and run.
Reward Loyalty is self-hosted customer loyalty software sold with a one-time license and full Laravel source. Run points, digital stamp cards, vouchers and prepaid passes for one business or several clients on your installation. You choose the host and data location and take responsibility for mail, backups, security and updates.
A complete loyalty system on your server.
Reward Loyalty ships the member wallet, staff counter tools, business dashboard and installation administration together. You choose the host and data location and receive the full application source.
Points, stamps and prepaid passes
Run points cards with rewards and tiers, stamp cards for repeat purchases, vouchers and prepaid visits, access or credit. Each business configures its own programs.
See the loyalty workflowsSeveral businesses on one installation
One license has no client-business cap. Each partner sees its own members and activity. Separate production installations need separate licenses; capacity depends on the server you provide.
Review the multi-business modelSource and integration access
The license includes unobfuscated Laravel source. Use the documented APIs and signed outbound webhooks for supported integration work. Shopify and WooCommerce integrations are in early access.
Inspect the application and extension pathsAn installation your team maintains
Prepare compatible hosting, HTTPS, a database and email, then run the browser installer. The standard setup needs no cron or separate queue worker. Your team maintains backups, security, monitoring and updates and supports the businesses using the service.
Inspect the browser installation steps
One license, unlimited client businesses
$349 once for one installation, including full source and 12 months of updates and product support. Keep running your last version if you skip the optional $99 yearly renewal. You pay for hosting and email delivery and maintain the installation.
What the decision changes.
These choices affect configuration, staff work, economics, support, and the customer promise.
Operational ownership
Name the person or provider who will maintain the server, mail delivery, backups, monitoring, and release process.
Data location
Choose the infrastructure and subprocessors that match the organization’s privacy, security, and contractual needs.
Source-level change
Use source access for work that creates real value, and keep a record of changes that future updates must preserve.
Count the work that remains after the license.
A one-time software license changes billing. It does not remove the operating layer.
Software
The current license and renewal terms come from the pricing page. Keep them out of static calculations.
Infrastructure
Budget for the server, transactional email, backups, monitoring, storage, and any delivery service the installation uses.
People
Include installation, updates, incident response, integration work, and support for the businesses using the system.
Prove recovery before inviting customers.
A calm self-hosted launch starts with staging, mail, backups, and monitoring before the first program goes live.
-
1
Meet the current requirements
Use the maintained requirements page rather than an old framework or runtime number copied into a proposal.
-
2
Install on a staging address
Test configuration, mail, scheduled work, uploads, and the intended loyalty flow without production customer data.
-
3
Create and restore a backup
A backup policy is incomplete until the operator has restored one in a safe environment.
-
4
Plan the update window
Read the changelog, preserve custom work, and rehearse each update before it reaches production.
Keep the recommendation inside the product boundary.
- Reward Loyalty is software you operate. It is not a managed hosting, monitoring, backup, or incident-response service.
- Source changes can create update work. Keep customizations small, documented, and tested against new releases.
- Self-hosting can reduce third-party product exposure. It does not remove every processor or make an insecure installation compliant.
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.