Multi-platform orchestration
Dispatch only the configured target builds to matching macOS, Linux, Windows, or mobile-capable agents.
AI-assisted release orchestration
Release control for desktop and multi-platform software.
ReleaseForge coordinates local Go build agents, source-provider checkouts, human approvals, artifact verification, and AppPorter publishing from a Cloudflare control plane.
macOS DMG
Linux deb
Windows EXE
Android APK
Custom artifacts
Live release plan
v1.4.2 production
Build is running
System busy: coordinating macOS, Linux, and Windows agents.
Source locked
github / abc123
Build is running
system busy / local Go agent
Windows signing
needs approval
AppPorter upload
waiting on manifest
Required artifacts
3 / 3
Auto retries
2 max
Upload state
Held
What it does
One control loop for builds, approvals, artifacts, and publishing.
Provider-neutral source
Pull exact commits from GitHub, GitE2E, GitLab, Bitbucket, or any reachable Git remote before the build starts.
Local Go agents
Keep platform-specific build, signing, and packaging steps on the machines that have the right OS and credentials.
Human approval gates
Route risky decisions such as clean rebuilds, signing profile changes, partial uploads, and cancellations to the release owner.
GPT failure summaries
Summarize logs and suggest safe next actions while policy remains the authority for what can actually execute.
Verified AppPorter publishing
Create manifests with file size and SHA-256 checksums, then upload only verified artifacts to AppPorter.
Release flow
Designed for recoverable releases, not blind automation.
ReleaseForge starts deterministic, asks for help when state is ambiguous, and records the whole path in the audit log.
-
01
Create release
Submit repo URL, source provider, commit/ref, version, and target override from web, CLI, MCP, or desktop.
-
02
Dispatch required builds
The Cloudflare Worker writes state to D1 and queues only the platform jobs declared by `releaseforge.yaml`.
-
03
Classify failures
Agents stream logs. GPT produces concise summaries, failure classes, and proposed safe actions.
-
04
Verify and upload
ReleaseForge checks artifact manifests, uploads through AppPorter, verifies acceptance, and notifies through TopicBell.
Integrations
Built to sit between the tools you already use.
GitHub
Source checkout
GitE2E
Encrypted repos
TopicBell
Events and notifications
AuthrzMe
SSO and identity
AppPorter
Distribution upload
Cloudflare native
Control plane on Workers, state in D1, artifacts in R2.
Cloud control plane
Workers own API/MCP orchestration, policy checks, queue dispatch, and release state transitions.
- D1 stores releases, jobs, tasks, uploads, and audit events.
- R2 holds manifests, logs, artifacts, and upload receipts.
- Queues decouple release requests from local build execution.
Local execution plane
The Go agent runs on the OS that can produce the artifact, with build execution disabled unless explicitly enabled.
- Exposes local MCP tools for status, probes, checksum, build, and AppPorter upload.
- Checks out exact provider refs before deterministic build commands.
- Keeps signing and platform credentials close to the owning machine.
First release slice is live