Softwr

Technology · head to head

Jenkins vs Make

Jenkins logo

Jenkins

Technology

A self-hosted automation server that can build almost anything, through a plugin ecosystem that is also its main liability.

From
Free
Rated
-
Full reviewWebsite
Make logo

Make

Remote Work

The platform for the new way of working

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Jenkins the controller is stateful and, in the open source distribution, has no high availability: build history, configuration and plugin state live on one filesystem, so every plugin upgrade and core update is downtime for every team using it, and a controller disk failure is a restore-from-backup event.; Make free tier limited to 1,000 credits per month
  • They diverge on capability: Jenkins covers Plugin ecosystem, Make covers Visual workflow builder.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Jenkins and Make actually diverge.

Attributes where Jenkins and Make differ
AttributeJenkinsMake
Pricing modelopen-sourcefreemium
PlatformsLinux, Windows, Macos, DockerWeb
CategoryTechnologyRemote Work
Founded20112013

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Jenkins

  • Plugin ecosystem
  • Distributed agents
  • Declarative and scripted pipelines
  • Shared libraries
  • Configuration as Code
  • Credentials management
  • Self-hosted anywhere
  • Multibranch and organisation folders

Only in Make

  • Visual workflow builder
  • Webhooks
  • API connectors
  • Conditional logic
  • Data transformation
  • Error handling
  • Scheduling
  • Team collaboration

What people use each for

The jobs each tool is most often brought in to do.

Jenkins

  • Builds that must touch physical hardware, such as embedded devices, test rigs or signing modules attached to a specific machinenot Make
  • Air-gapped or heavily regulated environments where a hosted CI runner cannot be used at allnot Make
  • Toolchains that hosted CI does not support, including node-locked commercial licences for EDA, CAD or simulation softwarenot Make
  • Organisations with years of existing Jenkins pipelines where the migration cost currently outweighs the operational cost of stayingnot Make

Make

  • Automating integrations between 3,000+ pre-built applicationsnot Jenkins
  • Building AI agents and workflow automation without extensive codingnot Jenkins
  • Enterprise automation with GDPR, SOC 2 Type II compliancenot Jenkins
  • Rapid deployment of automations from concept to livenot Jenkins

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Jenkins

  • The controller is stateful and, in the open source distribution, has no high availability: build history, configuration and plugin state live on one filesystem, so every plugin upgrade and core update is downtime for every team using it, and a controller disk failure is a restore-from-backup event.
  • Capability comes from around 1,900 community plugins of very uneven maintenance, and the Jenkins security team regularly publishes advisories for plugins whose maintainer has gone; in some cases the advisory itself states that no fix is available and the only remedy is to stop using it.
  • Plugin upgrades are coupled: one plugin can require a newer core or a newer version of another plugin, so applying a single security fix cascades into a coordinated upgrade of a dozen components on a timetable you did not choose.
  • Pipelines are Groovy running under a sandbox and a continuation-passing-style transformation, so ordinary Groovy constructs sometimes fail in non-obvious ways, and the debugging skill you build transfers to no other CI system.
  • It is free to licence and expensive to run: somebody must own the controller, the agents, the Java version, the credentials store and the plugin upgrade cycle, and that recurring staff cost is the usual reason organisations move to hosted CI even when Jenkins works.
  • Leaving is costly by construction, because shared libraries, plugin-specific pipeline steps and accumulated freestyle jobs have no mechanical translation into GitHub Actions or GitLab CI, so the migration is a rewrite whose price grows every year you defer it.

Make

  • Free tier limited to 1,000 credits per month
  • Free tier restricted to 2 active scenarios maximum
  • Free tier enforces 15-minute minimum scheduling interval
  • Credit-based model means costs scale with usage volume, not just features

Pricing, plan by plan

Jenkins

Free
  • Open SourceFree
    • Unlimited builds
    • 1000+ plugins
    • Self-hosted
  • CloudBees CI$undefined/month
    • Enterprise features
    • High availability
    • Role-based access

Make

Free

No published plan breakdown. See the Make review.

Which should you pick?

