Administer
Register and renew an installation
Understand the issued term, online registration and the 720 powered-on-hour cutoff.
Understand the issued term
Pūnaha is one full proprietary product. The current issued 12-month term costs US$0 from its signed issue date. Personal and organisational use, multiple versions and multiple independently registered installations are permitted. Each installation must be registered and may include its approved cluster nodes. Optional support is separate.
Future renewal pricing is undecided. Proposed paid terms require advance disclosure and explicit acceptance. Issued terms and accepted commitments must be honoured. Keep the exact accepted document versions and receipts.
Register and confirm activation
Sign in as the System Owner and review the installation information in Registration & licence. Follow the displayed registration route to Support, review the applicable terms, complete approval and apply the verified activation. Check the active term on the original installation. Request submission or a downloaded file alone does not establish activation.
The production source defaults to Pūnaha Support. Final hosted and installed registration acceptance remains a release gate for these steps.
The 720 powered-on-hour allowance
Initial registration after setup and each renewal after a term expires have a 720 powered-on-hour allowance. Normal use is available during that allowance. Powered-off time does not count. Stopping the Product service alone does not pause the host TPM clock. Sleep, standby and VM suspension depend on the platform’s verified TPM behaviour.
The signed term uses its issued calendar dates. The allowance counts powered-on hours. Computer-date changes, restarts, adding nodes and importing activation again cannot create a fresh allowance.
Renew or export before the 720 powered-on-hour cutoff. At the cutoff, normal processing, tenant functions, administration, customer-data access and exports stop. Customer data is retained. Sign-in and the registration, renewal and identity functions needed to restore registration remain available.
Clock incidents
The approved policy allows at most 40 powered-on hours of cumulative undercount within each initial or post-expiry allowance, shared across incidents and approved nodes. An incident can qualify only when its maximum missing powered time fits the remaining tolerance and is durably recorded against that allowance with protection against replay and rollback. The normal cutoff stays at 720 counted hours, and signed term expiry and Owner warning thresholds stay the same.
A restart, clock change or activation import cannot replenish this tolerance. The final release must qualify the mechanism on the installed platforms. If powered time cannot be verified, follow the troubleshooting guide.
Renew in time
Review the displayed renewal terms and complete activation before the applicable cutoff. Plan enough time for approval and, when required, offline transfer. Export required data while normal access remains available.
Read the System Owner warnings
The application distinguishes renewal reminders before the signed term expires from allowance warnings after setup or term expiry. Renewal reminder thresholds come from the signed licence; the reviewed 60, 30 and 7-day policy uses calendar days. During a verified initial or post-expiry allowance, warnings appear at 168, 72 and 24 powered-on hours remaining. They do not create extra time.
The banner identifies initial registration, renewal or an unverifiable allowance. An unverifiable clock is not displayed as a trusted remaining-time countdown. Complete the action shown in Registration & licence and confirm the restored state.
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.