Terms of Use

Last updated: October 28, 2026

1. Operator and agreement

Tenkai is operated by Romain Lanz, sole proprietorship, Entreprise individuelle, Switzerland, IDE CHE-375.491.965. "We", "us" and "our" mean Romain Lanz, not a separate limited-liability company.

These terms govern the deployment platform we provide to you. If you act for an organisation or team, you must have authority to bind the customer you represent. You must be at least 18 and legally able to enter this agreement. The Privacy Policy explains personal data processing; it is not a substitute for a required data processing agreement.

2. Service and authorised operations

Tenkai helps teams provision and configure servers, deploy applications and manage resources on infrastructure they control. You choose the infrastructure and storage providers and are responsible for your contracts with them.

You authorise us to access connected accounts, repositories, registries and servers and to run the operations you request through authorised team members or agent tokens. Those operations can install software and the Tenkai Agent, change configuration, update or reboot servers, deploy or withdraw workloads, run backups and restores, and delete managed resources. Confirmed deletion of a database resource or a project containing it can remove its stored data.

Tenkai uses privileged SSH access and administration commands. Provider permissions may extend beyond the controls shown in the platform.

3. Accounts, teams and acceptable use

Provide accurate account information, protect credentials, choose team roles carefully and revoke access when a member or agent no longer needs it. You are responsible for instructions from people and agents you authorise, to the extent allowed by law. Report suspected compromise promptly.

Only connect systems you are entitled to manage. You must have the rights and permissions needed for your code, data and deployment instructions, including obligations to the individuals whose data your applications process.

Do not use Tenkai for unlawful activity, infringement, fraud, unsolicited bulk messaging, malware or unauthorised access. Do not bypass security or plan limits, abuse billing offers, or disrupt Tenkai or other customers. Follow your providers' applicable rules. Authorised use of Tenkai's supported automation interfaces is allowed.

4. Plans, billing and cancellation

Paid plans are team subscriptions, not per-server or per-seat invoices. Available monthly or yearly prices, limits, currency and applicable tax are shown before purchase. Our payment provider handles purchases through its own checkout, which names the seller of the subscription. Payment details, invoices, tax handling and any merchant terms shown at checkout also apply to that purchase. Tenkai remains responsible for providing its platform.

Subscriptions renew automatically and are charged for each billing period until cancelled. A member with billing permission can cancel through Tenkai. A subscription that currently grants a paid plan ends at the end of its paid period, with that plan available until then. A live subscription that no longer grants a paid plan, such as an unpaid or paused subscription, is cancelled immediately. If an upgrade is waiting for payment, cancellation may require completing that payment or waiting for the pending upgrade to expire. Cancellation clears a scheduled plan change and is separate from deleting your account.

Upgrades are invoiced immediately for the applicable difference and take effect once payment succeeds. A supported downgrade starts at the end of the paid period, without a credit for that period. Cancelling does not automatically refund payments. Refund requests follow the seller's applicable process and mandatory law; these terms do not remove rights concerning an incorrect charge or our failure to provide the service.

Provider charges are separate. You pay your infrastructure, storage, registry and other providers even if a deployment fails or you cancel Tenkai. Reaching a plan limit prevents additional items; it does not by itself stop or delete existing workloads, including after a downgrade or failed payment.

We will notify you of a subscription price increase at least 30 days before it applies, and it will apply no earlier than the next renewal after that notice. You can cancel before renewal. A quoted paid period is not repriced retrospectively.

5. Your content and confidentiality

You retain ownership of your code, files, configuration, logs, databases and backups. You grant us a non-exclusive permission to access, copy, transmit and process them only as necessary to provide the service, carry out your instructions and complete an agreed transition or legally required retention. Providers assisting us receive only the permissions needed for their tasks. This permission does not authorise public reuse of your content, advertising, or use of your name or logo in marketing.

We treat non-public content and credentials as confidential. We restrict access to people and providers who need it for operations, authorised support, security or legal obligations, with appropriate confidentiality duties. Support access must be limited to the work needed; do not send unnecessary secrets or personal data. Necessary legal disclosures are subject to applicable law. Confidentiality duties continue after termination.

Tenkai's own software, branding and documentation remain ours or their respective owners'.

6. Security, backups and recovery

You are responsible for your application code, lawful data use, provider permissions, resource configuration and customer-managed security settings. Maintain your own administrator access, monitor operations and backup failures, and keep recovery procedures that work without Tenkai.

Do not rely on a single copy of important data. Keep independent backups with access controls appropriate to your risks, test restoration and check that bucket lifecycle rules do not remove needed copies. A displayed successful operation is not a guarantee that every application-level recovery requirement is met.

Tenkai's backup feature uses a team-provided S3-compatible bucket, not backup storage supplied by Tenkai. It encrypts backups before they leave the node using a team backup key. Tenkai holds the encrypted private keys and can use them for restores; only-customer decryption is not promised. An owner or administrator must download and protect the current and previous private backup keys to recover independently, and download them again after a rotation. A backup object without its matching key cannot be decrypted. Losing access to Tenkai without saved keys can prevent recovery. Rotation does not re-encrypt older objects or invalidate a previously downloaded key for those objects.

Backup schedules, retention and restores depend on the supported resource and your configuration. Registering a bucket alone does not create backups. Retention depends on the kind of backup, as the Privacy Policy describes; it does not guarantee a number of days of history. Missed daily runs are not all recreated after an outage. Removing a bucket connection leaves its objects with the provider. We do not guarantee successful backups, uninterrupted scheduling or successful restores.

7. Removing a server and ending access

