Tetra Connectors

Tetra Connectors provide built-in data integration with specific instruments or systems. They offer similar functionality as Tetra Agents, but are containerized applications that can run either on-premises or in the cloud. After the data is uploaded to the Tetra OS, it can then be processed by a pipeline, translated into a Tetra Data model, and integrated with other systems.

To start using an integration, see our Integration Quickstart Guides and the specific integration's documentation.

For more information about the different types of Tetra Integrations, see Tetra Integrations. For additional best practices, see Data Integration in the TetraConnect Hub. For access, see Access the TetraConnect Hub.

Connector Types

The TDP currently supports two Connector types, which offer the same functionality, but different levels of customization:

Legacy Connectors are tightly coupled with the TDP and must be upgraded in conjunction with TDP releases.
Pluggable Connectors can be deployed independent of a TDP release. You can create your own custom Pluggable Connectors by building self-service Connectors. For more information, see Create, Configure, and Update Pluggable Connectors.

Supported Pluggable Connectors

📘
NOTE
You can deploy Pluggable Connectors to the cloud, an on-premises Tetra Hub, or on any Docker-compatible host as a standalone Connector. For more information, see Connector Deployment Options and Create, Configure, and Update Pluggable Connectors. Standalone deployments are available on request. To deploy a standalone Connector, contact your CSM or account executive.

The TDP currently supports the following Pluggable Connectors. All Pluggable Connectors require additional third-party licenses and/or infrastructure. You can also create your own custom Pluggable Connectors by building self-service Connectors.

For information about which Connector versions are eligible for patches and customer engineering support, see Tetra Integrations Support.

Pluggable Connector	Source Type	Description	Required Licenses and Infrastructure
Tetra Amazon S3 Connector	File sharing	Monitors Amazon S3 folders for new and modified files and automatically uploads them and/or their metadata to the TDP	AWS account Amazon S3 bucket Amazon SQS Queue Amazon SNS topic IAM role AWS CLI See details
Tetra Benchling Connector	Connectivity middleware	Pulls events from Benchling and uploads it to the TDP Can use self-signed SSL/TLS certificates	Benchling Notebook account See details
Tetra Biacore Insight Connector	Connectivity middleware	Pulls data from Cytiva Biacore Insight and uploads it to the TDP	Biacore Insight account See details
Tetra Cellario Connector	Connectivity middleware	Pulls order data from Cellario and uploads it to the TDP Uploads historical data to the TDP Can use self-signed SSL/TLS certificates	Cellario account Cellario instance, installed and running See details
Tetra Egnyte Connector	File sharing	Monitors Egnyte folders for new and modified files and automatically uploads them to the TDP	Egnyte account A valid client ID and client secret for an app defined in your Egnyte developer portal See details
Tetra SDC Connector	Connectivity middleware	Pulls measurements from SDC and then uploads them to the TDP Accepts measurement requests and sends them to SDC	AGU SDC account See details
Tetra SharePoint Online Connector	File sharing	Monitors SharePoint folders for new and modified files and automatically uploads them to the TDP	SharePoint Online account Microsoft enterprise application See details
Tetra KEPServerEX Connector	Connectivity middleware	Pulls data from KEPServerEX and uploads it to the TDP	KEPServerEX account IoT Gateway plugin (licensed separately from KEPServerEX) An MQTT broker run on the same machine as KEPServerEX (Recommended) Tetra Hub See details
Tetra LabX Connector	Connectivity middleware	Pulls data from multiple LabX instances and uploads it to the TDP	LabX account Linux host machine See details
Tetra Metrohm OMNIS Connector	Connectivity middleware	Receives analysis results from Metrohm OMNIS and uploads them to the TDP	Metrohm OMNIS system with CALL WEB API support See details

Supported Legacy Tetra Connectors

The TDP currently supports the following Legacy Connectors. All Legacy Connectors require additional third-party licenses and/or infrastructure.

For information about which Connector versions are eligible for patches and customer engineering support, see Tetra Integrations Support.

Connector	Source Type	Capabilities	Supported Deployment Types	Required Licenses and Infrastructure
Legacy Tetra Cellario Connector	Connectivity middleware	Pulls order data from Cellario and uploads it to the TDP	Cloud On-premises (Tetra Data Hub)	Cellario account Cellario instance, installed and running See details
Legacy Tetra IDBS E-Workbook Connector	ELN	Pulls data from IDBS E-Workbook and uploads it to the TDP Searches data in the TDP and downloads the results to IDBS E-Workbook	Cloud On-premises (Tetra Data Hub)	IDBS E-Workbook account Linux host machine See details
Legacy Tetra SDC Connector	Connectivity middleware	Pulls measurements from SDC and then uploads them to the TDP Accepts measurement requests and sends them to SDC	Cloud only	AGU SDC account See details
Legacy Tetra Solace Connector	Connectivity middleware	Integrates the TDP with the Solace PubSub+ Platform	Cloud On-premises (Tetra Data Hub)	Solace PubSub+ account See details
Legacy Tetra Signals Connector	ELN	Pulls data from Signals and uploads it to the TDP Searches data in the TDP and downloads the results to Signals	Cloud only	Revvity Signals account Linux host machine See details
Legacy Tetra Egnyte Connector	File sharing	Monitors Egnyte folders for new and modified files and automatically uploads them to the TDP	Cloud only	Egnyte account See details
Legacy Tetra Box Connector	File sharing	Monitors Box folders for new and modified files and automatically uploads them to the TDP	Cloud only	Box account See details

Install a Connector

To install a Connector, see that Connector's documentation. To download a Connector for on-premises installation (Tetra Hub or Standalone deployments), see Tetra Agent & Connector Installers in the TetraConnect Hub.

Connector Deployment Options

You can deploy Connectors in three ways:

Cloud: Runs Connectors in the cloud and provides network access directly to the TDP and AWS APIs.
Standalone: Runs Connectors on-premises by using a Docker container image and installation script provided by the TDP. This option allows customers to install Pluggable Connectors on any host server that can run Docker containers. These Connectors have the same network requirements as ones installed on a Tetra Hub.
Hub: Uses an on-premises Tetra Hub for Pluggable Connectors, or a Tetra Data Hub for Legacy Connectors, to proxy connections to TDP and AWS APIs. For more information, see Add a Connector to a Hub and Add a Connector to a Data Hub.

To learn about TDP networking best practices, see Recommended Architectures for Network Connectivity to Private Cloud and On-Premises Components in the TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘
NOTE
Standalone deployments are available on request. To deploy a standalone Connector, contact your customer success manager (CSM) or account executive. For more information, see the Standalone Connector Installation and Upgrade Guide in the TetraConnect Hub.

Documentation Feedback

Do you have questions about our documentation or suggestions for how we can improve it? Start a discussion in TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘
NOTE
Feedback isn't part of the official TetraScience product documentation. TetraScience doesn't warrant or make any guarantees about the feedback provided, including its accuracy, relevance, or reliability. All feedback is subject to the terms set forth in the TetraConnect Hub Community Guidelines.