Hikube-Dienstleistungsvertrag

Internal Ref.: 003-HikubeServiceDetails — Edition: October 2026
HIDORA SA (CHE-286.910.173) – Avenue des Morgines 12, 1213 Petit-Lancy, Switzerland
Website : https://hidora.io

Between

HIDORA SA, CHE-286.910.173, Avenue des Morgines 12, 1213 Petit-Lancy (Switzerland),

hereinafter referred to as “HIDORA”,

and

[Client], [full identification], [address]

hereinafter referred to as “Client”

Collectively, the “Parties”

1. Object and contractual documents

1.1. These HIKUBE Special Terms and Conditions (“HIKUBE STCs”) govern, together with the documents listed below, the provision by HIDORA of the cloud infrastructure and platform services “HIKUBE,” as well as associated services (support, backups, managed options, and integration projects).

1.2. Applicable documents (in descending order of precedence) :

1. The Order(s) or Statement(s) of Work (SOW) approved by the Client (quantities, durations, prices, and options) ;
2. These HIKUBE STCs ;
3. HIDORA SA’s General Terms and Conditions (the “GTCs”), including their appendices (Hosting SLA, Notice & Action Procedure, Data Processing Agreement/DPA, Confidentiality/NDA) ;
4. Technical documentation published on the HIDORA Portal and/or attached to the Orders ;
5. The “HIKUBE Service Sheet” (summary), as updated from time to time for technical, security, or operational reasons, in accordance with the documentation update rules of the GTCs (operational rank).

1.3. Hierarchy : In case of conflict: (i) Special Terms of an Order/SOW, (ii) these HIKUBE STCs, (iii) the GTCs, (iv) commercial documents. Lower-ranked documents are interpreted in a complementary manner.

1.4. Functional evolution : HIDORA may publish new HIKUBE components/services or evolve existing ones without materially degrading security or key functionalities. Purely operational updates (service sheets, published SLAs, procedures) are governed by the documentation update regime set out in the GTCs; any substantial change adversely affecting the Client’s essential rights will be notified with reasonable prior notice and will apply only prospectively.

1.5. Gateway clause : Terms in capital letters not defined in the HIKUBE STCs have the meaning set out in the GTCs.

1.6. Reference language : Unless otherwise specified, the French version prevails. Translations may be provided as a courtesy.

2. Specific definitions

In addition to the definitions in the GTCs, the following terms apply to the Hikube STCs:

Client Access: Credentials, roles, and access profiles enabling the Client to use HIKUBE (API/CLI/Portal).

Direct Hardware Access (Passthrough GPU): Mode in which a GPU card is presented directly to a Client’s VM/Pod (without an intermediate virtualization layer), granting sensitive hardware privileges.

GPU Card: Dedicated graphics/accelerator card made available to the Client.

HIDORA Counters: Mechanisms for measuring and aggregating usage (units/steps, prorating/rounding) used for PAYG billing.

Availability: Service availability as measured and defined in the SLA of the GTCs.

Environment: Data centers, networks, hypervisors, platforms, and software components operated by HIDORA to deliver HIKUBE.

HIKUBE Service Sheet: Summary document describing the scope, managed mode if applicable, prerequisites, and metrics applicable to HIKUBE Services, published and updated on the Website/Portal.

HIKUBE: Cloud offering operated by HIDORA encompassing all current and future resources and services (IaaS/PaaS and related services), including, without limitation, managed options (e.g., Kubernetes, databases, messaging, VPN, object storage, GPU) and support services, as described and updated in the “HIKUBE Service Sheet” and/or technical documentation published on the HIDORA Portal.

Maintenance Window: Scheduled time period during which HIDORA may perform operations that may temporarily affect Availability. Applicable windows are published on the Portal.

MFA (Multi-Factor Authentication): Authentication mechanism requiring at least two distinct factor categories (knowledge, possession, inherence), including, notably, FIDO2/WebAuthn or TOTP.

MTTR: Mean Time To Repair as defined in the SLA, representing the target recovery time of a service after an Incident.

Pod: Kubernetes deployment unit grouping one or more containers sharing network/volumes and a namespace.

PRA: Disaster Recovery Plan defined by the Client (procedures, responsibilities, tests, and restoration milestones).

RPO / RTO: Data recovery point objective / recovery time objective defined by the Client for its applications.

