Operate
Run Pūnaha on several servers
Set up private databases, service groups, and a secure web address.
Start with a working Primary
Use a new Primary for each independent installation. Add approved Nodes when capacity or service placement requires them.
Choose public and private addresses
Map each public frontend to its browser facing API address. Use trusted HTTPS and explicit OIDC callbacks. Keep databases and private cluster listeners away from public traffic.
Read Public addresses and organisation sign in.
Add more servers
You can run more than one Workflow or AI server. Each node needs the same installation identity, provider choice, approved configuration, and access to the required storage.
Follow Add and manage cluster nodes. Database leases distribute queued work. Forwarding to a ready peer is not a guarantee against every machine failure.
Use the current authority
Make shared changes on the current configuration authority. Check node readiness before a transfer or service change. Joining nodes does not extend the 720 powered on hour allowance.
Upgrade the installation
Use a qualified upgrade path and one coordinated recovery checkpoint. Update every participating node before depending on a new private routing feature.
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.