Terms of
Protocol
By interacting with the SOUAHOST NZ private infrastructure blueprint, validating an infrastructure signature via the Registry Gate, or establishing an external runtime deployment pipeline, you explicitly assent to the following technical and legal parameters.
1. Absolute Vetting & Invitation Imperative
SOUAHOST does not provide generic public computing pools. All clusters are deployed on a strictly finite pool of high-security bare-metal nodes. System access requires an authenticated, non-transferable cryptographic allocation token signature. Any unvetted handshake attempt will result in instantaneous drop configurations.
2. Permitted Isolation Boundaries
Authorized tenants are leased a single-tenant virtualized runtime sandbox. Under this matrix, you guarantee that your deployment pipelines will not execute multi-tenant bleeding vectors, automated proxy scanning arrays, or asynchronous stress configurations targeted at neighboring isolated hypervisors.
| Infrastructure Module | Rate Limit Guard Ring | Compliance Standard |
|---|---|---|
| Next.js / Edge Interfaces | Sliding-Window Token Bucket | 100% Core Web Vitals SLA |
| Node.js / Go Backends | Granular Isolated Pool Arrays | Zero Shared Thread Overflow |
| PostgreSQL Schemas | Dedicated Connection Isolation | Absolute Virtual Data Separation |
3. Data Sovereignty & New Zealand Jurisdiction
All network engineering and compute tasks are governed entirely by the laws of New Zealand. Both parties agree that any legal dispute, structural interpretation, or data enforcement actions fall under the exclusive jurisdiction of the courts of New Zealand, executed locally within the Auckland region.
4. Cryptographic Disclaimer & Liability Cap
SOUAHOST provides uncompromised structural infrastructure isolation. However, we assume no liability for structural software flaws, vulnerable pipeline code dependencies, or leaked session JWT sign-keys engineered outside our native core HSM infrastructure layers.
5. Protocol Termination Procedures
The SOUAHOST Engineering Board retains unilateral rights to immediately revoke infrastructure tokens and de-provision container systems if malicious thread injection, cross-guild scope violations, or unvetted resource throttling are detected by the Sovereign Edge Monitor.