Compare platforms and deployments
Use the six-option comparison to compare Golf self-hosted and Golf on Cloudflare with GitHub, GitLab, Bitbucket and Forgejo. The individual pages cover both Golf deployments and link to current vendor documentation:
Choose the deployment you will evaluate
Golf self-hosted uses Forgejo, a Go/React application and separate PostgreSQL ownership. Docker workers, agent services and private object storage have their own configuration. Start with Docker installation or the complete Kubernetes guide.
Golf on Cloudflare uses Artifacts Git, D1, Workers and Durable Objects, with approved Containers, orchestration, private outputs and protected previews. It runs in an operator’s Cloudflare account. Private access requires enrollment; self-service SaaS signup is unavailable. Read the Cloudflare setup and service inventory.
Check the workflow and the data
Test a disposable repository with the exact roles, workflow syntax, dependencies, secrets and preview type you need. Check permission revocation, unsupported jobs, uncertain responses and output access. Golf’s current native merge requires the same repository and an ancestor base; full protected merge and arbitrary production delivery remain open.
A Git clone does not verify migration of identities, private reviews, issues, attachments, LFS or pipeline configuration. Keep the existing platform until the required fidelity and recovery checks pass. The current capability guide identifies Golf’s evidence and remaining work.