The terms for Klair.

These terms (the “Terms”) govern your access to and use of klair.dev (the “Site”) and the three products that klair operates: Hermes, Apollo, and Moon (each a “Product”, together the “Products”). They apply when your team uses a Product directly — for example, as an invited Cohort participant during the private beta, or under a paid plan after general availability.

If you are engaging klair to deliver custom software for you as a service, that engagement is covered by a separate per-project agreement — a Master Services Agreement and one or more Statements of Work, scoped, priced, and signed independently of this document (a “Services Engagement”). For that engagement, the per-project agreement controls; nothing in these Terms forms part of it unless explicitly incorporated by reference.

By creating an account, accepting an invitation to the Cohort program, or otherwise accessing the Site or a Product, you agree to be bound by these Terms on behalf of yourself and, where applicable, the organisation you represent. If you do not agree, do not use the Site or the Products.

klair.dev (“klair”, “we”, “us”, “our”) is a French société par actions simplifiée (SAS) registered in France. We build and operate the Products; we also use them internally to deliver custom software for our clients under separate Services Engagements. The language of record for these Terms is English; French law governs them. Our general contact is hello@klair.dev. Legal, privacy, and security contacts are listed in section 22.

“Klair”, “we”, “us”. klair.dev, a French société par actions simplifiée (SAS) registered in France, and any affiliate acting on its behalf in delivering the Site or a Product.

“Customer”, “you”. The organisation that accepts these Terms via an account, an accepted Cohort invitation, an order form, or actual use of a Product. Where an individual uses the Products without an organisation, “Customer” means that individual.

“Authorized User”. An individual the Customer permits to access a Product under the Customer's account — for example, an employee, contractor, or external collaborator with a named seat.

“Product”. Hermes, Apollo, or Moon, including the web interfaces, APIs, embeddable components, orchestration engines, and supporting infrastructure that klair makes available under these Terms.

“Hermes”. klair's universal proposal/intake plugin, designed to be embedded on a Deploying Party's surface and to draft proposals and scoping documents with prospects across verticals (software intake, legal engagement letters, design RFPs, accountant scoping, marketing campaigns, and similar).

“Apollo”. klair's AI development platform, which picks up tickets from a Customer's project tracker, reads the surrounding repository, drafts plans for human review, implements approved plans on isolated lab branches, validates in ephemeral environments, and opens pull requests for human approval.

“Moon”. klair's post-launch managed operate phase, including the “Apollo on Call” incident workflow, in which hotfix PRs are drafted in a lab and routed for one-click human approval. Moon is currently open only to Customers with an active Services Engagement; Apollo-direct Moon rolls out post-GA.

“Cohort”. The invited group of teams using a Product in private beta with klair prior to general availability on 1 September 2026. Cohort participation is governed by these Terms together with any cohort-specific terms communicated at invitation.

“Beta”. The pre-GA period for each Product, during which capability, pricing, rate limits, and support response times may change with reasonable notice.

“Services Engagement”. A custom software engagement delivered by klair under a separate Master Services Agreement and Statement of Work. Outside the scope of these Terms.

“Embedding Site” / “Deploying Party”. For Hermes: the website, web application, or other surface on which Hermes is embedded (the “Embedding Site”), and the party that controls that surface (the “Deploying Party”). The Deploying Party may be the Customer itself or a third party that the Customer authorises.

“Output”. Any draft, plan, code change, pull request, message, report, or other artefact that a Product generates on the Customer's behalf, whether or not subsequently accepted by an Authorized User.

“Customer Data”. All data, code, content, and materials that the Customer, its Authorized Users, or a Deploying Party submit to or generate through a Product, including prospect submissions to Hermes, repository contents read by Apollo, and incident telemetry processed by Moon.

Authentication uses magic links and OAuth — we do not store passwords. You must provide accurate registration information, keep your access credentials and any session links secure, and let us know promptly if you suspect that an account, session, or repository access token has been compromised. You are responsible for everything done under your account, including the actions of your Authorized Users.

Some Products require granting tokens or permissions to third-party systems (for example, project trackers, source repositories, or messaging platforms). You are responsible for ensuring that the scope of any access you grant is appropriate for the Product's documented function and for revoking access when an Authorized User leaves your organisation.

