Last updated: October 2026
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"). These Terms apply exclusively; any conflicting or deviating terms of the Customer are not recognized unless the Provider expressly agrees to them in writing. Where the parties conclude an individual agreement (in particular for Enterprise or guided onboarding), the individual agreement takes precedence over these Terms; these Terms apply in addition.
1.2 Contract Formation
For the Starter and Team plans, the contract is concluded when the Customer completes an order in the application at app.kanman.ai. By clicking the order button, the Customer submits a binding offer to enter into a contract. The Provider accepts this offer by activating access and sending an order confirmation. Enterprise contracts 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 completing the order, had the opportunity to take note of them in a reasonable manner, and actively confirmed their acceptance.
1.4 Business Customers Only
The Provider contracts exclusively with businesses (entrepreneurs within the meaning of Section 14 BGB), legal entities under public law and special funds under public law. Consumers within the meaning of Section 13 BGB are excluded. By ordering, the Customer confirms that it acts in the exercise of its commercial or independent professional activity. The Provider may request proof of business status.
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 with acceptance criteria, runs coding agents (for example Claude Code or Codex) in an isolated sandbox, verifies the result against the acceptance criteria, opens pull 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
- Local: free use of the kanman board and the kanman MCP with the Customer's own coding agents, without cloud runs.
- Starter and Team: subscriptions per AI team, billed monthly.
- Enterprise: a contracted number of AI teams under a separate agreement, where agreed including operation of further components in the Customer's own infrastructure.
New AI teams can use the Team plan free of charge for 14 days without providing payment details. When the trial ends, cloud runs pause until the Customer orders a plan; the board and the Local plan remain available. Guided onboarding is an optional paid service on request, agreed and priced individually for the Customer's setup. Pilot agreements concluded before October 2026 continue on the terms of the Team plan until the end date stated in them; the Pilot plan is no longer offered.
Current prices are shown on the pricing page at kanman.ai/en/pricing or in the order form.
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 either use its own contract and API key with a supported model provider (bring your own key, "BYOK"), in which case the provider's terms apply directly between the Customer and that provider, or use model access provided through the Provider, in which case usage is charged as stated in section 4.3.
2.5 Availability
The Provider targets an availability of the service of 99.5% on a monthly average. This excludes planned maintenance windows (Sundays 02:00-06:00 CET, maximum 4 hours per month, with 48 hours advance notice), emergency maintenance for security-critical updates, force majeure events, outages of third-party model providers or of services connected by the Customer, and self-hosted runners operated by the Customer.
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. 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 sandbox 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 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 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; verification against acceptance criteria reduces this risk but does not replace the Customer's own review where the Customer's policy requires it.
4. Prices and Payment
4.1 Prices
The prices stated on the pricing page or in the order form at the time of order apply. Due to small business status pursuant to Section 19 UStG (German VAT Act), we do not charge VAT and do not show it separately.
4.2 Payment
The Starter and Team plans are billed monthly in advance. Enterprise and guided onboarding fees are invoiced as set out in the respective agreement. Invoices are issued electronically by email. The invoice amount is due upon invoicing.
4.3 Model Usage
If the Customer uses BYOK, model usage is billed by the model provider directly to the Customer. If the Customer uses model access provided through the Provider, usage is passed through and billed as stated on the pricing page or in the order form, monthly in arrears. Budgets configured by the Customer limit 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 and can be terminated by either party to the end of the current billing month. Enterprise contracts and guided onboarding run for the term stated in the respective agreement.
5.2 Ordinary Termination
Termination can be made in text form (e.g., by email to support@kanman.ai) or in the billing settings of the application.
5.3 Extraordinary Termination
The right of both parties to extraordinary termination for good cause remains unaffected.
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. After the contract ends, customer data will be deleted within 30 days, unless legal retention obligations apply. Pull 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 damages resulting from injury to life, body, or health based on a negligent or intentional breach of duty, for damages based on intentional or grossly negligent conduct, and for damages 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 Liability for Breach of Non-Material Obligations
In the event of a breach of non-material contractual obligations through slight negligence, liability is limited to the fees paid in the last 12 months.
7.4 Indirect Damages
Liability for indirect damages and consequential damages, in particular lost profits, is excluded unless they are based on intent or gross negligence or result from a breach of material contractual obligations.
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).
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 applies.
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, 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 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. 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
The exclusive place of jurisdiction for all disputes arising from or in connection with this contract is the Provider's registered office in 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.