Product overview

Build Event-Driven Applications Cloud Natively

Your cloud-first strategy reduces costs, increases flexibility and efficiency. For the same reasons, your integration platform should be cloud native, too.

Who Uses TriggerMesh Technology

SAP
ONUG
GitLab
Adenza
WMWARE
PNS Bank

TriggerMesh is a complete
cloud native integration platform

Declaratively define event flows between sources and targets, with content-based filtering, splitting and processing using functions.

Sources are the origin of data and events. These may be on-premises or cloud-based. Examples include databases, message queues, logs, and events from applications or services.
Source
Splitter
Splitters breaks events into multiple events which may then be processed individually.
Router
Transformation
Transformations are a set of modifications to incoming events. Examples include annotating incoming events with timestamps, dropping fields, or rearranging data to fit an expected format.
Function
Functions implement custom event flow logic and may act as a source, transformation, or target. Functions support Python, NodeJS, and Ruby runtimes.
Filter
Filters determine which events to process based on their content. These may be the basis for dropping unwanted events or for creating rules engines for event processing.
Target
Targets are the destination for the processed events or data. Examples include databases, message queues, monitoring systems, and cloud services.
Source
Splitter
Splitters breaks events into multiple events which may then be processed individually.
Router
Transformation
Transformations are a set of modifications to incoming events. Examples include annotating incoming events with timestamps, dropping fields, or rearranging data to fit an expected format.
Function
Functions implement custom event flow logic and may act as a source, transformation, or target. Functions support Python, NodeJS, and Ruby runtimes.
Filter
Filters determine which events to process based on their content. These may be the basis for dropping unwanted events or for creating rules engines for event processing.
Target
Targets are the destination for the processed events or data. Examples include databases, message queues, monitoring systems, and cloud services.

TriggerMesh is the leading Kubernetes-based integration platform

Our open source API helps you combine on-premises systems and cloud services in an automated manner

Build an application flow using our catalog of bridges

TriggerMesh accelerates the move to an event-driven architecture

Integration as Code TM

Kubernetes Native API

Triggermesh runs on Knative, so it is an easy platform to deploy and operate. You can incorporate existing Kubernetes objects like Secrets and Configmaps when defining your integrations.

Logs and metrics can also be consumed with any Kubernetes-ready observability platform

Kubernetes Native API
Integration Components as Code

Integration Components as Code

Our integration components are API objects that can be managed declaratively from the command line, CI/CD pipeline or integrated in code. Less technical users benefit from the low-code TriggerMesh UI

Declaratively Event Driven

With Triggermesh, you get a full Event Driven platform powered by Knative. Our integrations inherit a strong sense of loose coupling, allowing for unlimited extensibility

Enterprises can use our platform out of the box to build applications that rely on Event-Driven Architectures and serverless.

Declaratively Event Driven Scheme

Bundled into Bridges

TriggerMeshKubernetesBridge

TriggerMesh application flows are bundled into Bridges – sets of Kubernetes objects that are deployed and tracked as a unit

Bridge
Api

Bridges provide information about the status of their components through a single API call

KustomizeBridgeObject

Kustomize, Helm, or other Kubernetes deployers can be used to generate Bridge objects

Bundled into Bridges

Integration Catalog

Zendesk Ticket Analysis

Use this Bridge to perform sentiment analysis on newly-created Zendesk Tickets.

AWS SQS to Sendgrid

This Bridge consumes messages from an AWS SQS queue and sends the content by email with SendGrid.

Slack to Google Sheets

Send messages from a Slack bot to a Google Sheet.

Cloud Services

Salesforce to Elasticsearch

Send Salesforce events to be indexed in Elasticsearch.

Cloud Services

Oracle Cloud Metrics to Datadog

Send Oracle Cloud metrics to Datadog.

Cloud Services

GitHub Events to SMS

Send SMS notifications via Twilio on GitHub push events.

Cloud Services

Azure Activity Logs to Splunk

This Bridge consumes Azure Activity Logs generated within an Azure Subscription and sends them as CloudEvents to Splunk, where they can be further analyzed and visualized.

Cloud Services

Slack to Confluent

Listen to Slack events and forward them to a Confluent Kafka cluster for further processing.

Cloud Services

GitLab to Elasticsearch

This Bridge forwards GitLab events from a specific repository to be indexed by Elasticsearch.

Enterprise providers

GitHub to AWS EventBridge

This Bridge listens to GitHub events from a specific repository and forwards these events to AWS EventBridge.

Enterprise providers

GitHub event display Bridge

This Bridge configures a GitHub event source and sends all received events to a service called event-display.

Enterprise providers

GitLab to AWS Lambda

This Bridge configures a GitLab event source to receive events from GitLab when a particular event happens in a repository, then the event is used to trigger the execution of a function in AWS Lambda.

Join our newsletter

Sign up for our newsletter for the latest news, training, and offers to help you build event-driven systems with TriggerMesh.