TriggerMesh Brings Eventing to DigitalOcean

Easily build event-driven applications

Open-source AWS EventBridge alternative
Unified eventing experience
Developer-friendly CLI
Runs on Docker or natively on Kubernetes
Get started
Illustration of how TriggerMesh works

Trusted by

Adenza
Colruyt
CrowdStrike
GitLab
ManoMano
Motorq
PNS Bank
Pragna
Prometric
SAP
Snyk
WMWARE
Adenza
Colruyt
CrowdStrike
GitLab
ManoMano
Motorq
PNS Bank
Pragna
Prometric
SAP
Snyk
WMWARE

Easily capture, route, and deliver events

Get started and create your first Broker in minutes.Then, create event source and targets. Pick between an interactive CLI or declarative YAML configuration.
Get started
$
brew install triggermesh/cli/tmctl
Copied
$
tmctl create broker mybroker
Copied
$
tmctl send-event {“hello”:”world”}
Copied
$
curl -sSfL https://raw.githubusercontent.com/triggermesh/tmctl/HEAD/hack/install.sh | sh
Copied
$
tmctl create broker mybroker
Copied
$
tmctl send-event {“hello”:”world”}
Copied
$
tmctl create source awss3 --eventTypes s3:ObjectCreated:* --arn <bucket:arn>
Copied
$
tmctl create target cloudevents --endpoint https://example.com/my-function --source mybroker-awss3source
Copied
apiVersion: sources.triggermesh.io/v1alpha1
kind: AWSS3Source
metadata:
  name: s3source
spec:
  arn: <arn>

  eventTypes:
  - s3:ObjectCreated:*

  auth:
    credentials:
      accessKeyID:
        valueFromSecret:
          name: awscreds
          key: aws_access_key_id
      secretAccessKey:
        valueFromSecret:
          name: awscreds
          key: aws_secret_access_key

  sink:
    ref:
      apiVersion: eventing.triggermesh.io/v1alpha1
      kind: RedisBroker
      name: mybroker

---

apiVersion: eventing.triggermesh.io/v1alpha1
kind: Trigger
metadata:
  name: s3trigger
spec:
  broker:
    kind: RedisBroker
    group: eventing.triggermesh.io
    name: mybroker
  filters:
  - any:
    - exact:
        type: s3:ObjectCreated:*
  target:
    ref:
       apiVersion: v1alpha1
       kind: CloudEventsTarget
       name: mybroker-cloudeventstarget

---

apiVersion: targets.triggermesh.io/v1alpha1
kind: CloudEventsTarget
metadata:
  name: mybroker-cloudeventstarget
spec:
  endpoint: https://example.com/my-function
$
tmctl create source awscodecommit --arn <arn> --branch master --eventTypes com.amazon.codecommit.pull_request
Copied
$
tmctl create target cloudevents --endpoint https://example.com/pii-scan-function.py --source broker-awscodecommitsource
Copied
apiVersion: sources.triggermesh.io/v1alpha1
kind: AWSCodeCommitSource
metadata:
  name: mybroker-awscodecommitsource
spec:
  arn: <arn>
  branch: master

  eventTypes:
  - pull_request

  auth:
    credentials:
      accessKeyID:
        valueFromSecret:
          name: awscreds
          key: aws_access_key_id
      secretAccessKey:
        valueFromSecret:
          name: awscreds
          key: aws_secret_access_key

  sink:
    ref:
      apiVersion: eventing.triggermesh.io/v1alpha1
      kind: RedisBroker
      name: mybroker

---

apiVersion: eventing.triggermesh.io/v1alpha1
kind: Trigger
metadata:
  name: codecommittrigger
spec:
  broker:
    kind: RedisBroker
    group: eventing.triggermesh.io
    name: mybroker
  filters:
  - any:
    - exact:
        type: com.amazon.codecommit.pull_request
  target:
    ref:
       apiVersion: v1alpha1
       kind: CloudEventsTarget
       name: mybroker-cloudeventstarget

---

apiVersion: targets.triggermesh.io/v1alpha1
kind: CloudEventsTarget
metadata:
  name: mybroker-cloudeventstarget
spec:
  endpoint: https://example.com/pii-scan-function.py
$
tmctl create source googlecloudauditlogs --serviceName reports.googleapis.com --methodName google.admin.reports.v1.suspicious_login --pubsub.project my-project --serviceAccountKey $(cat ./key.txt)
Copied
$
tmctl create target kafka --topic suspicious-logins --bootstrapServers 127.0.0.1:47561 --source broker-googlecloudauditlogs
Copied
apiVersion: sources.triggermesh.io/v1alpha1
kind: GoogleCloudAuditLogsSource
metadata:
  name: auditlogssource
