Choose your hosting.
Use your own domain and HTTPS, with PHP 8.4 or later and SQLite, MySQL 8.4 or a supported MariaDB release. Your host or developer can check the requirements with you.
Check the requirementsSelf-hosting and ownership
Your server.
Your say.
Put Pepper on hosting you choose. Keep the source and decide who gets access, with the upkeep in your hands.
Need a custom platform built and maintained? Explore tailored platforms.
- Your records
- In your database.
Customer details, documents and evidence live in your installation.
- Your software
- The full source.
Read, change and maintain the code under a commercial license.
- Your license
- Yours to keep.
One production installation. Continued use does not expire when update access ends. Read the full licence scope.
From download to daily use
A setup you
can look after.
The documentation covers installation and everyday care. Bring your developer or hosting partner if you want help.
Install your copy.
The package includes dependencies and built frontend assets. Follow the installer, add your company details and configure email and scheduled tasks.
Read the installation guideKeep it in good order.
Keep the server and application updated. Export records and files together from the browser. Import a backup into a fresh installation and verify it before relying on it.
Plan your backupsYour exit plan
Leave when
you choose.
Moving a Pepper installation to new hosting or a new partner follows a documented procedure. The export covers the records and files; the rest of the pack is yours to keep.
Moving to a different product is a different job. The customer list and reports download as CSV, and mapping the rest is work to plan for.
Export from the browser
Open Settings > Backups, enter a recovery password and click Export and download. The ZIP holds every record, setting and file, encrypted with that password. Test the export before you rely on it.
Know what the export leaves out
Application code, the .env file, server configuration and uploaded update packages are not in it. Keep the trusted package for your version from your purchase downloads. Older or scheduled backups also need the original APP_KEY from .env, saved in a separate secret store.
Keep custom code in version control
The updater replaces the application code and refuses a customized installation. Changes you make live in a repository of your own, applied again after each update.
Import into a fresh installation
Upload the package on new hosting, choose Import a backup during setup, select the ZIP and its password, and choose SQLite, MySQL or MariaDB. Import verifies every record and file before activation. The Docker recipe in the download is one way to stand up the new server.
Hand over the keys
A new technical partner needs the package and its hash, the export and its password, the APP_KEY for older backups, the custom-code repository, the domain and DNS, the email settings, the hosting account and the manual.
The responsibilities
Know who
looks after what.
You arrange hosting, email delivery, maintenance and backups. Product support covers bugs and built-in features that do not work as documented, including the supplied installation and update process.
Your subscription includes software updates and product support while active. Hosting administration and custom development are separate, unless a written service agreement covers them.