Work together
Open a public repository and create or review a signed issue, discussion, or pull request. Open the live repository.
Docs / Product promise
A reversible four-step proof
See the promise work.
ForkMesh lets developers collaborate on, mirror, and preserve source-code repositories across independent hosts—without relying on any single hosting provider.
Add an independent copy
Use the repository Mirrors tab to ask another node, or add a separate machine from Network. Wait for fresh signed health, matching refs, and integrity ok.
Stop the source safely
Stop forkmesh-mirror-node on the managed source host. The desktop remains online as a client and is not part of the serving path.
Use the same URL
Clone into a new directory and compare HEAD with the commit recorded before the source stopped.
git clone https://forkmesh.com/OWNER/REPOSITORYUse a disposable public repository. Confirm an independent mirror is eligible before stopping the source. A configured, stale, unhealthy, or integrity-mismatched host is not proof.
Failure and recovery are part of the proof
- With no eligible mirror, clone must report unavailable rather than claim success.
- Routing excludes a stale, unhealthy, or integrity-mismatched mirror.
- The public drill does not cover private repositories, which use authorized opaque replicas.
- To roll back, restart
forkmesh-mirror-nodeon the managed source host and wait for fresh signed health before retrying.
Current proof coverage
- Web collaboration and clone use a current browser and standard Git client.
- The desktop source-host control ships for macOS, Windows, and Linux.
- Managed independent server mirrors use the Linux headless service.
- Optional, consented telemetry records only coarse proof and clone actions—never repository names, URLs, commands, refs, or form values.
Maintainers, contributors, and operators use the measurement and comprehension protocol before release closure.