Who supplies the machine that runs your build?

Buildkite schedules jobs. A build agent is the worker that runs one. Choose Buildkite-hosted workers or workers you maintain. Pipeline steps can live in a repository file or the Buildkite editor. Keep a record of which workers have the tools the build needs.

Can everyone who starts a build unblock a release?

A block step can make a build wait. Buildkite documents restricting who unblocks a step with allowed teams. Verify the pipeline’s permission and team settings, and check whether any separate release path could act without that review.

What should you budget for on both kinds of workers?

Compare the user allowance and plan limits on simultaneous self-hosted jobs. Your own workers still use compute you provide. For hosted workers, check machine type, included compute and metered usage. Save important build outputs separately from the plan’s artifact retention.

Who can approve the build after it moves to a different worker?

Draw the same passing build on two fictional workers. Give both the same release rule and expected output.

Check the work before the pause
Write down which output file both workers should produce.
Check the decision
Only the release team should be able to clear the fictional block. Name the output they would review.