License Agreement edi-service.eu (rental license for operation on the customer's own server)

This is a convenience translation. Only the German version is legally binding; in case of any discrepancy the German version prevails.

Between fokus it solutions, owner Jens Musleh, Herrenberger Str. 62, 71069 Sindelfingen, Germany ("Provider") and the customer named in the order ("Customer"). The General Terms and Conditions (AGB), the Service Description, the SLA and, where applicable, the Data Processing Agreement (AVV) apply in addition.

---

§ 1 Definitions

• Software: the runtime environment of the EDI hub edi-service.eu that runs on the Customer's server (transport, processing, execution of mappings, ERP adapters, dashboard, configuration API), including updates.
• Instance: one installation of the Software on a server of the Customer, identified by an instance ID and its own instance key.
• License key: a time-limited proof of an Instance's right of use, signed by the Provider's license service.
• Central system: the Provider's services at app.edi-service.eu (ordering, customer portal, license service, onboarding questionnaire, setup service with AI agent, tunnel endpoint, update distribution).
• Customer data: all data created in or stored in the Instance, in particular messages, raw data, archives, logs and credentials.
• Customer configuration: partners, channels, rules, settings, ERP targets and mappings (rule sets with versions and test cases) created for the Customer, whether by the Customer, the Provider or the AI.
• Third-party components: programs of third parties that the Software uses and that are subject to their own license terms (§ 7).

§ 2 Right of use

1. For the term of the contract, the Provider grants the Customer the simple (non-exclusive), non-transferable and non-sublicensable right to install and use the Software on one server or one virtual machine, operated by the Customer or on its behalf, as one Instance for its own business purposes. TEST and PROD operation run in the same Instance.
2. The Customer may make the copies required for backup and restoration (§ 69d (2) of the German Copyright Act, UrhG) and may restore the Instance on a replacement server after a failure. Operating two Instances with the same ID at the same time is not permitted.
3. The Customer may also use the Instance for its affiliated companies (group companies), as long as it remains one Instance. The Customer is also liable for the obligations under this agreement to the extent these companies use the Instance. Use for any other third parties (data center operation, services for other companies) is not permitted.
4. The trial version is limited to one trading partner, one message type and TEST operation and ends after 30 days (AGB § 4).

§ 3 License key and renewal

1. The Software works only with a valid license key. The key is bound to the Instance and the server and is valid for 14 days at a time.
2. The Instance renews the key automatically every day via an outgoing HTTPS connection to the license service; the Customer's administrator can also trigger the renewal immediately in the dashboard. The Customer allows this connection. Incoming connections are not required for this.
3. On renewal, the Instance transmits a usage report containing only counters and identifiers: number of partners and message types, number of messages and slot changes in the last 30 days, environments used, software version and build ID, result of the integrity check, local time and a checksum of the change log. It does not transmit message contents, partner names or personal data.
4. If the license service is temporarily unavailable, the Instance continues to run with the most recently renewed key (up to 14 days) and then for a grace period of 7 days; the dashboard displays a warning. The Provider ensures the availability of the license service so that such an interruption remains the exception (SLA section 6).
5. The Software detects manipulation of the system clock and the operation of cloned Instances and reports them.
6. If the Customer switches from the trial version to the full version, the existing Instance receives the key of the full version with the next renewal, without reinstallation.

§ 4 Suspension without access to the server

1. If the contract ends, or if the Provider suspends renewal under AGB § 6 (6) (payment default) or because of a breach of § 6 of this agreement, the license service no longer issues new keys. The Provider does not access the Customer's server for this purpose. There is no remote shutdown through a back door.
2. After the last key and the grace period have expired (in the trial version without a grace period), the Instance switches to read-only mode: it no longer fetches messages for processing and hands nothing over to the ERP or to partners. Configuration, mappings, raw data, archives and logs remain viewable and exportable. Data is not deleted.
3. The Provider announces a suspension due to payment default in advance in text form (AGB § 6 (6)). Once the reason has been remedied, the license service resumes renewal; the Instance leaves read-only mode with the next valid key without reinstallation.
4. An Instance in read-only mode does not handle any EDI traffic. If the end of the contract is foreseeable, the Customer arranges a replacement in good time (§ 13).

§ 5 Limits of the trial version

The Software technically enforces the limits of the trial version at several points (on creation, during processing and on renewal). The Customer does not attempt to circumvent them; § 6 applies.

§ 6 Prohibited acts, protection of know-how

1. Unless § 69d or § 69e UrhG mandatorily permit otherwise, the Customer may not a) circumvent, alter or disable the license check, the limits of the edition, the integrity check or the signature check of updates, b) copy, distribute, rent out or make the Software available to third parties, except under § 2, c) modify, translate, decompile or otherwise reverse engineer the Software, including with the help of AI tools, d) use the Software, parts of it or findings from its examination to develop, have developed or market a program with essentially the same function, e) remove any identifiers, watermarks or copyright notices.
2. Paragraph 1 c and d also apply to the extent that parts of the Software are stored in readable form (scripts, playbooks, configuration) on the Customer's server. Readability does not confer any right to modify or reuse. The parties expressly agree on a duty to limit the acquisition within the meaning of § 3 (1) no. 2 letter b of the German Trade Secrets Act (GeschGehG) for all trade secrets contained in the Software.
3. Mandatory statutory rights remain unaffected, in particular observing, studying and testing the functioning during intended use (§ 69d (3) UrhG) and decompilation to achieve interoperability (§ 69e UrhG). Before the Customer obtains information on interoperability by decompilation, it requests this information from the Provider; the Provider makes the interface description (configuration API, OpenAPI) available.
4. § 6 does not apply to third-party components; they are governed solely by their own licenses (§ 7).
5. At the Provider's request, the Customer informs the Provider once per contract year in text form on which servers the Software is installed.
6. In the event of a culpable breach of paragraph 1 a, c or d, the Provider may terminate without notice. In addition, the Customer undertakes to pay, for each culpable breach of paragraph 1 a, c or d, a contractual penalty whose amount the Provider determines at its reasonable discretion and which, in the event of a dispute, the competent court reviews for appropriateness. The contractual penalty is credited against any claim for damages.

