What is TriggerMesh Open Sourcing?

We are open sourcing the TriggerMesh Cloud Native Integration Platform with a declarative API to compose event-driven applications using any combination of cloud services and on-premises applications. All of the following is available free and open source:

  • Declarative API 
  • To configure and create integrations between multiple endpoints. https://github.com/triggermesh/triggermesh
  • Catalog of Event Sources
  • Catalog of Event Targets (aka sinks)
  • Event Transformation
  • Declarative and function-based transformation of events.
  • Event Filters & Splitters
  • Filters events based on attributes or conditional expressions. Splits single events into multiple ones
  • Event Routing
  • Events are routed from an event  producer and then published to an event consumer. 
  • Autoscaling
  • Scale-up and scale-to-zero (via Knative Serving) 
  • TriggerMesh Integration Language 
  • An HCL-based configuration language to express integrations.   https://github.com/triggermesh/til
  • Command Line Interface (CLI)
  • Command-line interface to deploy TriggerMesh functions        https://github.com/triggermesh/tm 
  • Chart-based installation 
  • Use Helm to install the TriggerMesh platform
  • RBAC (Role-Based Access Controls)
  • Permission levels assigned to users using the Kubernetes RBAC API
  • Quotas
  • Quotas on sources, sinks, function, filters, splitters.

Why is TriggerMesh open sourcing the platform now?

We want to make it as easy as possible for everyone to build event-driven systems across any cloud and on-premises service. And in the world of DevOps, customers like trying things out before deploying them more fully. From early on, we knew that we wanted to both open source TriggerMesh and build an enduring business. Releasing high-quality open source software is part of this, and developing complementary products and services is the other part. Our team’s experience with other open source projects taught us that the most successful projects are backed by the resources to make the project successful. With this in mind, we built a platform that we thought would have a high-level of inherent value to our community users and then staffed up our developer relations and engineering to support our open source users. This Spring, we raised additional capital so we could expand our team with the aim of supporting our open source efforts. For example, we hired Matt Ray to head DevRel. Matt has helped DevOps users with the open source Chef project and did the same at Zenoss where he helped support a large open source community. In addition we have expanded our engineering team, which includes people who have built cloud native and systems management software like Kubeless, Knative, HelmPack, Apache CloudStack, Zenoss, Elastic, and many others.

What license are you using? Are there any limitations?

The TriggerMesh platform is licensed under the Apache Version 2.0 license, which means there are no restrictions on using the source code for any enterprise looking for a better way to build application flows and sync data across multiple clouds and their own data centers. TriggerMesh owns and will protect its trademarks. You may not commercially distribute TriggerMesh’s build artifacts or use TriggerMesh’s trademarked materials without written permission.

Is it open core? What’s your open source model?

The project is open source and we offer products that are complementary to TriggerMesh open source. These products are intended to enhance but not compete with the project. Examples of what we offer commercially are support and services for TriggerMesh Open Source, hosting services, and additional complex capabilities like organizational support and third-party integrations for products that aren't free and open source.

What are the best ways to contribute? Is the company looking for any particular types of contributions?

Right now, we’re looking for customers to try out TriggerMesh Open Source and evaluate how much faster it is to compose multi-cloud application flows. We’ve open sourced a lot of functionality to make it as easy as possible for everyone to use it and provide feedback. Issues in GitHub, documentation suggestions, pull requests, anything you think we can do to make TriggerMesh Open Source even better will be greatly appreciated. 

Where should developers go to get started?

We will be providing free training on TriggerMesh Open Source to help developers and cloud operators deploy and extend TriggerMesh. To register, please visit: https://www.triggermesh.com/oss-intro 

You can grab the code at: https://github.com/triggermesh/triggermesh

Why should we upgrade to the Starter Edition?

We believe TriggerMesh Open Source provides tremendous value to enterprises seeking a platform to wire together services across clouds without requiring hard-to-find, expert-level cloud engineers. Starter edition customers enjoy assistance from the Kubernetes and Knative experts at TriggerMesh with tasks like troubleshooting to ensure maximum uptime.


Other FAQs

Find answers to common questions or reach out to our support

Let’s start integrating

Connect services together to automate workflows and accelerate the flow of information across your organization.