Skip to content

Terms of Service

Last changed: 31 October 2026. This English version is a courtesy translation; only the German version is legally binding.

1. Scope and Contract Formation

1.1 Scope

These Terms of Service (Terms) govern all contracts for the use of the Software-as-a-Service (SaaS) offering "kanman" between Marco Kerwitz, kerwitz.dev, Birkenweg 21, 31226 Peine, Germany (hereinafter "Provider") and the customer (hereinafter "Customer"). They apply to free use (the Local plan and the trial) as well as to the paid plans. These Terms apply exclusively; any conflicting or deviating terms of the Customer are not recognized unless the Provider expressly agrees to them in text form. Where the parties conclude an individual agreement (in particular an Enterprise agreement or guided onboarding), the individual agreement takes precedence over these Terms; these Terms apply in addition.

1.2 Contract Formation

Signing up at app.kanman.ai concludes a contract for free use. For the Starter and Team plans, the contract is concluded when the Customer completes an order in the application. By clicking the order button, the Customer submits a binding offer to enter into a contract. The Provider accepts this offer by activating the plan and sending an order confirmation. Enterprise agreements and guided onboarding are concluded by a signed order form or individual agreement.

1.3 Incorporation of Terms

These Terms become part of the contract when the Customer has been informed of them before signing up or ordering, had the opportunity to take note of them in a reasonable manner, and agreed to them.

1.4 Business Customers Only

kanman is an offer for businesses. The Provider contracts exclusively with entrepreneurs within the meaning of Section 14 BGB (German Civil Code), legal entities under public law and special funds under public law. No contracts are concluded with consumers within the meaning of Section 13 BGB; this also applies to free use. By signing up and with every order, the Customer confirms that it acts in the exercise of its commercial or independent professional activity. The Provider may request proof of business status and block access if it is not provided. There is therefore no statutory consumer right of withdrawal.

2. Service Description

2.1 Scope of Services

kanman is an AI teammate that works inside the Customer's engineering team and operates on the repositories and issue trackers the Customer connects (for example GitHub, GitLab or Jira). Depending on the configuration chosen by the Customer, kanman takes requirements, writes stories, runs coding agents (for example Claude Code or Codex) in an isolated environment, opens pull or merge requests and records its actions and decisions in an audit log. The exact scope of services is determined by the product description and documentation at docs.kanman.ai and by the plan or order form at the time of order.

2.2 Plans and Trial

Billing is per AI team (one kanman team with its board), not per user.

  • Local: free. The kanman board and the kanman MCP with the Customer's own coding agents on its own machines. kanman starts no runs, neither in the cloud nor on runners.
  • Starter: €99 per AI team per month, billed monthly in advance.
  • Team: €249 per AI team per month, billed monthly in advance. If a workspace has several teams on the Team plan, a volume price per workspace applies: the number of teams on the Team plan sets the price of each of them, as shown on the pricing page.
  • Enterprise: there is no self-serve Enterprise plan. Services beyond the plans (for example SSO, longer audit log retention, committed availability, invoicing) are only available under an Enterprise agreement negotiated individually. Requests to [email protected].

Every new AI team can use the Team plan free of charge for 14 days without providing payment details (trial). The trial ends automatically; it costs nothing and needs no cancellation. If the Customer does not order a plan by the end of the trial, the team continues on the Local plan: the board and the kanman MCP remain available, and kanman starts no more runs. The Provider may limit the number of trials per workspace and person and end a trial in case of abuse.

Guided onboarding is an optional paid service on request, agreed and priced individually. Pilot agreements concluded before October 2026 continue on the terms of the Team plan until the end date stated in them.

Current prices and the services of each plan are shown on the pricing page.

2.3 Execution Environment

Coding agents run either in the Provider's cloud environment in Frankfurt am Main, Germany, or on a self-hosted runner that the Customer operates in its own network. When the Customer uses a self-hosted runner, the Customer is responsible for providing, operating, securing and updating the infrastructure on which the runner runs. The Provider is responsible for the runner software as delivered, not for the Customer's infrastructure. Operators are responsible for complying with their model provider's terms when they configure the runner environment.