Managed Service: Component/service for which HIDORA performs operational tasks according to a scope defined in the HIKUBE Service Sheet and, where applicable, a specific SLA.

VM: Virtual machine provided on HIKUBE (vCPU/RAM/storage) and administered by the Client.

3. Service description and scope

a. Summary: HIKUBE provides the resources and services described in Appendix A – HIKUBE Service Sheet (summary).

b. Location & Sovereignty: HIKUBE is operated from data centers located in Switzerland (currently: Plan-les-Ouates, Gland, and Lucerne), with inter-site redundancy. Ancillary processing (e.g., anti-DDoS, monitoring, support) may involve subcontractors, managed in accordance with the GTCs (Appendix DPA).

c. Shared Responsibility Model: HIDORA operates and secures the Environment. The Client administers its resources (OS, middleware, applications, IAM, secrets, L7 policies, hardening, backups when not included) and remains responsible for the legality of its processing and content.

d. Encryption: Optionally, the Client may enable “at-rest” encryption on eligible resources, in accordance with the Order.

e. Activation of Additional Components/Services: HIDORA may offer additional HIKUBE Services (e.g., new database engines, network features, storage classes, AI/GPU modules) as described on the Portal and/or the HIKUBE Service Sheet. Their activation requires an Order/validation via the Portal. In the absence of specific terms, these HIKUBE STCs and the GTCs (including their appendices: SLA, Notice & Action, DPA, NDA) apply by default to these additional components. Availability targets and credit scales remain those published in the Hosting SLA for the relevant service.

4. Provision, changes, and maintenance

a. HIDORA may evolve the Environment (hardware/software upgrades, patches, configuration changes) without materially degrading functionality or security. Planned interventions are performed during the published Maintenance Windows. Emergency maintenance related to security or stability may be carried out with the best reasonable notice.

b. The Client accesses HIKUBE via API/CLI/Portal using Client Access credentials (MFA mandatory for administrative profiles, recommended for others). Permissions are granted according to the principle of least privilege.

5. Security, AUP, and compliance

a. The Client must at all times comply with the Acceptable Use Policy (AUP) in the GTCs. Prohibited activities include illegal, intrusive, or disruptive actions (malware, DDoS/DoS attacks, scanning, spamming, “bulletproof” hosting, etc.).

b. HIDORA implements technical and organizational measures in line with industry best practices and its internal policies. HIDORA SA is ISO/IEC 27001 certified; this certification applies to the scope indicated on the current certificate, which the Client may review upon request. HIDORA strives to maintain this certification for the duration of the HIKUBE STCs and informs the Client of any material changes to its status or scope. HIDORA may limit or suspend a Service to protect the Environment, comply with an injunction, or in case of a manifest violation.

c. FADP/GDPR Compliance: Processing of Personal Data is governed by the Data Processing Agreement (DPA) appended to the GTCs. The Client must ensure it has an appropriate legal basis and informs the data subjects. International transfers rely on mechanisms recognized by the DPA (e.g., EU SCCs + Swiss addendum, adequacy decision).

d. Personality Rights and Third-Party Content: HIDORA applies the Notice & Action Procedure of the GTCs in the presence of credible claims of rights infringement (image, voice, sensitive data, defamation, IP, trade secrets).

6. SLA, support, and proof agreement

a. Availability Targets: The availability objectives, measurement method, exclusions, and Service Credits are those specified in the Hosting SLA appended to the GTCs.

b. Support: Business days 08:00–18:00 CET via Portal/ticket and email; 24×7 infrastructure monitoring and on-call support. Target response times by severity are as published in the SLA. Repair times are not guaranteed unless specifically stated in the Order/SOW.

c. Proof Agreement: HIDORA’s logs, metrics, and technical records are conclusive, except where contrary evidence is provided by corroborating technical data from the Client.

d. Specific GPU (Passthrough) Exclusion: SLA/MTTR commitments do not apply to Incidents caused by a prohibited operation (section 8.c) or by risks inherent to the Client’s chosen GPU Passthrough; no Service Credit is owed in such cases.

7. Client obligations

a. The Client administers its deployments and configurations on HIKUBE, including, without limitation: IAM/RBAC, L7 security, public exposure (networks/ports/domains/IP/CDN), messaging (e.g., Kafka/RabbitMQ) and database schemas/topologies and ACLs; the Client plans and executes backups and restoration tests according to its RPO/RTO objectives and validates application behavior.

