Skip to main content
Version: Alpha

Local, Docker, Kubernetes and hosted

ProfileCoreExecutionOperator responsibility
Local Docker ComposeGolf React/Go, Forgejo, separate PostgreSQL roles/databasesOptional enrolled Docker workers and private object storagePrivate environment files, account enrollment, loopback origins, persistent volumes
Docker beyond localhostSame portable core with explicit secure public originsExplicitly configured workers/agentsTLS, DNS, credential storage, network policy, backup/restore acceptance
Kubernetes / HelmGolf replicas, Forgejo and optional bundled PostgreSQLCore chart does not install Docker runners or every agent serviceExact image, existing namespace Secret, storage, ingress and enforcing CNI
Native CloudflareWorkers, Artifacts Git, D1, SQLite Durable ObjectsQueues, Workflows, approved Containers and optional proposalsAccount eligibility, domain, Access enrollment, resource/token ownership, quotas and cleanup

These are infrastructure choices, not separate product editions. Optional provider adapters do not transfer canonical ownership automatically.

Portable release boundary​

Current portable installations, including fresh Compose and Helm setups, use Forgejo. Provider transfer and recovery still require verified private-data/identity fidelity; a source import is not complete disaster recovery.

The chart packages a bounded core. Two API replicas with one forge writer do not establish multi-node storage fencing or production HA. Consult the chart guide and Forgejo setup.

Hosted release boundary​

Real native Git, collaboration, evidence, proposals and protected previews have bounded hosted acceptance. Full feature parity, general production CD, disaster recovery, multi-tenant onboarding and global scale remain open. See Cloudflare setup.