Forgejo
Choose Forgejo on its own when its Git collaboration and Actions runner model meet your needs. You can operate a forge without adding the Golf control plane.
GOLF Resources / Compare
Golf vs Forgejo
Golf self-hosted builds on Forgejo. Forgejo owns canonical Git and collaboration; Golf adds its shared interface, credential/session handling and selected execution workflows. Golf on Cloudflare uses Artifacts and D1 instead.
Reviewed October 14, 2026 · editions and plans matter01 / WHERE EACH FITS
Start with your requirements.
Golf self-hosted
Evaluate Golf self-hosted when you want the Golf interface and its supported workflow around Forgejo. You still maintain Forgejo and PostgreSQL, plus Golf and any separately enrolled execution or agent services.
Golf on Cloudflare
Evaluate Golf on Cloudflare when you want the native Artifacts/D1/Workers architecture. This deployment does not run Forgejo behind the scenes. Its collaboration and merge surface is currently narrower than the Forgejo product.
02 / CAPABILITIES AND OWNERSHIP
Compare the deployment you will run.
The Golf columns describe the developer preview. Cloudflare manages the provider services; the operator still manages Golf policy, account access, resources and recovery.
| Compare | Forgejo | Golf self-hosted | Golf on Cloudflare |
|---|---|---|---|
| Hosting | Self-hostable forge; hosting providers may operate their own Forgejo instances.Forgejo documentation ↗ | Your Docker or Kubernetes infrastructure. Forgejo, Golf Go/React and PostgreSQL. | Operator-hosted in a Cloudflare account. Workers, Artifacts Git, D1 and Durable Objects; no Forgejo origin. |
| Git and collaboration | Git, issues, pull requests, reviews and repository access controls.Forgejo documentation ↗ | Supported Forgejo APIs, shared source/issues/PR interface and current repository permissions. | Native source, issues, PRs and reviews. Current merge requires the same repository and an ancestor base. |
| Storage and registries | Git repositories and package registries, including container images.Forgejo documentation ↗ | Forgejo owns Git; separate PostgreSQL databases hold Golf/forge state. Execution uses configured private object storage. | Artifacts owns Git, D1 holds domain state, R2 retains private outputs and the managed registry holds images. |
| CI and runners | Forgejo Actions with a separately configured runner; workflow compatibility has documented differences.Forgejo documentation ↗ | Configured Docker workers and tested Actions/GitLab profiles. Full workflow compatibility is incomplete. | Queues and Workflows coordinate approved Containers. Exact-source checks have hosted proof; arbitrary pipelines are unsupported. |
| AI and agents | Forgejo Actions with a separately configured runner; GitHub Actions differences are documented.Forgejo documentation ↗ | Optional configured agent accounts and scoped tasks. Each harness needs its own setup and testing. | Optional Clef metadata advice and tested proposals through Workers AI/AI Gateway. Demo proposals edit one approved file. |
| Previews and delivery | Use runner workflows and your chosen deployment infrastructure.Forgejo documentation ↗ | Available provider/profile integrations. The Helm core does not install the entire execution or delivery stack. | Protected expiring R2/static and Workers for Platforms app previews. General production promotion/rollback is incomplete. |
| Operations | You or your hosting provider manage the forge, database/storage, upgrades, backups and runner isolation.Forgejo documentation ↗ | You own images, credentials, storage, networking, upgrades and recovery. One-node core Kubernetes proof passed. | Cloudflare manages provider services. You still own account policy, grants, images, resource lifecycle, costs and recovery. |
| Fit and current limits | A choice for running a forge on your terms. Golf portable uses Forgejo rather than replacing its Git engine.Forgejo documentation ↗ | Evaluate an owned developer workflow. Full recovery, production HA and retained migration fidelity remain open. | Evaluate the native Cloudflare workflow. Enrolled private access; no self-service SaaS signup. Analytics/Cron gaps remain. |
See Golf’s current evidence, Kubernetes installation and Cloudflare service inventory. Full workflow parity, protected merge, production delivery and coordinated recovery remain open. Vectorize search is in development.
03 / EVALUATION
Check these before a migration.
- Identify which responsibilities stay in Forgejo and which Golf stores in its own database.
- Golf’s bundled Forgejo profile disables native Actions; separately configured Golf workers run supported profiles.
- Use supported Forgejo APIs and Git transport. Never treat direct database or repository-file edits as an integration.
- Verify migration and coordinated recovery for identities, private reviews, Git data and encryption keys.
Try Golf with a disposable repository.
Explore the browser simulations or run an owned installation. Keep your existing platform until the required data and workflow checks pass.