b. The Client manages its software licenses, content, and updates, and ensures regulatory compliance of its activities.

c. Use of GPUs requires the Client to install and manage the necessary drivers, frameworks, and licenses.

8. Dedicated GPUs – direct access (passthrough)

a. Scope: GPU Passthrough consists of presenting a GPU Card directly to a Client’s VM/Pod. This mode grants sensitive hardware privileges and involves increased technical risks assumed by the Client.

b. Client Administration & Obligations: The Client fully administers the guest OS, GPU drivers, and tools; ensures hardening, updates/patches, access management, and necessary logging.

c. Strictly Prohibited Operations: The following are prohibited unless prior written approval is obtained from HIDORA:

1. Flashing/upgrading/downgrading GPU firmware/vBIOS/microcode or the host server;
2. Unvalidated hardware/PCIe/SR-IOV/ACS reconfigurations or re-binding;
3. Installation/activation of rootkits, kernel modules, or tools intended to bypass the hypervisor or disable integrity controls.

d. Safety Measures and Suspension: In the event of a serious and imminent risk to hardware/infrastructure, HIDORA may immediately suspend the affected Service and notify the Client without delay.

e. Material Breach and Termination: Any violation of section 8.c constitutes a material breach, entitling HIDORA to terminate the Service by operation of law (or the Contract for just cause) by written notice, without compensation and without prejudice to claims for damages.

f. SLA Limits: SLA/MTTR commitments and Service Credits do not apply to Incidents caused by a prohibited operation (section 8.c) or by risks inherent to GPU Passthrough chosen by the Client.

g. Support and Billing: Any HIDORA assistance relating to Client-managed elements may be billed according to the applicable rates.

9. Price, billing, and taxes

a. Pricing Model (PAYG – HIKUBE): Prices (excluding taxes) are those published on the HIDORA Portal and/or specified in the Order. Unless expressly stated otherwise (e.g., prepaid credits, reservations, discounts), HIKUBE Services are billed on a consumption basis (PAYG) according to HIDORA counters.

b. Consumption Measurement: Usage is measured and aggregated by HIDORA counters; units, billing steps, prorating, and rounding rules are those published on the Portal. In case of discrepancies between the Client’s internal measurements and HIDORA’s, HIDORA’s measurements prevail, except in the case of manifest error.

c. Billing and Due Dates: Billing is done monthly in arrears: an invoice is issued at the end of the month for consumption of the previous calendar month (Europe/Zurich). Project/consulting services, if ordered, are billed based on time spent or milestones, also in arrears, according to the applicable rates. Payment terms, taxes, and currency are governed by the GTCs.

d. Late Payment and Default: In case of late payment, HIDORA may apply the measures provided in the GTCs (interest, suspension after notice, early maturity, payment guarantees). No refund is due for amounts already paid for credits/reservations or for services already commenced, except where mandatory legal provisions apply.

e. Price Adjustments: HIDORA may adjust applicable rates for future periods in accordance with the GTCs; changes are notified via the Portal and/or by email with the required notice. Past consumption remains subject to the rates in effect at the time of execution.

f. Restoration Costs (GPU) and Interventions: In case of damage attributable to the Client (notably following a prohibited operation under section 8.c), the Client bears (i) the replacement of the GPU Card and impacted components, (ii) reasonable and documented costs for diagnostics, datacenter intervention, logistics, and labor (time-based, applicable rates), and (iii) services to restore operational conditions. These amounts are invoiced in addition, in arrears, independently of PAYG billing.

10. Duration, suspension, and termination

a. The initial term and renewal conditions are specified in the Order. At expiration without renewal, access is suspended.

b. HIDORA may suspend all or part of the Services in case of a material breach, non-payment, security incident, fraud, request from authorities, or threat to the Environment. Suspension does not affect amounts due.

c. Termination for just cause is governed by the GTCs, after formal notice if the breach is remediable.

11. Reversibility, return, and deletion

Upon expiration or termination, the Client may request the return of its Content in a reasonable standard format; fees may apply. Unless otherwise specified, HIDORA retains the Content for thirty (30) days to allow recovery, and then permanently deletes it within the following thirty (30) days, in accordance with the DPA of the GTCs.

12. Intellectual property

The Client retains all rights to its Content. HIDORA retains all rights to the Environment, its documentation, scripts, templates, and know-how, including those developed during execution, subject to applicable third-party/open-source licenses.

