Pepper includes the full application source under a commercial license. You can inspect the code, run the software on your hosting and change it for your licensed installation. That can matter when an invoice layout, integration or internal process needs a change your developer can maintain.
Source access gives you control over the installation. It also leaves someone with the job of understanding and maintaining each change.
Separate the four parts of the purchase
| Part | Pepper's terms |
|---|---|
| First year | $99 for a perpetual licence and one production installation serving one business |
| Continued use | A perpetual license to keep using the purchased software |
| Update access | Renews automatically at $199/year; cancel anytime. Installed use continues after download access ends |
| Product support | Six months, unless the purchase agreement says otherwise |
An update renewal does not extend product support. Hosting, email and your maintenance work remain separate. Read the full terms for license and refund conditions.
Know the rights you need
Pepper is source available. Its commercial license permits changes for the licensed installation; it does not grant permission to publish or redistribute the application as a product, template, package or service.
Development and staging copies can support that installation under the same license when they do not serve live business operations. A separate client business needs a separate production installation and license.
For example, a developer can adapt the invoice presentation for an agency's installation and charge for that work. Supplying that modified application to several client businesses under one license would exceed the stated scope. Resolve any unusual use with the seller before building it.
Plan for the first update before the first change
Keep a clean copy of the purchased source and record your changes in version control. Make each change for a specific requirement. Use a test installation to check both the modified behavior and the invoices or exports it touches.
The built-in updater refuses modified application files. A custom installation needs a managed update process that compares the new release with your changes and preserves business records. Source access does not make an update merge automatic.
Product support covers defects in supplied features and the documented installation and update procedures. It excludes custom development and debugging modified code. Your developer needs time for that work after the initial customization.
Test the reason you want source access
Write down the first change you expect to make. Have the person who will maintain it inspect the technical stack, hosting requirements and customization guide.
If the requirement is a payment gateway, bookkeeping ledger or customer portal, buying the source does not make that feature part of Pepper. Choose based on the released product and budget any separate development as its own project.