Terms of Service
Version: September 2026, effective 1 November 2026
English translation: the German version is the legally authoritative one. Full notice at the foot of this page.
1. Scope
These Terms of Service govern the use of the services of kubehz, operated by Lanisce, razvoj programske opreme, d.o.o. (hereinafter the “Provider”).
The services are offered exclusively to entrepreneurs, businesses, and professionals (B2B), i.e. natural or legal persons acting in the exercise of their commercial or independent professional activity, and are not directed at consumers. By registering, the user confirms that they are acting in a commercial or independent professional capacity.
2. Description of services
The Provider offers the following services:
- Self-hosted monitoring: dashboard access for monitoring self-operated Kubernetes clusters on Hetzner infrastructure
- Hosted control plane: managed Kubernetes control plane (etcd, apiserver, scheduler, controller-manager) on the Provider’s infrastructure
- Spaces (shared control plane): namespaces on a control plane the Provider operates and shares between customers, with worker nodes the customer supplies and owns
- CLI tooling: lok8s (open-source CLI for cluster provisioning and management)
3. Third-party infrastructure (Hetzner)
- Where the customer provisions worker nodes on Hetzner Cloud, that infrastructure is operated by Hetzner Online GmbH (“Hetzner”). Spaces customers may instead register machines from another provider or their own hardware, in which case this section binds only to the extent Hetzner is used
- The customer is solely responsible for their Hetzner account, their API credentials, billing with Hetzner, and compliance with Hetzner’s terms and acceptable-use policies
- The Provider acts solely as a facilitator of the managed control plane and the associated tooling
- Hetzner is an independent third party; the Provider has no control over Hetzner’s performance, availability, security, or policies
- Any issues, outages, or other matters on Hetzner’s side are governed exclusively by the agreement between the customer and Hetzner
- The customer must maintain an active, compliant Hetzner account for the duration of the contract and bears all costs owed to Hetzner
4. No warranties
To the maximum extent permitted by law, the service is provided “AS IS” and “AS AVAILABLE”, without warranties of any kind. All express and implied warranties are disclaimed, including, without limitation, the implied warranties of MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, and NON-INFRINGEMENT. Mandatory statutory rights of the customer remain unaffected.
5. Registration
- Use of the services requires registration with a valid e-mail address
- The user is responsible for the security of their credentials
- A user account is not transferable
6. Acceptable use
This section applies to the use of the service, including hosted control planes running on the Provider’s infrastructure. Worker nodes in the customer’s Hetzner account are governed by Hetzner’s acceptable-use policies (see Section 3).
The following is prohibited in particular:
- unlawful content or activities
- infringement of third-party rights
- attacks on third parties or on the Provider’s infrastructure (e.g. DoS attacks, abusive port scanning, distribution of malware, phishing)
- origination of spam
- unauthorized crypto-mining on the Provider’s infrastructure (hosted control planes); workloads on the customer’s own worker nodes remain the customer’s business
- attempts to circumvent quotas, tenant isolation, or security boundaries
- resale of the service without prior agreement with the Provider
In case of violations, the Provider may suspend or terminate the affected resources or the account (see Section 13), with immediate effect in serious cases. Statutory duties to report remain unaffected.
7. Prices and payment
7.1 Free / Community
- Free of charge, no payment details required
- Up to 2 registered clusters
- Community support via GitHub Discussions
7.2 Supporter (pay what you want)
- Minimum contribution: 5 EUR/month
- Suggested contribution: 10 EUR/month
- Cancellation possible at any time
7.3 Hosted
Hosted control planes, their add-ons and Spaces are metered per started hour of existence. The following four rules govern that metering:
- Every started hour is billed in full. Billing begins at the moment the resource is created. A resource that exists for part of an hour is billed for that whole hour, so a control plane or a Space that exists for ten minutes is billed for one hour.
- Existence is the billable event, not activity. A resource is billed for as long as it exists in the customer’s account, irrespective of its operational state. Only removal of the resource ends the charge: its deletion, or, for a unit the customer can switch off (such as an own control plane in a Space), its deactivation.
- A monthly cap applies per unit. The hourly charges accrued by a single unit within a calendar month do not exceed the monthly price published for that unit. The published monthly price is the unit’s hourly rate multiplied by 730 hours and constitutes a maximum: a calendar month of 31 days is billed no higher than that monthly price.
- Add-ons are billed separately. An add-on or resource that continues to exist after another resource has been deleted continues to accrue its own hourly charge until it is itself deleted.
By way of exception to rule 2, a static node (a worker node the customer brings and registers with a hosted cluster) is billed only for the hours in which it reports Ready; a node in the NotReady state is not billed.
Billing and invoicing remain monthly. There are no fixed plans; the shapes named on the pricing page are worked examples.
A hosted control plane is priced by three units:
- Control plane (one API server, the datastore, scheduled backups and the first 2 GB of state): 0.016 EUR/hour
- Each additional API server (the customer sets one to three): 0.008 EUR/hour
- State storage held above 2 GB, rounded up to whole GB each hour: 0.0005 EUR/hour per GB
The customer sets the API-server count and a state storage limit on the cluster and may change both at any time; the limits themselves are free of charge. The state limit can grow automatically, in steps the customer sets, up to a maximum the customer sets. Because the meter counts the bytes held and the datastore accepts no data beyond the limit, that maximum is the ceiling of the state charge.
- enterprise (custom): individually negotiated
- Add-ons: metered the same way, 0 to 0.018 EUR/hour each (backups are included in every hosted control plane, not a separate add-on); the kine datastore option is a credit of 0.002 EUR/hour
- Worker nodes run exclusively on the customer’s own Hetzner account (the customer pays Hetzner directly) and are subject to Hetzner’s terms (see Section 3)
For orientation, the monthly price of a unit is its hourly rate multiplied by 730 hours; under rule 3 above that amount is also the maximum the unit can cost within a calendar month. The canonical, current list prices are published on the pricing page; the amounts above reflect the list at the time this document was last updated.
Launch trial. Until 1 November 2026 nothing is charged for use under this section. Use before that date is metered and shown in the dashboard, so the customer can see what the month would have cost, but it is never invoiced. The first charged month is the first whole calendar month that ends after that date, and it is invoiced when that month closes. A payment the customer chooses to make during this period, such as a Supporter contribution, is charged and invoiced as usual. The Provider may move the date forward only, never earlier, and announces a move with the notice period in Section 17. Ten days before the date, the Provider sends a reminder by e-mail to every customer running a hosted control plane, stating the projected monthly cost at that customer’s use at that time.
7.4 Price changes
Current prices are introductory (beta) prices. Price changes will be announced at least 30 days in advance.
7.5 Gift codes
The Provider may issue single-use gift codes. A code carries a number of days of the Supporter tier, is redeemed in the dashboard, and moves no money: a redemption is never invoiced and never charges the customer. A code expires 12 months after it is issued. A customer may redeem at most 2 codes per rolling year and may hold at most 92 days of gift time at once; a redemption above either limit is refused without consuming the code. A yearly contribution at or above the amount shown at checkout also produces gift codes for the contributing customer.
7.6 Contributions
A contribution is a voluntary payment for the free dashboard service, made once or yearly, in an amount the customer chooses, at or above the minimum shown at checkout. It is not deferred payment for anything, and nothing is owed if it is not made. A contribution is invoiced like any other payment, VAT applies to it, and it does not change the account’s tier.
7.7 Refunds
The Provider can refund a paid invoice in full, to the payment method it was paid with. A refund is recorded on the invoice and in the customer’s billing history. Partial refunds are not supported.
8. Beta notice
kubehz is in its beta phase. The header carries a beta badge on every page, and the limitations below apply.
- The service is provided “AS IS” and “AS AVAILABLE”, without warranties of any kind (see Section 4)
- The Provider makes no representations regarding performance, uptime, compatibility, data integrity, security, or fitness for any purpose
- Features may change or be removed at any time without notice
- During the beta phase there is NO SLA, NO uptime guarantee, and NO support commitment
- Participation in the beta is entirely at the customer’s own risk; the customer acknowledges that beta services may expose them to increased risks of instability, data loss, or security issues
- The Provider recommends keeping independent backups of all data and configurations
9. Availability
- No SLA. The Provider strives for high availability but gives no guarantee, including for any downtime caused by Hetzner (see Section 3).
- Planned maintenance will be announced in advance where possible.
- The free tier is not guaranteed to be available permanently. If it is discontinued, this will be announced 90 days in advance.
10. Force majeure
Neither party is liable for delays or failures in the performance of its obligations, except for payment obligations, to the extent caused by events beyond its reasonable control. This includes, in particular, natural disasters, war, terror, labor disputes, power or network failures outside the party’s own sphere of influence, acts of authorities, and large-scale outages of the internet or of cloud providers.
The affected obligations are suspended for the duration of the event. Each party shall inform the other without undue delay of the occurrence and the end of such an event. If the force majeure event persists for more than 30 days, either party may terminate the affected services.
11. Data ownership
- The customer is and remains the owner of all cluster data
- The Provider has no rights whatsoever to the customer’s data
- For hosted clusters: the control plane data (etcd) belongs to the customer
- The Provider has no access to and no responsibility for data on worker nodes in the customer’s Hetzner account or for customer-managed backups; these are solely the customer’s responsibility (see Section 3)
- Upon termination of the contract: complete deletion of data, planned within 14 days, at the latest within 30 days
For hosted services, the data processing agreement (DPA) pursuant to Art. 28 GDPR additionally applies.
11a. Account deletion, undo and data export
- The customer can delete the account in the dashboard. The deletion starts a window of 14 days in which the account is frozen (no new resources) but still complete
- Within that window the account owner can cancel the deletion in the dashboard. The account returns to normal, including the self-hosted clusters the deletion detached. After the window the data is erased and the account cannot be restored
- The deletion is refused while the customer still runs hosted control planes; those are removed first. Registered self-hosted clusters do not block it: they are detached and their agent credentials are revoked, and the customer keeps running them
- The account owner can download the account’s data at any time, as one structured file, without asking for it. Secrets the platform holds as hashes or encrypted values, such as token hashes and stored credentials, are not part of that file; they are erased with the account
12. Limitation of liability
To the maximum extent permitted by law:
- The service is provided “AS IS” (see Sections 4 and 8)
- The Provider is liable without limitation only for intent and gross negligence
- In cases of slight negligence, the Provider is liable only for the breach of essential contractual obligations (cardinal obligations), i.e. obligations whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the customer may regularly rely; in such cases, liability is limited to the foreseeable damage typical for this type of contract
- Liability for data loss is limited to the typical recovery effort that would have been required had the customer made regular and proper backups
- The Provider is not liable for indirect, incidental, special, consequential, or punitive damages (including lost profits, lost data, and business interruption), even if advised of the possibility of such damages
- The Provider’s total cumulative liability is capped at the amounts actually paid by the customer to the Provider in the 12 months preceding the event giving rise to the claim, but no lower than EUR 60; for free/community users the cap is EUR 60
- Liability under mandatory product liability law and liability for culpable injury to life, body, or health remain unaffected
Because the service is in its beta phase and relies on third-party infrastructure (Hetzner), the Provider in particular accepts no liability for downtime, performance degradation, or data loss caused in whole or in part by Hetzner Cloud, network issues, or the customer’s own Kubernetes or worker-node configuration.
13. Termination
- The customer may terminate at any time
- The Provider may terminate with 90 days’ notice
- In case of a breach of these Terms: termination without notice is possible
- After termination: data deletion in accordance with the privacy policy; complete deletion planned within 14 days, at the latest within 30 days (see Section 11)
- Data and backups on worker nodes in the customer’s Hetzner account remain the customer’s sole responsibility
14. Hosted clusters — inactivity
The following applies exclusively to hosted clusters of customers without an active paid subscription (Free/Community). Hosted clusters of paying customers are neither paused nor deleted due to inactivity.
| Condition | Measure |
|---|---|
| 14 days inactive | E-mail warning |
| 21 days inactive | Cluster paused (CP pods stopped) |
| 30 days paused without response | Cluster deleted |
A paused cluster resumes automatically on the next active use (e.g. retrieving access credentials, a cluster or worker operation). Switching to a paid subscription removes the cluster from this scheme; an already-paused cluster then remains paused until its next active use, but is not deleted.
Payment default by paying customers is governed separately: after a failed payment, a grace period with notification follows; the account may then be suspended (clusters are not deleted by this). Upon successful payment, the suspension is lifted automatically.
Worker nodes in the customer’s Hetzner account are unaffected by these measures; they remain the customer’s responsibility and continue to be billed by Hetzner directly to the customer.
14a. Hosted clusters — Kubernetes version lifecycle
kubehz offers a curated set of Kubernetes versions for hosted control planes. You choose your cluster’s version and when to upgrade it (always forward, one minor version per step, executed inside your cluster’s maintenance window).
Every Kubernetes minor version reaches its upstream end of life (EOL), after which it no longer receives security patches. Hosted clusters running a Kubernetes version past its published EOL date will be upgraded by kubehz to the next supported minor version, after advance notice by e-mail 30, 14, and 7 days before the deadline. These notices, and the final confirmation of a performed upgrade, are service-critical and cannot be opted out of. The forced upgrade is the minimum viable step (one minor version only) and is executed inside the cluster’s maintenance window.
Shared control planes (Spaces) are versioned by kubehz on a fleet-wide policy (one minor behind the newest supported release; patches after a stabilisation period). Upgrades are announced to affected customers before they run and confirmed after completion. Customer machines (“nodes”) are never modified by kubehz; a node whose kubelet falls outside the supported version skew keeps running and is flagged in the dashboard, with a notice asking you to upgrade it.
15. Indemnification
The customer shall indemnify, defend, and hold harmless the Provider from and against any claims, losses, and liabilities (including reasonable attorneys’ fees) arising out of:
- the customer’s use of the service,
- the customer’s violation of these Terms,
- the customer’s use of Hetzner services or violation of Hetzner’s terms, or
- third-party claims (including intellectual-property claims) arising from content or workloads the customer runs (e.g. on worker nodes).
16. Governing law and jurisdiction
- Slovenian law applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG)
- Place of jurisdiction: Ljubljana, Slovenia
17. Changes to these Terms
The Provider reserves the right to amend these Terms. Changes will be announced by e-mail at least 30 days before they take effect. If the customer does not object within 30 days, the new Terms are deemed accepted.
18. Final provisions
- Severability: Should individual provisions of these Terms be or become invalid or unenforceable, the validity of the remaining provisions remains unaffected. The invalid or unenforceable provision shall be replaced by the valid rule that comes closest to the economic intent.
- Text form: There are no oral side agreements. Amendments and additions to these Terms must be made in text form; this also applies to any waiver of this text-form requirement.
- Assignment: The customer may transfer rights and obligations under the contract only with the Provider’s prior consent. The Provider may assign the contract to affiliated companies or legal successors.
This is an English translation provided for convenience. The German version of these Terms of Service is authoritative. For questions, contact contact@kubehz.io.