spec:
  serviceName: reports.googleapis.com
  methodName: google.admin.reports.v1.suspicious_login

  pubsub:
    project: my-project
    # Alternatively, provide a pre-existing Pub/Sub topic:
    # topic: projects/my-project/topics/my-topic

  serviceAccountKey:
    value: >-
      {
        "type": "service_account",
        "project_id": "my-project",
        "private_key_id": "0000000000000000000000000000000000000000",
        "private_key": "-----BEGIN PRIVATE KEY-----\nMIIE...\n-----END PRIVATE KEY-----\n",
        "client_email": "triggermesh-auditlogs-source@my-project.iam.gserviceaccount.com",
        "client_id": "000000000000000000000",
        "auth_uri": "https://accounts.google.com/o/oauth2/auth",
        "token_uri": "https://oauth2.googleapis.com/token",
        "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
        "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/triggermesh-auditlogs-source%40my-project.iam.gserviceaccount.com"
      }

  sink:
    ref:
      apiVersion: eventing.triggermesh.io/v1alpha1
      kind: RedisBroker
      name: mybroker

---

apiVersion: eventing.triggermesh.io/v1alpha1
kind: Trigger
metadata:
  name: auditlogstrigger
spec:
  broker:
    kind: RedisBroker
    group: eventing.triggermesh.io
    name: mybroker
  filters:
  - any:
    - exact:
        type: com.google.cloud.auditlogs.message
  target:
    ref:
       apiVersion: v1alpha1
       kind: KafkaTarget
       name: mybroker-kafkatarget

---

apiVersion: targets.triggermesh.io/v1alpha1
kind: KafkaTarget
metadata:
  name: mybroker-kafkatarget
spec:
  bootstrapServers:
  - 127.0.0.1:47561
  topic: suspicous-logins
  auth:
    saslEnable: true
    tlsEnable: false
    securityMechanism: PLAIN
    username: admin
    password:
      value: admin-secret

Introducing TriggerMesh

Who is it For?

Icon

Platform Engineers

Empower developers in your organization to write code that reacts to events from any cloud service or in-house application. Increase agility and reduce lead time. Keep producers and consumers decoupled.

See how ManoMano does it
Icon

Integration Developers

Connect SaaS applications and on-prem systems to unleash new productivity and innovation. Be agile and incremental and avoid bottlenecks.

Checkout our list of connectors
Icon

B2B Software Vendors

Grow your business by expanding your target market and landing more deals. TriggerMesh lets you quickly add new event flows and integrations to your software without disrupting core R&D efforts.

Ingest 3rd-party cloud audit logs

How It Works

Brokers provide unified access to events

Events from all sources are centralized in a broker in a standard format based on CloudEvents. Uniformly use Triggers to filter for specific events and route them to any destination.

A broker can be memory-only, backed Redis for durability, or leverage Knative.

Easily transform events

Add, move, or delete, or modify event metadata or content to match the requirements of event consumers. Remove useless fields to save bandwidth or hide sensitive information.

Use the TriggerMesh low-code transformation language, or for more flexibility you can write functions in python, node or ruby.

Built-in event types and schemas

When you connect a new source to a broker, it will know the types of events produced by that source. Use this information to simplify the writing of filters and transformations.

Archive and replay past events (preview)

TriggerMesh lets you archive events to longer term storage to be replayed at a later time.

Replay events to a new consumer, or recover from an issue by replaying already processed events to a recently patched service.

Run on Docker or natively on Kubernetes

TriggerMesh runs natively in Kubernetes thanks to its open-source custom resources and controllers. Bring events from any source into any containerised environment. Handle scaling, reliability, and auth the Kubernetes way.

It now also runs on just Docker, for easy local development and simpler deployments.

Connectors

