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.
You own a licensed copy, not the intellectual property in the application. You may modify it for your licensed installation. You may not redistribute the application source or installable package. Someone must maintain each change.
Separate the four parts of the purchase
| Part | Pepper's terms |
|---|---|
| First year | $199 for one production installation, a perpetual licence, full source, and one year of updates and support |
| Continued use | A perpetual license to keep using the purchased software |
| Source code | Included for inspection and changes within your commercial licence |
| Updates and support | Included for one year, then renew automatically at $199/year unless you cancel |
Cancel anytime to stop future charges. Downloads, updates and support remain available until the paid period ends; your downloaded copy keeps working after that. 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 and selling widget access to multiple customer businesses on it. Customer widget workspaces keep each business’s widgets and staff separate. You may not publish or redistribute the application source or installable package.
Development and staging copies can support that installation under the same license when they do not serve live business operations. Each additional production installation needs its own license.
For example, a developer can adapt the invoice presentation for an agency's installation and charge for that work. Selling those businesses widget access on the licensed installation is also permitted. Redistributing the modified application source or installable package is prohibited.
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.