AppVeyor vs Semaphore

What AppVeyor is

AppVeyor is a hosted continuous-integration service with YAML or UI build configuration, build matrices, hosted workers and bring-your-own-cloud workers. Its public free tier is scoped to open-source projects; private-project allowances, concurrent jobs and self-hosted job capacity vary by paid plan.

What Semaphore is

Semaphore is a CI/CD platform offered as a managed cloud service, a free open-source Community Edition and a commercial self-hosted Enterprise Edition. Cloud pipelines are stored as YAML under .semaphore, can use hosted or self-hosted agents, and are billed from compute, storage, transfer and optional support usage rather than one flat subscription.

What AppVeyor is built to do

YAML or UI configuration

Defines the pipeline in appveyor.yml or through project settings, with documented precedence rules.

Build matrix

Expands selected environment dimensions into separate build jobs.

Build workers

Runs jobs on hosted environments or qualifying self-hosted and BYOC capacity.

Secure variables

Encrypts secret values for YAML and restricts their default use in pull-request builds.

What Semaphore is built to do

YAML pipelines

Connects dependency-aware blocks and jobs from files in the .semaphore directory.

Hosted and self-hosted agents

Runs jobs on listed cloud machines or customer-managed agent capacity.

Secrets

Injects governed environment variables or files into selected jobs and pipelines.

Promotions

Chains pipelines into release and deployment workflows with configurable conditions.

Choose AppVeyor if

• Open-source projects that fit the public-project free tier and one hosted concurrent job
• Teams expressing multi-environment builds through a repository YAML file
• Organizations combining hosted CI control with their own worker infrastructure

Skip AppVeyor if

• A private project must remain on a free hosted plan
• Required concurrent or self-hosted capacity exceeds the acceptable subscription cost
• Your scripts cannot be hardened to fail reliably and keep secrets out of logs

Choose Semaphore if

• Teams versioning multi-stage build, test and deployment workflows in YAML
• Workloads that benefit from mixing hosted compute with customer-managed agents
• Organizations able to forecast compute minutes, artifact usage and support needs

Skip Semaphore if

• Hosted Windows workers are required and self-hosting is not acceptable
• Your procurement process requires a single fixed all-inclusive price
• No owner can maintain pipeline YAML, secrets, agents and usage controls

AppVeyor: pros & cons

• Repository configuration: Builds can be defined in appveyor.yml and carried with the source repository.
• Build matrices: Creates jobs across selected operating systems, platforms, configurations and environment variables.
• Hosted and self-hosted execution: Pricing documents Windows, Linux and macOS options plus BYOC workers.
• Secret variables: Account-specific encryption supports protected values in visible YAML files.
• Narrow free scope: The listed free plan is for unlimited public open-source projects, not private repositories.
• Concurrency queue: Jobs beyond the plan's concurrent-job allowance wait for capacity.
• Plan limits: Private projects, concurrent hosted jobs and simultaneous self-hosted jobs differ by tier.
• Script error handling: AppVeyor warns that PowerShell non-terminating errors can leave a build reported as successful unless configured to stop.

Semaphore: pros & cons

• Deployment choice: Offers managed cloud, open-source Community Edition and commercial self-hosted editions.
• Repository pipelines: Defines connected blocks, dependencies, jobs and promotions in versioned YAML files.
• Execution options: Cloud supports Linux, Docker and macOS agents, while self-hosted agents add customer-controlled machines.
• Usage visibility: Current pricing publishes per-minute compute and separate artifact allowances and overages.
• Variable monthly cost: Machine minutes, artifact transfer, storage and optional services can all affect spend.
• Platform boundary: Hosted Windows jobs are not listed; Windows is documented through self-hosted agents.
• Operational burden shifts: Community or self-hosted deployment requires the customer to operate its own CI infrastructure.
• Support tiers are separate: Advanced troubleshooting, response commitments and engineering assistance are paid additions.