Effortlessly integrate with the most popular event sources and destinations, or use standards like HTTP to ingest and deliver events to and from anywhere.
Solace
Solace
MongoDB
MongoDB
CloudEvents
CloudEvents
Azure Sentinel
Azure Sentinel
Google Cloud Audit Logs
Google Cloud Audit Logs
Azure Service Bus
Azure Service Bus
Azure Queue Storage
Azure Queue Storage
Google Cloud Billing
Google Cloud Billing
Google Cloud Workflows
Google Cloud Workflows
Google Cloud Firestore
Google Cloud Firestore
Alibaba OSS
Alibaba OSS
AWS Comprehend
AWS Comprehend
AWS CloudWatch Logs
AWS CloudWatch Logs
AWS CloudWatch
AWS CloudWatch
IBM MQ
IBM MQ
Jira
Jira
Azure IoT Hub
Azure IoT Hub
Azure EventGrid
Azure EventGrid
Solace
Solace
MongoDB
MongoDB
CloudEvents
CloudEvents
Azure Sentinel
Azure Sentinel
Google Cloud Audit Logs
Google Cloud Audit Logs
Azure Service Bus
Azure Service Bus
Azure Queue Storage
Azure Queue Storage
Google Cloud Billing
Google Cloud Billing
Google Cloud Workflows
Google Cloud Workflows
Google Cloud Firestore
Google Cloud Firestore
Alibaba OSS
Alibaba OSS
AWS Comprehend
AWS Comprehend
AWS CloudWatch Logs
AWS CloudWatch Logs
AWS CloudWatch
AWS CloudWatch
IBM MQ
IBM MQ
Jira
Jira
Azure IoT Hub
Azure IoT Hub
Azure EventGrid
Azure EventGrid
Zendesk
Zendesk
OCIMetrics
OCIMetrics
Tekton
Tekton
Splunk
Splunk
SendGrid
SendGrid
Logz.io
Logz.io
Hasura
Hasura
Datadog
Datadog
AWS EventBridge
AWS EventBridge
Azure Blob Storage
Azure Blob Storage
Azure Activity Logs
Azure Activity Logs
Salesforce
Salesforce
Webhooks
Webhooks
Google Storage
Google Storage
AWS S3
AWS S3
AWS Kinesis
AWS Kinesis
AWS SNS
AWS SNS
AWS Lambda
AWS Lambda
Zendesk
Zendesk
OCIMetrics
OCIMetrics
Tekton
Tekton
Splunk
Splunk
SendGrid
SendGrid
Logz.io
Logz.io
Hasura
Hasura
Datadog
Datadog
AWS EventBridge
AWS EventBridge
Azure Blob Storage
Azure Blob Storage
Azure Activity Logs
Azure Activity Logs
Salesforce
Salesforce
Webhooks
Webhooks
Google Storage
Google Storage
AWS S3
AWS S3
AWS Kinesis
AWS Kinesis
AWS SNS
AWS SNS
AWS Lambda
AWS Lambda
Apache Kafka
Apache Kafka
OracleDB
OracleDB
Azure Event Hubs
Azure Event Hubs
AWS Code Commit
AWS Code Commit
AWS SQS
AWS SQS
AWS Dynamo DB
AWS Dynamo DB
AWS Cognito
AWS Cognito
Google Pub/Sub
Google Pub/Sub
Google Sheets
Google Sheets
AWS EventBridge
AWS EventBridge
AWS lambda
AWS lambda
Confluent
Confluent
Elasticsearch
Elasticsearch
Zendesk
Zendesk
Slack
Slack
Twilio
Twilio
GitHub
GitHub
Apache Kafka
Apache Kafka
OracleDB
OracleDB
Azure Event Hubs
Azure Event Hubs
AWS Code Commit
AWS Code Commit
AWS SQS
AWS SQS
AWS Dynamo DB
AWS Dynamo DB
AWS Cognito
AWS Cognito
Google Pub/Sub
Google Pub/Sub
Google Sheets
Google Sheets
AWS EventBridge
AWS EventBridge
AWS lambda
AWS lambda
Confluent
Confluent
Elasticsearch
Elasticsearch
Zendesk
Zendesk
Slack
Slack
Twilio
Twilio
GitHub
GitHub

Case Studies

Taegis XDR

Stream new security events into Secureworks TaegisXDR

As the threat landscape evolves, it's essential to be able to add new security event streams to TaegisXDR. TriggerMesh has experience working with Secureworks customers to ingest security events into TaegisXDR from sources that aren't natively supported out of the box.

Learn how
ManoMano

Accelerate Event Driven Test Engineering at ManoMano

TriggerMesh is scratching ManoMano’s itch to reduce the number of idling containers that waste valuable compute resources, while also providing developers with an easy way to deploy their code that consumes AWS events.

Read the blog post
PNC

Fortune 500 Bank Automates Software Supply Chain Security with TriggerMesh

The previously manual 30-day process now runs automatically and finishes in a few hours.

All event processing code runs as auto-scalable serverless functions, easily accommodating demand peaks, and only consuming the compute resources needed.

PNC case study
Salesforce

Global FinTech Accelerates Event Flow from Salesforce to On-premises Kafka

The streamlined EDA with TriggerMesh reduced complexity by 50%, significantly speeding up the implementation of new Application Flows between Salesforce and Kafka. The simplified architecture also reduces technical debt and shrinks the attack surface, making the systems even more stable and secure.

Check out the use case

Create your first event flow in under 5 minutes