You agree not to use the Site or any Product to: (a) generate, ship, or distribute content or code that knowingly infringes third-party rights, including intellectual property, privacy, and publicity rights; (b) bypass authentication, access controls, or rate limits in systems you do not own or are not authorised to test; (c) violate applicable export-control, sanctions, anti-bribery, or other trade-compliance law; (d) attempt to extract model weights, reverse-engineer the orchestration layer, or bulk-exfiltrate other customers' data, plan histories, or repository contents; (e) interfere with the integrity or performance of the Site or a Product, or with other customers' use of it; or (f) use a Product to build a directly competing product through systematic benchmarking, scraping, or model distillation. We may suspend or terminate access for material breach of this section as described in section 17.

Hermes is an intake and proposal-drafting component that the Deploying Party embeds on its own Embedding Site. Prospects interact with Hermes through a conversational interface, and Hermes drafts proposals, engagement letters, scoping documents, or similar deliverables based on the conversation and on configuration the Deploying Party provides. Hermes is cross-vertical and is not limited to software intake.

The Deploying Party controls the Embedding Site and is responsible for the lawful basis on which prospects interact with that site, including all cookie notices, consent banners, privacy disclosures, and similar notices required by applicable law on that surface. klair acts as a processor for the personal data submitted through Hermes on the Customer's behalf; the Deploying Party (or Customer, where they are the same party) acts as controller for that data and warrants that it has provided the disclosures and obtained the consents required for klair to process it as described in our privacy policy.

klair does not train models on prospect submissions or on Customer configuration. Submissions are processed solely to deliver Hermes' documented functions to the Customer, to operate and secure the service, and to meet legal obligations. The Customer is responsible for any decisions taken on the basis of Outputs generated by Hermes, including any contract or engagement issued to a prospect.

Apollo reads a Customer's project tracker and source repository at the scope authorised by the Customer's access tokens, drafts plans for the work it picks up, and — once a plan is approved by an Authorized User — implements that plan on an isolated lab branch, validates the change in an ephemeral environment, and opens a pull request. Apollo never merges code into a protected, shared, or default branch of a Customer repository without a human reviewer on the Customer's team approving the pull request. Human approval before merge is a mandatory gate, not a configurable default.

Source code stays in Customer repositories. klair does not copy, mirror, or persist Customer source code outside the active task window required to draft, implement, and validate a single plan, and klair does not retain Customer source code beyond that task window. klair does not use Customer source code, Customer prompts, or Customer repository metadata to train, fine-tune, or otherwise adapt the underlying models, whether Anthropic-provided or any future provider.

Apollo is currently in private Beta. Outputs are drafts intended for human review; the Customer remains solely responsible for what its Authorized Users choose to merge, deploy, or release. During the Beta, capability, rate limits, and supported integrations may change with reasonable notice to active Cohort participants. Beta-time disclaimers in section 14 apply.

Moon is klair's post-launch managed operate phase. It includes “Apollo on Call”, which monitors agreed signals, diagnoses incidents, drafts hotfix pull requests on isolated lab branches, and routes them for one-click human approval by an on-call reviewer on the Customer's team. Code remains in the Customer's repository at all times, and the same human-approval gate that applies to Apollo applies to Moon-initiated changes.

Moon is sold month-to-month with no lock-in. You can cancel at any time effective at the end of the current month; pro-rata refunds are not provided for partial months unless required by law. We will hand back the runbook — covering on-call rota, alert routing, known issues, and incident playbooks — to the Customer on cancellation, whether the cancellation comes from you or from us, so the Customer or its chosen successor can continue to operate the system without disruption.

Moon is currently offered only to Customers with an active Services Engagement that originally built the system being operated. Apollo-direct Moon (where the system was not built by klair) will roll out after general availability; until then, eligibility for Moon is at klair's discretion and may require an onboarding assessment.

Each Product is in private Beta until general availability on 1 September 2026. During the Beta, access is offered through the Cohort program: a small number of invited teams use Hermes, Apollo, or Moon with klair under these Terms and any cohort-specific terms communicated at invitation. Cohort access is free of charge for the duration of the Beta unless an order form expressly states otherwise.

