Appcircle vs Jenkins

Appcircle offers an always-free Starter plan with limited monthly builds, and a Corporate plan with tailored, customizable limits priced through annual licensing.

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.

The free Starter plan includes 1 concurrent build, 30-minute max build time, 20 builds per month, 1,000 CodePush updates, and 100 Testing Distribution downloads per month.

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.

Corporate plans use an annual licensing model with bank transfer payments due within 30 days of invoicing, and usage against limits can be tracked in the billing dashboard.

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.

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.

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.