Pepper includes the application source for your licensed installation. The runtime uses Laravel and PHP, React with Inertia, TypeScript and Tailwind CSS. Blade templates render PDFs and email.
Install without a frontend build
The package includes production PHP dependencies and compiled assets. A normal buyer installation needs no Composer, Node.js, npm, Vite or Redis. Use PHP 8.4+ with SQLite 3.44+, MySQL 8.4 or MariaDB 10.11, 11.4 or 11.8 and configure HTTPS, email and cron.
Extend the business rules
Core document, customer and payment writes use Laravel actions. PHP calculates stored financial totals. Permission checks apply at the action boundary; a custom interface must preserve them.
Three invoice PDF layouts ship as Blade views. The package includes frontend source, locked build configuration, migrations and language files. Development tests and internal delivery tooling are not part of the buyer package.
Connect an external client
AI is optional. The owner can connect MCP and HTTP clients with expiring access to permitted records, exact previews and invoice drafts. Documented jobs prepare invoice drafts, explain overdue balances, read customer context, work with Sales and record project time. You confirm invoice issuance in Pepper. MCP clients can use browser sign-in. A client can issue a prepared document only after the delegated person approves it in Pepper. Sending, recording payments, exports and settings changes also run only after the person approves each exact change; see Approve sensitive steps. No model account is required. Read the Agent API category for tested clients, job sequences, field limits and retry behavior.
Installing for clients
Each client business needs its own production installation and licence. You may adapt the source for that installation and charge for a separate installation or maintenance service. Pepper does not host multiple client businesses inside one installation.
Agree who handles hosting, email, backups and updates before handover. Development and staging copies for that business can use the same licence.
Plan for updates
Keep changes in version control and rehearse them on staging. The Update page refuses modified application files. Reapply and verify custom work through a controlled update process while preserving business records and originals.
Read the customization guide before planning a source change. The technical manual, hosting requirements and licence terms cover the package and deployment conditions.