13. Subcontracting, location, and transfers

HIDORA may subcontract all or part of the service provision, under its responsibility and in compliance with the DPA appended to the GTCs (register of subcontractors, location, recognized transfer mechanisms for Switzerland/EU).

14. Commercial references

Unless the Client objects in writing, HIDORA may mention the Client’s name and logo as a reference (without disclosing confidential information). The Client may object at any time by contacting legal@hidora.io.

15. Notifications and miscellaneous

a. Notifications: Shall be made in writing (including email) to the contact addresses designated in the Order or on the Portal.

b. Assignment: The Client may not assign its rights or obligations without HIDORA’s prior written consent, except for non-substantial intra-group assignments. HIDORA may assign in the context of a reorganization or business transfer.

c. Force Majeure: As provided in the GTCs.

d. Partial Invalidity: The invalidity of any provision does not affect the validity of the others.

16. Governing law and jurisdiction

a. The HIKUBE STCs are governed by Swiss law, excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG).

b. The exclusive jurisdiction is in Geneva, subject to legal remedies before the Swiss Federal Supreme Court according to applicable law.

Each Party confirms its acceptance of the HIKUBE STCs and the documents referenced therein.

HIDORA SA Place and Date :
Client Place and Date :

HIDORA SA – All Rights Reserved
October 2026

Appendix A – HIKUBE Service Sheet (summary)

Included/Optional Components:

Purpose

This appendix sets the framework for classifying HIKUBE Components (included/optional) without establishing a fixed list.

Classification and Activation

Any component identified as such on the HIKUBE Service Sheet and/or the HIDORA Portal at the time of Service activation is included; any component requiring specific activation via Order or Portal, which may involve separate pricing and/or a distinct SLA, is optional.

References and Documentation Hierarchy

For each component, technical specifications, consumption metrics/units, prerequisites, and Managed Service scope are those published and updated on the HIKUBE Service Sheet and/or the HIDORA Portal. In case of discrepancies, the Order, HIKUBE STCs, and GTCs prevail for contractual obligations and SLAs; the Service Sheet/Portal prevails for technical specifications and metrics.

Component Families (non-exhaustive, illustrative)

Linux/Windows VMs (scalable instance families) and block storage (replicated/encrypted); managed Kubernetes (LB Services, PV, kubeconfig, Ingress-NGINX options, cert-manager, FluxCD, Velero, Passthrough GPU); S3 object storage; managed databases (PostgreSQL, MariaDB/MySQL, Redis); messaging (Kafka, RabbitMQ); managed VPN; dedicated GPUs (models subject to availability); backups & DR plans (plans, retention, restore tests).

This list is illustrative; refer to the Portal/Service Sheet for current details.

Lifecycle and End-of-Life (EOL)

HIDORA may add, modify, replace, or remove components in accordance with the documentation update rules of the GTCs. Changes do not materially degrade key functionalities actually used by the Client; reasonable notice and, where applicable, appropriate migration measures are provided (except in case of security urgency/legal requirement).

Location

HIKUBE Services are provided from data centers located in Switzerland; sites may change for redundancy, maintenance, or security reasons, without transfer outside Switzerland without the Client’s written consent, except in security emergencies or legal obligations.

Shared Responsibility:

• HIDORA: Infrastructure availability, standard environment maintenance, Environment security, SLA, 24×7 monitoring.
• Client: IAM/RBAC, L7 security, application lifecycle (manifests/Helm), public exposure, Kafka/RabbitMQ/DB schemas/policies, restore tests, regulatory compliance.

Encryption:

• Optional at-rest encryption on eligible resources.

Support :

• Business days 08:00–18:00 CET (Portal, email). 24×7 infrastructure on-call. Target response times by severity (High ≤ 1h; Normal ≤ 2h; Low ≤ 8h) as per the SLA in the GTCs.

SLA (summary) :

• Availability per Service as published in the SLA; exclusions: announced maintenance, force majeure, use contrary to the AUP, components not provided by HIDORA. Service credits applied to subsequent invoices (exclusive remedy for covered downtime).

Security & Compliance:

• Technical and organizational measures aligned with industry best practices; ISO/IEC 27001 certification within the certified scope; DPA (FADP/GDPR, subcontractors, transfers, breaches) appended to the GTCs. Notice & Action procedure for rights infringements.

HIDORA SA – All Rights Reserved
October 2026