Protect the code that matters from a single-host failure

ForkMesh mirrors your Git repositories across a live mesh of desktop nodes — so your history, issues, and pull requests stay portable and verifiable. They remain cloneable while at least one eligible, healthy copy is available. Mirror the projects you rely on, and help keep them online.

curl -fsSL https://forkmesh.com/install.sh | bash
Get Started
Install Now Read docs
ForkMesh / forkmesh.com › Repositories › node-f4rlozos/repository
Encrypted Chat
node-f4rlozos / repository Public Mirror
Fork 0 Mirror 1 Star 0
TSX App.tsx TSX RepositoryCard.tsx TS repositories.ts 
import { useMemo, useState } from "react";
import { RepositoryCard } from "@/components/repository-card";
import { repositories } from "@/data/repositories";
 
export default function App() {
  const [query, setQuery] = useState("");
 
  const visibleRepositories = useMemo(() => {
    return repositories.filter((repo) =>
      repo.name.toLowerCase().includes(query.toLowerCase()),
    );
  }, [query]);
 
  return (
    <main className="min-h-screen bg-neutral-950 text-white">
      <h1>ForkMesh Repositories</h1>
      <RepositoryCard repository={visibleRepositories[0]} />
    </main>
  );
}
Meet Our Customers ›

Open source should not depend on one company staying online forever

Your node

Local-first

Signed by default

Every issue, comment, and patch is a signed event. Verify authorship without trusting the node serving it.

Clone from the nearest mirror

Mainnodes route live clone and fetch requests to whichever healthy mirror is closest to you.

Encrypted repo rooms

Collaborate beside the code with authenticated shared-key rooms. The relay derives the default key and can read room plaintext; persisted history is capped at 500 frames for 7 days.

Trusted by your mesh, not a platform

Account lookup resolves an identity to its known nodes - no central directory holds the only copy.

node-f4rlozos F
N node1
node-msryAdT7 M

Pick any live node and start a room

ForkMesh resolves reachable desktop nodes across the network, so a repository can move from discovery to encrypted discussion without depending on one hosted platform.

View active nodes

Go beyond hosted Git

ForkMesh lets communities browse, clone, discuss, and accept collaboration records through a network where repositories remain portable Git mirrors instead of platform-owned database rows.

Live host

node-kaif / forkmesh ⌄

HOST STATUS

Online

MIRRORS

48

REQUESTS

Live repository browsing

Tree, blob, and clone requests route through the mainnode to an online desktop node. If no host is online, the mainnode does not pretend to own the missing Git data.

Learn more

SIGNED EVENTS

184

Issues126 Comments58

PATCH PRS

21

Open Merged

Collaboration you can verify

Issues and patch PRs arrive as signed submissions. Maintainers can review them, acknowledge owner inbox entries, and keep accepted history alongside the repository.

Learn more
FORKMESH - NETWORK PARTICIPATION

Preserve code.
Share community rewards.

Your desktop mirrors source code and serves clone data, keeping projects discoverable even when centralized platforms go down. Community members may voluntarily fund a transparent public reward pool for eligible, verified mirror nodes.

Reward network
Solana mainnet-beta public on-chain state
Pool
Public on-chain balance and history
Selection
Verified eligible mirrors transparent proof
Wallet
Self-custodial public address only
Fund states stay distinct
YOUUser-owned funds
→
POOLCommunity-funded
→
CHAINPending / finalized
01

You mirror code

Your node stores and serves Git repositories. Staying cloneable and discoverable makes it eligible for rewards.

02

You may be selected

Configurable randomized rounds can send a small community incentive to an eligible node’s self-custodial address. No payment or return is guaranteed.

Participation does not require a contribution
Join or fund the reward program →
Non-custodial: ForkMesh never stores community members’ wallet private keys or controls user funds·Community incentives are not investments

Support ForkMesh

Help us keep source code alive across machines people control.

ForkMesh started after Kaif had 65+ merged open-source contributions become hard to access when a long-running organization was flagged and became unavailable almost overnight.

Kaif and Jett started ForkMesh so source-code history, repo mirrors, and collaboration records do not have to depend on one fragile place.

Support ForkMesh on Patreon Browse Instance

ForkMesh FAQ

Answers about desktop nodes, mainnodes, local Git mirrors, signed collaboration, encrypted repo rooms, and how ForkMesh keeps source code portable.

What is ForkMesh?⌄

ForkMesh is local-first infrastructure for preserving and collaborating on source code. Desktop nodes keep real Git encrypted mirrors locally, while mainnodes coordinate discovery, direct-HTTPS clone routing, encrypted repo rooms, signed inboxes, and account lookup.

Is ForkMesh replacing GitHub or GitLab?⌄

No. ForkMesh works with Git instead of replacing it. The goal is to make repositories more portable and resilient, so important code can stay discoverable and cloneable even if one platform, account, or organization disappears.

Where is the Git data stored?⌄

Encrypted Git mirrors live on independently operated desktop nodes. Mainnodes coordinate the network, but they are not the canonical storage layer for Git objects. When someone clones a public repository through ForkMesh, the Worker proxies a healthy, integrity-verified HTTPS mirror under the original URL.

What is a desktop node?⌄

A desktop node is the local ForkMesh app that keeps encrypted repository mirrors on your machine. Its authenticated gateway can serve clone and browse data through ordinary HTTPS when healthy; multiplayer sockets carry no repository bytes.

What is a mainnode?⌄

A mainnode is a coordination node for the ForkMesh network. It handles catalog discovery, account lookup, healthy HTTPS mirror routing, encrypted repo rooms, signed inboxes, and routing without becoming the owner of everyone's source code.

How does collaboration work?⌄

ForkMesh uses portable collaboration records such as signed issue events and signed patch PRs. Instead of locking all project activity inside one service database, collaboration can move with the repository and be verified by clients.

Are repo rooms encrypted?⌄

Yes, as authenticated shared-key transport. Clients encrypt messages before relay, but the mainnode derives and distributes the default passphrase, so its operator can decrypt room content. At most 500 persisted frames per room are retained for 7 days.

Do I need to run a mainnode to use ForkMesh?⌄

No. Most users can start by running a desktop node and mirroring repositories they care about. Communities, teams, or operators can run mainnodes when they want to coordinate their own catalog, routes, rooms, and inboxes.

Who is ForkMesh for?⌄

ForkMesh is for maintainers, open-source communities, researchers, archivists, and teams that care about keeping source code available long term. If a repository matters, ForkMesh gives people a way to help preserve it.

Can ForkMesh preserve a repository if the original host goes offline?⌄

Yes, if the repository has already been mirrored by desktop nodes. ForkMesh is designed so Git history can remain available through local mirrors instead of depending on one hosted forge staying online.

Does ForkMesh store my repositories in the cloud?⌄

ForkMesh does not make the Worker or a mainnode the canonical Git storage layer. Git mirrors live on desktop nodes. Mainnodes coordinate discovery, routing, rooms, inboxes, and lookup.

How is ForkMesh different from a normal Git backup?⌄

A normal backup protects one copy. ForkMesh adds network discovery, direct-HTTPS clone routing, signed collaboration records, encrypted repo rooms, and mainnode coordination so preserved repositories can still be found and used by others.

Can open-source communities run their own ForkMesh network?⌄

Yes. Communities can run mainnodes for their own catalog, direct-HTTPS routing, encrypted rooms, inboxes, and account lookup while contributors run desktop nodes that keep encrypted repository mirrors locally.

Still have questions? Join the early ForkMesh community when it opens, or follow upcoming product updates on X.