StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Task Scheduling
  4. Remote Server Task Execution
  5. Gunnery vs StackStorm

Gunnery vs StackStorm

OverviewComparisonAlternatives

Overview

Gunnery
Gunnery
Stacks2
Followers11
Votes1
GitHub Stars765
Forks72
StackStorm
StackStorm
Stacks80
Followers186
Votes31
GitHub Stars6.4K
Forks774

Gunnery vs StackStorm: What are the differences?

Developers describe Gunnery as "Multipurpose task execution tool for distributed systems with web-based interface". If your application is divided into multiple servers, you are probably connecting to them via ssh and executing over and over the same commands. Clearing caches, restarting services, backups, checking health. Wouldn't it be cool if you could do that from browser or smartphone? Gunnery is here for you!. On the other hand, StackStorm is detailed as "Open Source IFTTT for Ops: event-driven automation, security responses, auto-remediation with workflow engine & ChatOps". StackStorm is a platform for integration and automation across services and tools. It ties together your existing infrastructure and application environment so you can more easily automate that environment -- with a particular focus on taking actions in response to events.

Gunnery and StackStorm can be primarily classified as "Remote Server Task Execution" tools.

Some of the features offered by Gunnery are:

  • Support for wide variety of tools
  • Designed for distributed systems
  • Usable for deployment, service control, backups

On the other hand, StackStorm provides the following key features:

  • Automations tie events to actions you’d like to take, using a rules engine and, if you want, comprehensive workflow. Automations are your operational patterns summarized as code.
  • StackStorm automations work either by starting with your existing scripts – just add simple meta data – or by authoring the automations within StackStorm.
  • Automations are the heart of StackStorm – they allow you to share operational patterns, boost productivity, and automate away the routine.

Gunnery and StackStorm are both open source tools. It seems that StackStorm with 3.32K GitHub stars and 439 forks on GitHub has more adoption than Gunnery with 685 GitHub stars and 72 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Gunnery
Gunnery
StackStorm
StackStorm

If your application is divided into multiple servers, you are probably connecting to them via ssh and executing over and over the same commands. Clearing caches, restarting services, backups, checking health. Wouldn't it be cool if you could do that from browser or smartphone? Gunnery is here for you!

StackStorm is a platform for integration and automation across services and tools. It ties together your existing infrastructure and application environment so you can more easily automate that environment -- with a particular focus on taking actions in response to events.

Support for wide variety of tools ; Designed for distributed systems ; Usable for deployment, service control, backups ; Secure remote execution ; Web-based interface ; User notifications
Automations tie events to actions you’d like to take, using a rules engine and, if you want, comprehensive workflow. Automations are your operational patterns summarized as code.;StackStorm automations work either by starting with your existing scripts – just add simple meta data – or by authoring the automations within StackStorm.;Automations are the heart of StackStorm – they allow you to share operational patterns, boost productivity, and automate away the routine.;CLI, REST API + Python Bindings
Statistics
GitHub Stars
765
GitHub Stars
6.4K
GitHub Forks
72
GitHub Forks
774
Stacks
2
Stacks
80
Followers
11
Followers
186
Votes
1
Votes
31
Pros & Cons
Pros
  • 1
    Remote deploy
Pros
  • 7
    Auto-remediation
  • 5
    Integrations
  • 4
    Automation
  • 4
    Complex workflows
  • 3
    Open source
Cons
  • 3
    Complexity
  • 1
    There are not enough sources of information
Integrations
No integrations available
Mailgun
Mailgun
VMware vSphere
VMware vSphere
Rackspace Cloud Servers
Rackspace Cloud Servers
Vault
Vault
Octopus Deploy
Octopus Deploy
Ansible
Ansible
Duo
Duo
PhantomJS
PhantomJS
Yammer
Yammer
Cassandra
Cassandra

What are some alternatives to Gunnery, StackStorm?

Runbook

Runbook

Runbook is a SaaS application that monitors your servers and performs automated tasks when your monitors fails. Use Runbook to automatically recover from application crashes and unexpected failure without interrupting your service or your well earned sleep!

Neptune.io

Neptune.io

Neptune.io is a SaaS platform to automate your incident response. It integrates with your monitoring and alerting tools like NewRelic, Nagios, Pagerduty, CloudWatch etc. and lets you automate the remediation easily and much more.

Runops

Runops

Secure access to the Cloud with a single CLI. You run a SQL query and it goes to Runops instead of the database. We get peer reviews in Slack, run it, and remove sensitive data from results.

Burst

Burst

It lets you run your software remotely in the cloud, on powerful GPU's or multi-CPU hardware instances that are booted up and stopped automatically, so you only pay for the time you use.

Routine Ops

Routine Ops

Execute. Iterate. Improve. Build your organization's playbook with Routine Ops. Built for teams. Free for individuals.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana