Hyper-POS DocumentationDocs

VPS / root server setup

This mode uses a signed launcher and a reviewed root runner. The root operator performs one initial command and repeats the same command to approve and resume the immutable setup request.

1. Prepare the host

Customer or host operator taskWhat to confirm
Provide root/sudoA supported Ubuntu, aaPanel or reviewed root/WHM cPanel profile. A shared cPanel Terminal account is not sufficient.
Install compatible servicesPHP 8.3, web server/PHP-FPM, required extensions, supported MySQL/MariaDB and local administration access.
Configure domainsPlatform and subscriber hostnames resolve to this host and have valid HTTPS certificates.
Prepare mailSMTP can deliver the one-time owner invitation.
Download both signed filescustomer-delivery.zip and matching install-hyper-pos-saas.sh are in the same private folder. Verify their published checksum/fingerprint.

2. Run the only launcher command

Open an SSH terminal, change to the private folder containing both delivered files, then run:

sudo bash install-hyper-pos-saas.sh

The script locates exactly one compatible Hyper-POS installation, verifies the complete signed delivery and creates the protected internal directories itself. It stops if it finds zero or multiple candidates. No /root/hyper-pos-saas-delivery/host-tools directory needs to be created by the customer.

3. Continue in Hyper-POS

  1. Choose VPS with root access

    In a fresh install, use the SaaS hosting step. In an existing install, complete owner proof and open /operator/setup.

  2. Enter platform settings

    Provide the platform domain, subscriber hostname base, platform database name and SMTP. No root path is entered in the browser.

  3. Pass checks and review

    Resolve all PHP, DNS/TLS, database, mail, source and capacity blockers. The browser saves a one-time setup request.

4. Return to the root terminal

Run the same command again from the same download folder:

sudo bash install-hyper-pos-saas.sh

The launcher shows the exact review digest for the saved request. Compare it with the browser review and enter that digest when prompted. A mismatch stops without executing the job. The runner performs bounded steps and writes progress; if interrupted, rerun the same command to resume the pinned job.

5. Finish and verify

  1. Activate the owner

    Use the emailed activation invitation and create a separate Platform Super Admin password.

  2. Review health

    Sign in to the platform domain and check Operations for HTTPS, runtime, queue, scheduler, capacity and backups.

  3. Test automatic provisioning

    Create a test subscriber and confirm its isolated domain, database, POS login and background work.

Native support matters

The current release gate has not yet accepted real Ubuntu/aaPanel and root/WHM cPanel journeys. Use this command only with the exact production-signed delivery and host profile approved by the publisher. Do not run a preview launcher against customer business data.