Beta features are provided on an evaluation basis. Capability, pricing, rate limits, integration coverage, and support response times may change during the Beta; we will give reasonable advance notice of material changes that affect active Cohort participants. Service-level commitments for general availability will be published at GA and do not apply to the Beta.

Beta access for invited Cohort participants is free for the Beta period. Where a paid plan applies, fees are published on the klair pricing page or set out in an order form; fees are exclusive of VAT and other applicable taxes, which are added at the relevant rate.

Invoices are issued monthly in arrears unless otherwise stated on the plan or order form, and are payable net thirty days from the invoice date. Late amounts may accrue interest at the rate permitted by French law. Payments are processed by our payment processor (Stripe); card data does not touch klair's servers. Disputed amounts must be raised in writing within thirty days of the invoice date.

You retain all rights in Customer Data and in all Outputs generated for you, including code that Apollo or Moon commits to your repository's lab branches — that code is yours the moment it is committed. We do not train models on Customer Data or Customer source code, we do not retain Customer source code beyond the active task window required to draft, implement, and validate a plan, and we do not sell Customer Data to third parties. Full detail on what we collect, where it lives, how long we keep it, and which sub-processors we use lives in our privacy policy. For data-protection questions, including any data-subject request or sub-processor query, contact our DPO at dpo@klair.dev.

The Products themselves — including the orchestration engines, the execution and validation frameworks, prompt and policy templates, the web and embedded interfaces, the Site, related APIs, documentation, and supporting infrastructure — and all intellectual property in them remain owned by klair or its licensors. Nothing in these Terms transfers any ownership of the Products to the Customer.

Subject to your compliance with these Terms, klair grants you a worldwide, non-exclusive, non-transferable, non-sublicensable right to access and use the Products for your internal business purposes during the term of your access. The Customer grants klair only the rights in Customer Data that are necessary to provide the Products to the Customer, to operate and secure them, to comply with law, and to produce aggregated, anonymised statistics that do not identify the Customer or any individual.

We use a small number of sub-processors to deliver the Products: today, Supabase (EU-hosted Postgres) for primary storage, Stripe for payments, Resend for transactional email, and Anthropic for LLM inference. Each is bound by a data-processing agreement. We will give reasonable advance notice of material sub-processor changes that affect existing Customers. Where you connect a Product to a third-party system you control — for example, a project tracker, source repository, or messaging platform — your relationship with that third party is governed by your agreement with them, not by these Terms. The current list and the basis for each transfer are in our privacy policy.

Except as expressly stated in these Terms or in an applicable order form, the Site and each Product are provided “as is” and “as available”, without warranties of any kind, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, or that the Products will be uninterrupted, error-free, or secure. This is particularly so during the Beta. Outputs are drafts that require human review; klair does not warrant that any Output is fit for a Customer's purpose, free of defects, or non-infringing. To the maximum extent permitted by applicable law, all implied warranties and conditions are excluded. Nothing in this section limits any warranty that cannot be excluded under the law of a Customer's jurisdiction.

To the maximum extent permitted by applicable law, klair's total aggregate liability arising out of or related to these Terms or your use of the Site or the Products in any rolling twelve-month period is capped at the greater of (a) the fees paid by the Customer to klair for access to the relevant Product during the twelve months immediately preceding the event giving rise to the claim, and (b) one hundred euro (€100) where the Customer is in free Beta and has paid no fees in that period.

To the maximum extent permitted by applicable law, neither party will be liable to the other for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, goodwill, anticipated savings, business opportunity, or data, even if advised of the possibility of such damages and even if a stated remedy fails of its essential purpose.

Nothing in these Terms excludes or limits either party's liability for fraud or fraudulent misrepresentation, for wilful misconduct, for death or personal injury caused by negligence, for breach of payment obligations, or for any other liability that cannot be excluded or limited under applicable law. Where a Customer is a consumer in a jurisdiction with mandatory consumer-protection rules, those rules prevail over any conflicting provision in this section to the extent of the conflict.

klair will defend the Customer against any third-party claim alleging that a Product, as provided by klair and used by the Customer in accordance with these Terms, infringes that third party's intellectual property rights, and will pay damages and reasonable costs finally awarded against the Customer (or agreed in settlement by klair) in respect of such a claim. klair has no obligation under this paragraph to the extent the claim arises from Customer Data, Customer instructions, modifications not made by klair, combinations with materials not provided by klair, or use of a Product after klair has notified the Customer to stop.

The Customer will defend klair against any third-party claim arising from (a) Customer Data, including any allegation that Customer Data infringes a third party's rights or breaches applicable law; (b) the Customer's use of a Product in breach of section 5 (Acceptable use) or of applicable law; or (c) for Hermes, any failure by the Deploying Party to provide the notices, consents, or other disclosures required on the Embedding Site, and will pay damages and reasonable costs finally awarded against klair (or agreed in settlement by the Customer) in respect of such a claim. The party seeking indemnity must notify the other promptly, give it sole control of the defence and settlement (subject to the indemnified party's reasonable interests), and provide reasonable cooperation.

Either party may terminate access to a Product for convenience on thirty days' written notice (ten business days during the Beta). Moon is cancellable month-to-month as described in section 8. Either party may terminate immediately for the other's material breach that is not cured within thirty days of written notice, or immediately on the other party's insolvency, bankruptcy, or analogous event.

We may suspend access immediately, in whole or in part, if we reasonably believe that continued use would breach section 5 (Acceptable use), create a security incident, expose other customers to material risk, or violate applicable law. Where we suspend, we will tell you why and, where it is safe and lawful to do so, give you an opportunity to cure. On termination, the rights granted to the Customer under these Terms end; sections that by their nature should survive — including 11 (Your data and your code), 12 (Our intellectual property), 14 (Warranty disclaimer), 15 (Limitation of liability), 16 (Indemnification), 18 (Confidentiality), 19 (Governing law), and 22 (Questions and contact) — survive termination.

Each party agrees to keep the other's non-public information confidential, to use it only to perform under these Terms, and to protect it with at least the same care it uses for its own confidential information of like importance (and in no event less than reasonable care), for the duration of access and for three years thereafter. Confidential information does not include information that is or becomes public without breach, was already lawfully known to the receiver, is independently developed without use of the discloser's information, or is rightfully received from a third party without confidentiality obligations. Either party may disclose confidential information to the extent required by law, regulation, or court order, on reasonable prior notice where lawful. Case studies, customer logos, and narratives on klair's public site are anonymised unless you explicitly opt in to disclosure.

These Terms, and any non-contractual obligations arising out of or in connection with them, are governed by the laws of France. Subject to the next paragraph, the courts of Paris, France have exclusive jurisdiction to settle any dispute arising out of or in connection with these Terms. The parties will first attempt to resolve any dispute in good faith for thirty days from the date one party notifies the other in writing of the dispute, before commencing proceedings.

Where a Customer is a consumer resident in a jurisdiction whose mandatory consumer-protection law grants the consumer the right to bring proceedings in the courts of that jurisdiction or to rely on protections that cannot be derogated from by agreement, nothing in this section deprives the consumer of those rights, and the law of the consumer's habitual residence applies to the extent it provides protections that cannot be excluded by agreement.

Neither party is liable for any failure or delay in performing its obligations (other than payment obligations) caused by events beyond its reasonable control, including acts of God, war, civil unrest, terrorism, strikes, epidemics, governmental action, failures of public infrastructure, internet or telecommunications outages, or material upstream provider outages. The affected party will use reasonable efforts to mitigate and to resume performance as soon as practicable, and will notify the other party of the event without undue delay.

We may change these Terms from time to time. For material changes, we will notify active Customers at least thirty days before the change takes effect — by email to the address associated with the account or by an in-product notice — and the effective date and version number at the top of this page will be updated. Non-material changes (clarifications, typographical fixes, updated contact details) take effect on posting. If you do not accept a material change, you may terminate the affected access before the change takes effect; continued use after the effective date constitutes acceptance.

Written legal questions, notices, and contractual correspondence go to legal@klair.dev. For general enquiries, use hello@klair.dev; for data-protection matters, dpo@klair.dev; for security disclosures, security@klair.dev; to report abuse, spam, or misuse of a klair service, abuse@klair.dev. We respond to legal, security, and abuse correspondence within one business day.