Collection: A Collection is a concept to group Flow Templates and can be defined and managed by the User.

Component: A Component is an assortment of functions that allow access to external data sources and the passing of data through the OIH Services. Components can be generic i.e. for a technical stand-ards such as REST, GraphQL or Databases or they can be application specific.

Connector: A Connector is a type of a Component which is dedicated for the communication with another services’ Application Program-ming Interface (API).

Credentials: In order to activate an Integration Flow an End-User needs to grant access according to security mechanism the application chooses, for instance by providing their login information. Cre-dentials are necessary to ensure consent and compliant access to the data. Credentials are stored on the OIH Platform in an encrypted state.

Execution: When running a Flow Instance the Component’s functions are being executed to actually perform actions such as checking for new entries, or retrieving, transforming and passing on data. Each such action is counted as one Execution.

Flow Template: A Flow Template is a description of an Integration Flow that is created via the Open Integration Hub Platform and can be used to activate pre-defined Integration Flows. An Integration Flow is a set of functions that connect several components with each other and transfer data between the connected data sources.

Flow Instance: A Flow Instance is generated from a Flow Template through the activation by a User or End-User. It is the fully functional description of an Integration Flow, including credentials, variables, and customizations.

Flow Execution: A Flow Execution is the technical execution of an Integration Flow.

Integration Function: A function that allows the interaction with external API’s. The core functions are Actions and Triggers, used to retrieve or pass-on data to respective endpoints.

Mapping: A Mapping is used to transform data from one application’s data schema to another. It is provided by the User in a Flow Template and can sometimes be customized in a Flow Instance.

Open Integration Hub Framework (OIH Framework): OIH Framework provides technology, data models and defines standards to enable integration between business applications. The Framework is published as Open Source Software under the Apache 2.0 license and developed by an open source community.

Open Integration Hub Service (OIH Services): provide the functionality of the OIH Framework and are mostly built and consumed as Docker images or npm packages.

Open Integration Hub Platform (OIH Platform): provides a hosted version of a subset of the OIH Framework. The included OIH Services are deployed, run, and managed on a central cloud infrastructure. The OIH Platform also provides its own user interface and additional functionality which may not be open sourced.

Provider: Provider is the entity providing access to and usage of the OIH Platform.

Tenant: The person or entity who uses the OIH Platform to create and provide Flow Templates. The Tenant is the customer of the Provider. During the beta test each User is a Tenant.

User: The User of the Open Integration Hub Platform is an individual that is on behalf of a Tenant responsible for the administration of the Tenants integrations. A User manages these integrations via the OIH Platform and provides them for consumption to End Users. End-Users are users of service provided by a Tenant to its customers or other third parties.

1. The OIH Platform includes, to the extent of the features it provides, the ability to create, edit, and utilize the services offered, e.g. Connectors and Flow Templates. It can be used by Tenants for their own usage or to provide functionality which utilizes the OIH Platform to End-Users (e.g. usage of a Flow Instance by an End-User.
2. Connectors are offered by the Provider. A Tenant can propose to the Provider to include Connectors developed by the Tenant in the OIH Platform. If the proposal is accepted, the Tenant transfers all rights for the Connector to the Provider as needed for usage on the OIH Platform without limitation in time and place, unless the Connector is made available by the Tenant to the Provider under an open source license specified by the Provider. A Tenant may choose to have their custom developed Connectors be made available only for their own Tenant as a private Connector.
3. A Flow Template can either be provided by the Provider or can be created by a User for the own use of a Tenant. Any Flow Template is being made available “as it is” without any warranty of any kind for any defects, malfunctions, data losses etc. unless such defects are due to willful misconduct of the Provider.
4. The Provider reserves the right to reject to publish a Connector and / or a Flow Template or to remove it from the OIH Platform in its sole discretion. In general, a User will be informed if and why a Connector or Flow Template is not published or removed.

1. Each User can design Flow Templates for their own usage or for the usage of End Users. To run the Flow Template the User might have to enter information required, e.g. Credentials, variables, and customizations.
2. If a Flow Instance shall exchange data with a third-party service, the User or End-User must provide the Credentials for the service, if applicable. Otherwise, usage of a Component and thus the functionality of a Flow Instance is at least limited. In addition, usage of third-party services by means of a Component can be subject to license agreements of the relevant service provider, e.g. API license agreements, which the User or End-User might have to conclude on its own behalf with the relevant service provider. The Provider is not party to such agreements and not affiliated with third-party service providers even if a Component to use such service has been made available on the OIH Platform.
3. The Provider does not assume any liability for third-party services, as it only allows usage of these services by the means being made available by the relevant service provider (e.g. usage of public APIs).

1. Usage of the OIH Platform requires registration of a User account. For registration all data being marked as required must be stated correctly. Only one User account can be registered per person. We are free to reject any application for registration of a User account.
2. Any User account can be terminated by any party any time without notice. If the User terminates its account Flow Template published under the account for usage by other Users will still be available on the OIH Platform to other Users being subject to the license as set by the User.

1. This Agreement represents the entire understanding between the parties concerning its subject matter. Any conflicting ancillary agreements and prior agreements on the contractual subject matter are herewith rendered void.
2. Amendments and additions to this Agreement must be in text form, unless a stricter form is prescribed by statute. This also applies to any waiver of this form requirement.
3. The parties' general terms and conditions do not apply to this Agreement. This applies even if undisputed reference was made to their inclusion in later documents which are related to this Agreement.
4. If a provision of this Agreement is or becomes wholly or partially void, invalid or non-enforceable, or a necessary provision is not contained in the Agreement, the validity and enforceability of all other provisions of this Agreement will not be affected.
5. The Agreement is governed exclusively by the law of the Federal Republic of Germany. International private law does not apply unless mandatory. If a User is a consumer as stipulated in Sec. 13 German Civil Code (BGB) the German laws apply only so far as mandatory stipulations for the protection of consumers allow.
6. Exclusive place of jurisdiction for all disputes in connection with this agreement shall be at the registered office of the Provider unless the User is a consumer as stipulated in Sec. 13 German Civil Code (BGB) and has its place of residence in the European Union.