§ 7 Third-party components and free software

1. The Software uses third-party components under their own licenses, in particular free software (for example operating system and Python packages, PostgreSQL, nginx) and, for the OFTP2 and AS2 transport channels, the mendelson Community Edition, which is licensed under the GNU General Public License.
2. Rights in third-party components remain unaffected. Third-party components are governed exclusively by their own licenses. This agreement does not restrict the rights such a license grants the Customer; this applies in particular to components under the GPL, which expressly prohibits further restrictions. The fees under this agreement are not a fee for exercising rights under such a license.
3. Obtained from the manufacturer. Where possible, the installation downloads third-party components on the Customer's side directly from the official source of the respective manufacturer or project (package repositories, container registries, package index) and verifies them against fixed checksums. The same applies to the mendelson components: the installation downloads the unmodified program package from the manufacturer.
4. If the Provider exceptionally distributes a component under the GPL itself, it provides the complete corresponding source code of the distributed version in accordance with the terms of the respective license, for example at the same location as the executable version and without additional charge.
5. The Software communicates with the transport components only via folders, event files and logs in separate containers; it contains no code of these components.
6. A list of third-party components with license and source accompanies every installation (THIRD_PARTY.md) and can be viewed in the dashboard.

§ 8 Customer data and mappings belong to the Customer (no lock-in)

1. Customer data belongs solely to the Customer. The Provider acquires no rights to it.
2. In the Customer configuration, in particular the mappings created for the Customer, the Provider grants the Customer, to the extent the Provider holds rights in it, a perpetual, irrevocable, transferable right to use it, to modify it and to use it with other software or through other service providers, including after the end of the contract. The same applies accordingly to mappings created exclusively by the AI, to the extent any rights arise at all.
3. The Provider retains the rights in the Software, in general building blocks, templates, canonical format schemas and its expertise. It may use general, non-customer-specific insights from setups for further development, without disclosing Customer data or documents of trading partners.
4. Export. At any time, including in read-only mode, the Customer can export the entire Customer configuration as a file via the dashboard or the configuration API (partners, identifiers, channels, rules, settings, ERP targets, certificates, mappings with all versions and test cases, index of sample messages). The mappings are readable rule sets in JSON format. For security reasons, values of credentials are not readable and not included in the export (write-only); the Customer keeps them itself.
5. Raw data, archives and the database are stored on the Customer's server and remain there, including after the end of the contract.

§ 9 AI: the Customer's contract, data transfer, anonymization

1. The Customer concludes the AI contract itself with a provider of its choice, for a model that is on the Provider's current minimum list (as of October 2026, for example Claude Opus 5.5 or GPT-6 Astra). The AI provider bills the AI costs directly to the Customer. The Provider is not a party to that contract.
2. The Customer's AI key is stored encrypted on the Customer's server and cannot be read in plain text. The Central system calls the model only through the Customer's Instance and with the Customer's access.
3. When the AI works: during the initial setup, for new partner connections, for mapping changes and when evaluating uploaded documents. The Software processes ongoing message traffic on a rule basis without AI.
4. What is sent to the AI provider: For the setup, texts from the trading partners' documents (EDI guidelines, cover letters) and sample messages are sent to the Customer's AI provider. Ongoing business messages are sent neither to the AI provider nor to the Central system.
5. Anonymization. Personal data in sample messages and documents (names, email addresses, telephone numbers, in EDIFACT among others contact and name segments) is replaced by placeholders before transmission to the AI; this setting is enabled by default. The Customer can choose a more extensive level (additionally companies, addresses, prices, identifiers) or deselect anonymization. Identifiers and structure needed for the setup are retained at the standard level. The originals remain unchanged.
6. The Customer ensures that it may use the documents of its trading partners for this purpose and transmit them to its AI provider, and confirms its acknowledgment of the transmission when ordering. Without this confirmation the setup agent writes nothing.
7. Limits of the AI. The AI works only against TEST operation and only via a fixed list of tools of the configuration API. Switching to production, certificates, credentials, deletion and activating partners can only be proposed by the AI; an administrator of the Customer approves. Every change is logged with its originator, old value and new value. A cost budget applies to each setup job; consumption per operation is measured and displayed in the dashboard.
8. For the AI, documents and messages of partners are data only, not instructions. There is no complete protection against faulty AI results; therefore TEST before PROD applies (AGB § 11 (4)).

§ 10 Setup, connections, mapping changes

1. Included in the price, within the scope of the Service Description, are: a) the initial setup of the Instance from the implementation specification generated by the onboarding questionnaire, b) the connection to one ERP system of the Customer via a standard adapter, c) the connection of any number of trading partners in the formats and transport channels of the Service Description, d) mapping changes when an existing trading partner changes its format, its version or its guideline, e) new message types for existing trading partners in the formats and transport channels of the Service Description, f) the correction of mappings that do not comply with the specification or the guideline, g) test runs without limit.
2. There is no quantity limit for mapping changes or partner connections.
3. If information required for the setup is missing, the setup agent asks targeted follow-up questions in the dashboard and does not guess. The setup waits until the answer is given.
4. Not included in the price are: a) rebuilding the ERP connection after a change of the ERP system or a substantial change of its interface, b) formats, transport channels or adapters not named in the Service Description (for example X.400, VAN mailboxes, web EDI portal, Peppol), c) adaptations and programming in the ERP system itself, d) work on the Customer's server outside the Software (operating system, virtualization, backup, network).

The Provider offers such services separately on request, based on an individual quotation.

§ 11 Access of the Central system to the Instance, updates

1. No SSH and no root access. The Provider receives no SSH access, no user account with sudo rights and no passwords for the server. The Customer starts the installation itself with a single-use command.
2. The Instance establishes an outgoing tunnel to the Central system. Through it, the Central system reaches exclusively the configuration API of the Instance, and only with an access token that the Customer's administrator creates in the dashboard and whose permissions (scopes) the administrator defines. Reading message contents, setting credentials and switching to production are not possible through this access. The Instance logs every request.
3. The Customer can revoke the Central system's access at any time with one command (edi-service-access revoke) and revoke the token in the dashboard. The command stops the tunnel and automatic updates. The Software continues to run as long as the license key is valid; setup, AI services of the Central system and updates are then not possible. The revocation is permanent; the Customer sets up new access only with a new installation token from the customer portal.
4. The Instance fetches updates itself. It verifies the signature with the Provider's stored release key, accepts only higher versions and applies them locally. The Customer can pause updates (edi-service-access update-pause) and resume them. The Provider is not liable for damage resulting from a pause that prevents an announced security fix.
5. Remote access for support via SSH is not part of this agreement.

§ 12 Defects and liability

AGB § 10 and § 11 apply. In addition: the Provider owes Software that demonstrably implements the Customer's specification in TEST operation (mapping check against sample messages). Whether a mapping meets all functional requirements of the trading partner is shown only by the test with the partner; the Customer is responsible for this test and for the approval for PROD.

§ 13 Term and consequences of termination

1. The term is governed by AGB § 7.
2. The right of use under § 2 ends when the contract ends. The Instance switches to read-only mode in accordance with § 4 (2).
3. The Customer can still export its Customer configuration and Customer data afterwards (§ 8). On request, the Provider assists once with the export within 30 days after the end of the contract at no additional cost.
4. After the export, the Customer removes the Software from its server, no later than 90 days after the end of the contract. The Customer may keep and continue to use the mappings and data (§ 8 (2)).
5. The Provider deletes the Customer's data in the Central system (documents from onboarding, access token of the Central system) in accordance with the AVV.

§ 14 Miscellaneous

The final provisions of the AGB (§ 16) apply.