Golf on Cloudflare

The native hosted product uses Artifacts / D1 / Workers, independently of the portable Forgejo / Go / PostgreSQL deployment. The reviewed engineering deployment used Alchemy; the Python / native cf setup path remains available.

Start with the architecture, complete service inventory, setup and current status.

What the hosted workflow incorporates

• Artifacts Git and D1 collaboration, plus shared React/Connect product pages.
• SQLite Durable Objects, Queues and Workflows coordinating approved container checks and proposal jobs.
• Private R2 reports, contexts, bundles and bounded file uploads; managed container image registry.
• Access, custom domains/TLS, a Preview Worker and Workers for Platforms app dispatch with explicit outbound policy.
• Workers AI / AI Gateway for Clef advice and optional code proposals; Browser Run snapshots.
• Secrets Store, encrypted repository values, own-address Email Service notifications and signed webhook delivery.
• Operations, optional Analytics Engine, provider Worker analytics/logs, rate limiting, Cron Triggers and a Durable Object maintenance fallback.

The service inventory distinguishes bindings from successful consumers. Some features are optional, locally qualified, degraded or roadmap-only. Having a binding does not make every feature ready.

Provider requirements

Account eligibility, domain ownership, Access identity enrollment, supported images, scoped API permissions and resource limits are installation prerequisites. The Alchemy beta is deployment tooling, not an application dependency. Private input/state remains local and out of Git.

The full native product, arbitrary production deployments, general workflow compatibility, tenant onboarding and production scale remain acceptance work. AI is optional; no missing integration is replaced with mock success.