Choose Jenkins if

  • You need plugin ecosystem.
  • You want to start without paying.
  • You work on Linux, Windows, Macos, Docker.
  • You also want distributed agents.
Jenkins review

Choose Make if

  • You need visual workflow builder.
  • You want to start without paying.
  • You also want webhooks.
Make review

Questions people ask

Is Jenkins or Make better?
Neither clearly leads. Jenkins starts at Free and Make at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Jenkins or Make?
Jenkins starts at Free and Make at Free.
Does Jenkins or Make run on more platforms?
Jenkins runs on Linux, Windows, Macos, Docker. Make runs on Web.
Can I use Jenkins for free?
Both have a free tier, so you can try either at no cost before committing.
What is Jenkins best used for?
Jenkins is most often used for builds that must touch physical hardware, such as embedded devices, test rigs or signing modules attached to a specific machine, air-gapped or heavily regulated environments where a hosted ci runner cannot be used at all, toolchains that hosted ci does not support, including node-locked commercial licences for eda, cad or simulation software, organisations with years of existing jenkins pipelines where the migration cost currently outweighs the operational cost of staying. Of those, builds that must touch physical hardware, such as embedded devices, test rigs or signing modules attached to a specific machine and air-gapped or heavily regulated environments where a hosted ci runner cannot be used at all are not what Make is typically brought in for.
What can Jenkins do that Make cannot?
Jenkins covers Plugin ecosystem, Distributed agents, Declarative and scripted pipelines, Shared libraries. Make covers Visual workflow builder, Webhooks, API connectors, Conditional logic.

Answered from the vendors’ own pages

Jenkins: Why choose Jenkins over GitHub Actions or GitLab CI?

When the build needs something hosted runners cannot give you: physical hardware, an air-gapped network, a node-locked commercial tool licence, or an unusual platform. If none of those apply, hosted CI is usually less work to own.

Make: How is Make priced and does the free plan expire?

Make offers a free plan with 1,000 credits per month at no cost and no time limit. The free plan includes the no-code workflow builder, access to 3,000+ apps, and customer support. Paid tiers (Core, Pro, Teams) are $9-$29/month with 10,000+ credits included.

Source
Jenkins: Can Jenkins run in high availability?

Not in the open source distribution, which runs a single active controller. High availability and active-active controllers are features of CloudBees' commercial products. Open source deployments mitigate it with fast restores and, sometimes, multiple independent controllers.

Make: What happens if I exceed my monthly credits?

Extra credits beyond the monthly allowance can be purchased in bundles of 1,000 or 10,000. Auto-purchasing is available for Core, Pro, and Teams plans to automatically buy additional credits when needed.

Source
Jenkins: How risky are the plugins?

This is the main operational risk. Many plugins have a single volunteer maintainer, and Jenkins publishes security advisories for unmaintained plugins where no fix exists. Auditing which plugins you depend on and who maintains them should be a periodic task, not a one-off.

Make: Can I save money by switching to annual billing?

Yes, annual plans offer 15% or more savings compared to monthly billing. Monthly subscriptions continue until the end of the billing month, while annual plans run for 12 months.

Source
Jenkins: Do I need to know Groovy?

For declarative pipelines you can go a long way without it. Anything involving shared libraries, conditional logic or custom steps is Groovy, and it runs in a sandboxed, transformed environment where standard Groovy idioms sometimes behave unexpectedly.

Make: What happens to unused credits if I cancel?

Unused monthly credits expire at the end of each billing cycle. With annual subscriptions on Pro and Teams plans, credits are maintained for the full 12-month term. Users can cancel at any time and the organization converts to the free plan after the current billing cycle ends.

Source
Jenkins: What does it cost?

The software is free under the MIT licence. The cost is infrastructure and staff time to run controllers, agents and upgrades, plus a CloudBees subscription if you want high availability, support or centralised management of many controllers.

Make: How many active scenarios can I create on the free plan versus paid plans?

The free plan is limited to 2 active scenarios and has a 15-minute minimum interval between runs. Paid plans (Core and above) offer unlimited active scenarios with the ability to schedule runs down to the minute.

Source
Share

Related pages

More on Jenkins

More on Make

Keep looking

Other head to heads