2.4 AI Models

kanman uses third-party AI models. The Customer can use its own contract and API key with a supported model provider (bring your own key, "BYOK"). In that case the model provider's terms apply directly between the Customer and that provider, and the Customer pays for model usage directly to its provider. Where the Provider offers model access through kanman, the Customer can use it instead; usage is then charged as stated in section 4.3.

2.5 Availability and Support

The Provider operates the service with reasonable care on a best-effort basis. For the Local, Starter and Team plans and for the trial, the Provider makes no commitment on availability and no commitment on support response or resolution times. Support is available by email to [email protected] and in the application, also on a best-effort basis. The Provider may carry out maintenance at any time and will try to announce planned maintenance that is expected to interrupt the service in advance where reasonably possible. Availability, maintenance windows and response times exist only in an Enterprise agreement and only as set out there.

2.6 Changes to the Service

The Provider is entitled to further develop and adapt the service, provided this is reasonable for the Customer and does not restrict the essential scope of services of a paid plan. The Customer will be notified of significant changes in a timely manner.

3. Customer Obligations

3.1 Proper Use

The Customer agrees to use the service only in accordance with applicable laws and these Terms. In particular, it is prohibited to:

  • use the service for unlawful purposes;
  • impair the security or integrity of the service or of the execution environment;
  • perform automated access outside of the provided API and integrations;
  • connect repositories, trackers or content that the Customer is not entitled to process.

3.2 Access Credentials and Keys

The Customer is responsible for keeping its access credentials, API keys and tokens confidential and is liable for all activities that take place under its account, insofar as it is responsible for them. The Customer grants kanman only the repository and tracker permissions it needs and may revoke them at any time.

3.3 Data Backup

The Customer's source code remains in the Customer's repositories. The Customer is responsible for regularly backing up its repositories and other data. In the event of data loss, the Provider's liability is, except in the cases of section 7.1, limited to the costs of restoring data from the Customer's most recent backup.

3.4 Policies and Review

The Customer decides through its policy settings what kanman may do, in particular which repositories and paths it may change, which budgets apply, whether it may merge pull or merge requests and whether auto-merge is enabled. The Customer is responsible for the policies it enables and for reviewing the results before they are used in production. Output generated by AI models can contain errors; the checks kanman runs reduce this risk but do not replace the Customer's own review where the Customer's policy requires it.

4. Prices and Payment

4.1 Prices and VAT

The prices stated on the pricing page or in the order form at the time of order apply. The Provider is a small business. Pursuant to Section 19 UStG (German VAT Act), no VAT is charged ("Gemäß § 19 UStG wird keine Umsatzsteuer berechnet."). The stated prices are therefore the amounts payable; no VAT is added.

4.2 Payment

The Starter and Team plans are billed monthly in advance. Payment is made through the payment service provider Stripe with the payment methods offered there. Fees for an Enterprise agreement and for guided onboarding are invoiced as set out in the respective agreement. Invoices are provided electronically or sent by email. The invoice amount is due upon invoicing. If a payment fails, the Provider may, after an unsuccessful payment reminder, suspend the paid services of the team concerned; the Local plan remains available.

4.3 Model Usage

If the Customer uses BYOK, the model provider bills model usage directly to the Customer; the Provider charges nothing for it. If the Customer uses model access provided through the Provider, the Provider charges the model provider's cost plus a 15% surcharge, monthly in arrears. Budgets configured by the Customer and the Provider's limits cap usage as described in the documentation.

4.4 Price Changes

Price changes only apply to new billing periods. The Customer will be informed of price changes at least 30 days before they take effect. In the event of a price increase, the Customer has the right to terminate the contract with effect from the date the change takes effect.

5. Contract Term and Termination

5.1 Term

