Bitrise vs Buddy

Bitrise's REST API drives its mobile-focused CI/CD platform: triggering builds, reading build and workflow logs, and managing apps, webhooks, and cache across a project's pipelines. A live unauthenticated GET against api.bitrise.io/v0.1/me returned a clean 401 Unauthorized JSON body while still carrying access-control-allow-origin: * on both the request and an OPTIONS preflight, confirming the personal-access-token auth model and resolving its previously unknown CORS support to open. Its own pricing page offers a free Hobby tier for individual developers alongside paid team plans, so this is a freemium product, not a flat-fee one.

Buddy's REST API manages its visual CI/CD pipelines end to end — projects, actions, environments, runs, sandboxes, and Git operations — and is described as covering the same permission model as the web app itself. Its docs state plainly that authentication is performed with OAuth2, sending requests with a Bearer access_token, which this run reconfirmed live: an unauthenticated call to api.buddy.works/user returned a 401 "Wrong authentication data" response while still carrying access-control-allow-origin: * on both the request and its OPTIONS preflight, resolving the previously unknown CORS support to open. Buddy's own pricing page lists a free plan (limited pipeline minutes and one seat) alongside paid Pro and Hyper tiers, making it freemium rather than a flat fee.