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. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Envoyer vs Jenkins

Envoyer vs Jenkins

OverviewDecisionsComparisonAlternatives

Overview

Jenkins
Jenkins
Stacks59.2K
Followers50.4K
Votes2.2K
GitHub Stars24.6K
Forks9.2K
Envoyer
Envoyer
Stacks58
Followers80
Votes3

Envoyer vs Jenkins: What are the differences?

  1. Ease of Use: Envoyer is known for its simplicity and user-friendly interface, making it easy for users to deploy applications quickly without the need for extensive configuration. On the other hand, Jenkins is a more complex and robust tool that requires a steeper learning curve and setup process due to its extensive functionality and flexibility.

  2. Deployment Workflow: Envoyer streamlines the deployment process by providing a straightforward workflow that includes steps like pushing code changes, running scripts, and managing server configurations seamlessly. In contrast, Jenkins offers a wide range of customization options for creating complex pipelines and workflows, making it suitable for large-scale projects with intricate deployment requirements.

  3. Cost: Envoyer is a paid service, with pricing based on the number of servers and team members, while Jenkins is an open-source tool that is free to use. This difference in cost structure may influence the choice between the two tools, depending on the budget and requirements of the project.

  4. Scalability: Envoyer is designed to be a scalable solution that can handle deployments for projects of various sizes, from small startups to large enterprises. Jenkins, on the other hand, is also scalable but requires more manual configuration and maintenance as the project scales, making it ideal for teams with dedicated DevOps resources.

  5. Integration: Envoyer offers seamless integration with popular version control systems like GitHub, Bitbucket, and GitLab, simplifying the process of deploying code from repositories. Jenkins, on the other hand, boasts a vast array of plugins that enable integration with a wide range of tools and services, providing unparalleled flexibility in building automated pipelines.

  6. Monitoring and Reporting: Envoyer includes basic monitoring and reporting features that give users insights into the deployment process and server health. In comparison, Jenkins offers more advanced monitoring capabilities through plugins, allowing for in-depth tracking of deployment metrics and performance statistics.

In Summary, Envoyer emphasizes ease of use, streamlining the deployment process, and adapting pricing, while Jenkins stands out for its scalability, customization options, integration capabilities, and advanced monitoring features.

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

Advice on Jenkins, Envoyer

Balaramesh
Balaramesh

Apr 20, 2020

Needs adviceonAzure PipelinesAzure Pipelines.NET.NETJenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k
Comments
StackShare
StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k
Comments
Tatiana
Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k
Comments

Detailed Comparison

Jenkins
Jenkins
Envoyer
Envoyer

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Envoyer deploys your PHP applications with zero downtime. Just push your code, and let Envoyer deliver your application to one or many servers without interrupting a single customer. In this series, we'll discuss each feature of Envoyer, demonstrating how to use them with a sample project.

Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
GitHub / Bitbucket Integration;Seamless Deployment Rollbacks;Deploy To Multiple Servers;Easy Environment Syncing;Application Health Checks;Cron Job Monitoring;Integrated Chat Notifications;Deploy Any PHP Project;Unlimited Team Members;Unlimited Deployments;Customize Your Deployments;Tuned For Laravel
Statistics
GitHub Stars
24.6K
GitHub Stars
-
GitHub Forks
9.2K
GitHub Forks
-
Stacks
59.2K
Stacks
58
Followers
50.4K
Followers
80
Votes
2.2K
Votes
3
Pros & Cons
Pros
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
Cons
  • 13
    Workarounds needed for basic requirements
  • 10
    Groovy with cumbersome syntax
  • 8
    Plugins compatibility issues
  • 7
    Lack of support
  • 7
    Limited abilities with declarative pipelines
Pros
  • 3
    Easy to use
Integrations
No integrations available
PHP
PHP
Laravel
Laravel
GitHub
GitHub
Bitbucket
Bitbucket
HipChat
HipChat
Slack
Slack

What are some alternatives to Jenkins, Envoyer?

Heroku

Heroku

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

Clever Cloud

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

CircleCI

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Google App Engine

Google App Engine

Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.

Red Hat OpenShift

Red Hat OpenShift

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot