Install a new Hyper-POS SaaS platform
Use this path when Hyper-POS has not yet been installed. The SaaS option appears in the Hyper-POS installer only when a compatible, approved add-on delivery is present. The ordinary POS installer remains available separately.
The SaaS installer choice is default-off in the current preview. If you only see the standard POS choice, do not complete a normal business installation expecting it to become SaaS automatically. Confirm that the publisher supplied the production-signed combined delivery and enabled the exact fresh-installer handoff for your release.
1. Get the correct files
Keep the original Hyper-POS package and the matching signed SaaS customer delivery together. The delivery may include the add-on, platform runtime, production dependencies, built assets, manifest, signature, publisher public key and the VPS launcher. Compare the archive checksum and public-key fingerprint with the publisher’s separate release notice. Never replace a signed file inside the ZIP.
2. Check your hosting
| Item | Customer or hosting provider action |
|---|---|
| PHP | Use PHP 8.3 for the website and command-line/cron paths, with the extensions reported by the installer. |
| Database | Use MySQL/MariaDB supported by the exact signed release. Prepare a separate empty platform database; do not place platform and subscriber data in one database. |
| Domains and HTTPS | Prepare a platform hostname and subscriber hostname base. Point them at the server and obtain valid certificates. |
| Prepare a real SMTP account that can deliver an owner code and subscriber mail. | |
| Private storage | Confirm the host allows application-owned private paths outside the public document root. |
| Background tasks | cPanel must allow a once-per-minute cron entry; VPS/root must support the reviewed runner. |
3. Prepare resources for your hosting mode
On shared hosting, use cPanel to create the platform subdomain, an empty platform database with a dedicated user, HTTPS, and the initial subscriber hostname plan before opening the installer. You will add the exact cron command shown by the installer. Read the cPanel instructions.
On a VPS, place customer-delivery.zip and install-hyper-pos-saas.sh in the same private download folder. DNS, TLS, PHP and database administration access must be ready. Read the VPS instructions.
4. Follow the Hyper-POS installer
- Open your new website
Visit the domain and open
/installif the installer is not shown automatically. Choose the language. - Choose Hyper-POS SaaS
Select Set up SaaS platform. If the SaaS choice is unavailable, check the signed delivery and release gate; do not continue through the normal business database step.
- Choose hosting mode
Select Shared Hosting / cPanel — manual provisioning or VPS with root access — automatic provisioning. Confirm the warning shown for your mode.
- Enter hosting details
For cPanel, enter the platform hostname, subscriber base domain, absolute separate SaaS server folder, and empty platform database connection. Follow the SMTP and cron controls if your entry path presents them; the direct-claim release path configures mail later and requires hosting DNS/document-root/background setup outside this short form. For VPS, run the supplied launcher and complete the browser form.
- Pass requirements
Fix each failed PHP, database, private path, HTTPS, email or scheduler check. Use Recheck after changing the server.
- Verify purchases and owner
Enter and validate the Hyper-POS purchase code in its existing installer step. The SaaS add-on entitlement is checked separately against the signed release. In the configured direct-claim journey, create the Platform Super Admin credentials in the installer and continue through the saved account claim; it skips separate SaaS purchase-code, owner-code and invitation screens. Other supported release paths show their own owner verification controls. The subscriber does not enter a purchase code.
- Review and start platform setup
Check the domain, database and owner details. The browser saves a one-time handoff. cPanel advances bounded platform phases; VPS shows progress while the approved root runner advances them.
- Activate Platform Super Admin
After completed health and account claim, sign in on the platform hostname using the administrator credentials established in the direct-claim journey. If your release instead offers an owner invitation, complete that flow and set the platform password there.
Fresh shared-hosting fields and examples
| Field | Example / instruction |
|---|---|
| Platform domain | platform.example.com, without a scheme or URL path. |
| Workspace domain | shops.example.com; subscriber slugs form hostnames below it. |
| SaaS server folder | An absolute separate private application folder, for example /home/shopacct/saas-platform. Use the approved writable path for your host, outside the original Hyper-POS installation. Point the platform hostname to this folder’s public child. |
| Database host / port | Provider values; commonly localhost and 3306. |
| Platform database / username / password | A separate empty database with full cPanel-prefixed names, for example shopacct_saas and shopacct_saasuser. Enter the actual generated password privately. |
| Administrator credentials | Create the platform administrator name, email, password and confirmation in the installer’s dedicated admin step. They do not create a subscriber store. |
The direct-claim runner proceeds through runtime, schema, administrator, direct claim, health and hosted management phases. It initializes the dedicated platform, not a subscriber business. The older existing-owner add-on flow uses /operator/setup, a configured private artifact and separate mail/activation controls; follow that conversion guide for an already running POS.
Where a release presents SMTP fields, use the provider’s host, port, security scheme, username/password and verified sender address/name. Add the exact scheduled command supplied by that release. Do not enable preview bypass flags to force a different installer sequence.
5. Before inviting real subscribers
- Open Super Admin, set platform branding, currency, timezone, SMTP and security settings.
- Configure a sandbox payment gateway, create a draft plan, verify its billing method, then publish it.
- Create one test subscriber and verify its domain, database, POS login, sale, support request and backup/cron status.
- Keep the installation receipts and signed release details outside the public website.
Local test flags and fixture signatures only help developers rehearse setup. The production installer must pass its signed release, real purchase/owner proof, host checks and native acceptance gates.