The Starter and Team plans run for an indefinite period without a minimum term and can be terminated by either party to the end of the current billing month. Months already paid are not refunded pro rata. After a paid plan ends, the team continues on the Local plan. The Customer can end free use at any time by deleting its account or workspace; the Provider can end it with 30 days' notice. Enterprise agreements and guided onboarding run for the term stated in the respective agreement.

5.2 Ordinary Termination

Termination can be made in the billing settings of the application or in text form (e.g., by email to [email protected]).

5.3 Extraordinary Termination

The right of both parties to extraordinary termination for good cause remains unaffected. Good cause for the Provider exists in particular if the Customer breaches section 3.1 or is not a business within the meaning of section 1.4.

5.4 Consequences of Termination

Upon termination of the contract, kanman stops working on the Customer's repositories and trackers and access to the service will be blocked. The Customer can export its data, including the audit log, until the end of the contract period. Deleted teams and workspaces are erased for good 30 days after deletion, unless legal retention obligations apply (for example to invoices). Pull or merge requests, commits and tracker entries already written to the Customer's own systems remain there.

6. Rights to Results

Code, stories and other results that kanman creates for the Customer belong to the Customer to the extent rights in them arise. The Provider grants the Customer all rights of use required for this. The Provider may use the Customer's content only to provide the service and not to train AI models.

7. Liability

7.1 Unlimited Liability

The Provider is liable without limitation for intent and gross negligence, for damages resulting from injury to life, body or health, for fraudulently concealed defects, to the extent of a guarantee given, and under the Product Liability Act.

7.2 Liability for Breach of Material Contractual Obligations

In the event of a breach of material contractual obligations (cardinal obligations) through slight negligence, liability is limited to foreseeable, contract-typical damage. Material contractual obligations are those whose fulfillment makes the proper performance of the contract possible in the first place and on whose compliance the Customer may regularly rely.

7.3 Otherwise

Otherwise, the Provider's liability for slight negligence is excluded.

7.4 Free Use

For free use (the Local plan and the trial), the Provider is liable only in the cases of section 7.1.

7.5 Customer Policies and Infrastructure

Except in the cases of section 7.1, the Provider is not liable for damage that results from policies the Customer has enabled (for example auto-merge without human review), from changes the Customer merges or deploys without the review its own policy requires, from the Customer's self-hosted infrastructure, or from services of third parties that the Customer connects or contracts directly (including model providers used with BYOK).

7.6 Agents

The above limitations also apply in favor of the Provider's vicarious agents.

8. Data Protection

The Provider processes personal data in accordance with the Privacy Policy. Where the Provider processes personal data on behalf of the Customer, in particular in source code, tracker content and logs, the Data Processing Agreement forms part of the contract. The sub-processors used are listed on the sub-processor page.

9. Force Majeure

The Provider is not liable for the non-fulfillment or delayed fulfillment of obligations due to circumstances beyond its reasonable control, in particular war, terrorism, natural disasters, pandemics, government orders, outages of service providers for which the Provider is not responsible, or cyberattacks that could not be prevented despite reasonable protective measures.

10. Changes to the Terms

The Provider is entitled to change these Terms with effect for the future, provided this is reasonable for the Customer. Changes will be communicated to the Customer in text form at least 30 days before they take effect. If the Customer does not object within 30 days of receiving the change notification, the amended Terms are deemed approved. If the Customer objects, either party may terminate the contract with effect from the date the change takes effect. The Provider will inform the Customer in the change notification about the significance of the 30-day period and the right to object.

11. Final Provisions

11.1 Applicable Law

The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods.

11.2 Jurisdiction

If the Customer is a merchant (Kaufmann), a legal entity under public law or a special fund under public law, or has no general place of jurisdiction in Germany, the exclusive place of jurisdiction for all disputes arising from or in connection with this contract is Peine, Germany.

11.3 Severability

Should individual provisions of these Terms be or become invalid, the validity of the remaining provisions shall remain unaffected.

11.4 Text Form

For declarations in connection with this contract, in particular terminations, text form (e.g., email) is sufficient.

11.5 Language

The German version of these Terms is binding. The English version is for information only.