StackStorm joins the Charm Partner Programme

Ellen Arnold

on 19 December 2014

StackStorm is the newest member of Canonical’s Charm Partner Programme.  StackStorm is an operations automation software that enables users to define and share operational patterns from events and triggers through to actions taken in response.

“Both Canonical and StackStorm share a common goal in helping to alleviate common pain points for our end users, enabling them to focus more of their attention on delivering solutions.  Together we can do this more effectively,” says Milan Vaclavik, who leads business development for cloud infrastructure ISVs at Canonical.

Evan Powell, CEO of StackStorm says; “We’re excited about working with Canonical to assist their customers in the automation of today’s increasingly complex and fast moving environments.”

Canonical’s Charm Partner Programme lets solution providers make best use of Canonical’s cloud orchestration tool, Juju, enabling instant integration, scaling at the click of a button, simple to share blueprint deployments and an easy way to deliver solutions in minutes.

Talk to us today

Interested in running Ubuntu in your organisation?

Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

By submitting this form, I confirm that I have read and agree to Canonical's Privacy Policy.

Related posts

Building an open source chain of trust: new research uncovers key blockers and ways forward

Canonical is pleased to share its latest research report, “The open source chain of trust.” Based on a survey of 500 DevOps professionals, the report...

Beyond safety and security: Why automotive open source demands dependability 

In the traditional automotive world, teams often work in silos: the cybersecurity experts lock down the ports, the quality assurance teams hunt for bugs, and...

DirtyClone Linux kernel local privilege escalation vulnerability fixes available

On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been...