Removing a server makes Tenkai forget it. It does not delete or stop the provider machine, unless you ask Tenkai to delete the machine with the server where Tenkai offers it. Deleting the machine destroys everything on it and cannot be undone. On a machine that stays, the installed tenkai user, automation SSH key and agent remain on the machine, although Tenkai no longer accepts that server's agent or enrolment. Provider billing continues until you delete the machine and any separately billed volumes, IP addresses or other resources with the provider.

You must separately revoke provider, repository, registry and bucket credentials where appropriate, remove Tenkai's SSH access and agent, and decide what to keep or delete on your infrastructure. Removing records from Tenkai is not proof that access has been removed from the server. If a Tenkai bug deletes or damages something during removal, section 9 applies.

8. Availability and warranties

Tenkai depends on networks, provider APIs, registries, customer servers and other services. Their failure, your configuration or our own software errors can cause failed deployments, downtime or loss. We do not promise uninterrupted or error-free service, compatibility with every application, or a service level or recovery time unless separately agreed in writing.

Subject to mandatory law and express commitments we make, the service is provided "as is" without additional warranties of fitness for a particular purpose or a guaranteed result.

9. Faults, data loss and liability

An operation can fail after it has changed your infrastructure. A Tenkai bug can accidentally delete a database or resource, lose or corrupt data, break a deployment, cause downtime or damage infrastructure, even when you gave correct instructions. Those outcomes are not automatically your responsibility merely because you authorised access or owned the server.

Responsibility depends on the cause, breach of duty, fault and applicable law. We are not responsible to the extent a loss is caused by your unauthorised or incorrect instructions, insecure application or provider failure for which we are not legally responsible. Any liability for our own contribution, or for providers acting on our behalf, is subject only to the legally valid exclusions and limits below.

To the fullest extent permitted by law, and subject to the exceptions below, we exclude compensation for loss, deletion or corruption of data, loss of profit, revenue, business opportunities or anticipated savings, business interruption, and indirect or consequential losses. The data-loss exclusion is intended to apply whether the loss is classified as direct or indirect.

Subject to the same limits, we also exclude losses arising from software bugs, errors or failed operations, including accidental database or resource deletion, damage to infrastructure, and costs of restoring data, repairing configuration or rebuilding infrastructure. These exclusions are intended to cover ordinary negligence, including our own ordinary negligence, only where such an exclusion is lawful. Data recovery and infrastructure repair costs can be direct losses; the exclusion does not rely on calling them indirect. If an exclusion is invalid for a particular claim, that claim remains subject to any cap that can lawfully apply.

For liability that is not excluded, our total aggregate liability to a customer for all claims under or in connection with this agreement, whether in contract, tort or otherwise, is limited to the greater of CHF 500 or the Tenkai subscription fees actually paid by that customer in the three months immediately before the earliest event giving rise to any such claim. This is one cumulative cap across that customer's teams, incidents and claims, not a new cap per incident, team or billing year. Fees exclude tax, refunded amounts and third-party infrastructure charges. An annual payment counts in full if actually paid within that three-month window, and does not count if paid before it; it is not allocated over service months. Non-CHF fees are converted using the Swiss National Bank's published exchange rate for the payment date, or its latest preceding published rate. The CHF 500 floor applies even if no qualifying fees were paid, including for free customers. It is a floor on the ceiling, not minimum compensation, an automatic payment or insurance for your data.

Neither the exclusions nor the cap apply to unlawful intent, gross negligence, fraud, death or personal injury, or any other responsibility that cannot lawfully be excluded or limited. This includes applicable mandatory consumer remedies and data protection compensation rights. The cap does not reduce a refund required by law. Swiss law does not permit advance exclusion of liability for unlawful intent or gross negligence.

If something goes wrong, stop further destructive operations where possible, preserve relevant evidence and contact us promptly so we can investigate and discuss recovery. Reasonable steps to reduce further loss matter.

10. Suspension, termination and data

We may restrict access where necessary to address a security threat, unlawful use, a material breach or non-payment. Where practicable, we will explain the reason and give you a reasonable opportunity to resolve it. Urgent risks or legal requirements can require immediate action. Suspension should be proportionate to the problem.

You may stop using Tenkai and cancel paid renewal as described above. Write to [email protected] to request account or team closure and agree data access and deletion arrangements. Before closure, preserve your code, configuration, recovery keys and independent backups. No general self-service export or automatic account-deletion feature is promised here.

Closing or suspending a Tenkai account is not an instruction to terminate your provider contracts or delete your machines. Existing workloads can continue without the control plane, but continued operation is not guaranteed. On termination we will stop using your connections for routine operations and arrange removal of stored credentials and customer data, subject to required retention and any applicable processing agreement. You still need to revoke access at your providers and servers.

We will retain only data needed for legal obligations, security or unresolved disputes after the applicable deletion process. The Privacy Policy explains retention principles. Outstanding payment obligations, confidentiality and legally valid liability provisions continue as needed after termination.

11. Changes and discontinuation

We may update the service and these terms. We will give at least 30 days' notice of materially adverse contractual changes or planned discontinuation, unless a legal obligation or urgent security issue requires earlier action. We will explain the change and your options before it takes effect. Changes do not retrospectively reduce accrued rights. Where law requires express acceptance, continued use alone will not replace it.

For planned discontinuation, we will offer a reasonable opportunity to retrieve available customer information and recovery keys, and address unused prepaid service fees under applicable law. You should keep independent access and copies rather than waiting for a discontinuation notice.

12. Law, courts and contact

Swiss law governs this agreement. Disputes are submitted to the courts of Geneva, Switzerland, except where mandatory applicable law provides other protections or requires another competent court. This choice does not remove mandatory consumer rights, data protection remedies or rights to complain to a supervisory authority.

Address legal, billing and service questions to [email protected]. If a clause is unenforceable, the remaining terms apply to the extent allowed by law.