Nobody. There is no Forge server, company account or database.
- Refs, issues, PRs, reviews and access control are documents on Dash Platform, a network run by Dash masternodes. Each document is signed by its author's identity.
- Pack bytes (the git objects) are stored wherever the repository's owner puts them: their own S3-compatible bucket, an IPFS node, or Platform itself.
- The web app is a static site. It is served from GitHub Pages at forge.dashhq.org, and anyone can build it and serve it elsewhere.
- The CLI (
dg,git-remote-dash) talks to Platform nodes and storage directly.
The Forge project publishes code and nothing else. Anything that looks hosted is either a static file or something you run yourself.
Not at the protocol level. The Forge contracts are registered without Platform's contract moderation, so nobody can delete your documents or ban your identity. That includes the Forge project, Dash Core Group, and the masternode operators. Ref history can't be deleted even by you, so nobody can rewind a branch.
What someone can do:
- Your storage provider can delete your bucket. Refs and history metadata survive on Platform, but the bytes in that bucket go. Protect against this with a second copy (
dg storage use r2-main,kubo), with Platform storage for packs that must outlive every bucket, and withdg reseed --from-local, which restores a lost copy from any clone. See Bring your own storage. - GitHub, a domain registrar or Cloudflare can take down forge.dashhq.org. The repositories are not there, so they are unaffected. See the next question.
- A government can block access to Platform nodes or gateways in a country. That is a network problem, not a takedown. The data is still there, and reachable from anywhere else.
Not at the protocol level. On mainnet, spam and abuse cost the sender real fees, which is the only floor; on a test network DASH is free, so fees are no floor there. Clients can still choose what to show: an issue's or PR's state counts only changes made by its author or by the repository's members, and anyone can build a client that filters more. No one can delete another person's documents.
The site dashhq hosts does this too: it can leave a repository or identity out of its lists, and show "Not shown on this site" in place of a hidden repository's pages and a hidden identity's repositories and profile details. The data stays on Platform, dash:// still works, and other builds still show it. Hosted curation says how an entry is requested and added.
Nothing is lost. Your repositories live on Platform and in your storage, not on the website.
git clone dash://…,git pushand everydgcommand keep working. They never touch the website.- The web app is a static build of
forge-web/. Build it and serve it from anywhere, including IPFS: see Run your own copy of the web app.
Mostly not. Every Platform read is checked against a proof, and every byte is checked against its hash. Two things are still trusted. First, the HTTPS endpoint that supplies the validator quorum keys proofs are checked against; the web app compares those keys with a second source (Platform nodes themselves) on every repository page and says Failed if they disagree. Second, the code doing the checking: the web app's checks protect you only if the JavaScript you loaded is the real app, so if you don't trust forge.dashhq.org (GitHub Pages), build the app yourself from source you have read and serve it, or use the CLI, which needs no website. Verify Forge explains the Verification card, and shows how to cross-check the keys against your own Dash node.
You, directly, and only for what you write. Platform fees come from your identity's credits. Storage bills come from your own provider, if you use one. Reading and cloning are free. Nobody sponsors identities. See Costs.
Measured on devnets (to be re-measured on testnet): creating a repository costs about 0.0027 DASH, which is 0.0016 for the repository and 0.0011 for the members-only key that new public repositories get by default. A push to your own bucket costs about 0.004–0.0055 DASH. An issue costs about 0.0006–0.001 DASH. Storing packs on Platform costs about 0.33 DASH per MiB. On devnet moutai, a fork of a small repository cost about 0.01 DASH, and a first GitHub mirror of a small repository about 0.08 DASH. On testnet all of it is paid in free test Dash. The full table is in Costs.
Retired; everything on it is gone. See the archived devnet move notes.
After Dash Platform v5 activates on mainnet and the project owner registers Forge's contracts there. Forge needs Platform v5 for its shared contracts, membership checks and limited keys. Until then:
| Network | Status |
|---|---|
| Testnet | Live since 2026-10-26. forge.dashhq.org runs here, and it is the CLI's default network, so no flag is needed. Its DASH is free test money and the network can be reset. |
| Mainnet | Not deployed yet. After Dash Platform v5 activates, the owner registers Forge's contracts (runbook). |
Forge has left the devnets it ran on before testnet. Networks has their history, and Dash Forge moved to testnet says how to push again.
An earlier version of Forge (forge-v1, one contract per repository) ran on testnet. It was removed on 2026-09-26 with no backwards compatibility, so its repositories cannot be read or migrated.
dg doctor shows which network you are on, its protocol version, and whether forge-v2 is deployed there.
Yes, on testnet: dg repo create --private (or dg init --private), and New → Repository → Private in the web app. Contents are encrypted in the client with a per-repository key that only members hold, and branch names, issues, PRs, comments and reviews are encrypted too. Anyone can still see that the repository exists, its name, its members, its size and when it changes. Forks and webhooks are refused on private repositories, because they would publish content unencrypted (E207). Releases are supported and sealed: a private repository's release notes and asset list are encrypted, and so is every asset file Forge seals, in the web app and in dg release create, unpublish and download. The one exception is an imported asset that could not be fetched and sealed: it stays an external link, whose URL is hidden but whose file is not encrypted, so anyone who can reach its source can read it. Label definitions are allowed but stay public. Removing a member rotates the key for future content, but cannot take back what they could already read. Collaborating lists exactly what is hidden and what is not; the design is in private-repos.md and forge-v2.md §5.
Forge is not a GitHub clone, and it does not need you to leave GitHub.
- The commands are familiar.
dgis shaped likegh, and git itself is unchanged:git clone dash://…,git push, branches, tags. jj push and fetch work too (tested in October 2026); see the quick start for the one setup step that differs. - You can mirror. Keep working on GitHub, and keep an unkillable mirror on Forge. The Mirror Action keeps code, issues, PRs, releases and labels in sync on every GitHub event.
- CI can listen.
dg webhook addand a relay you run deliver GitHub-shaped webhooks, so existing CI receivers work (Collaborating). - It is not at feature parity. No hosted CI (bring your own: forge-runner runs GitHub Actions workflows on your machine and reports checks with a runner key), and no wiki, discussions, organizations or global search. No
https://clone URLs (that would need a server); the web app offers a zip download instead. No shallow clones: usegit clone --filter=blob:noneinstead. The web app opens, reviews and merges PRs and forks repositories, but some merges still needdg: changes both sides made to the same files, a private repository, a merge too large to build in the browser, and a history that changes.gitmodulesor.gitattributesor holds an object git would reject. See Collaborating. Moving from GitHub or GitLab lists what has no equivalent, and the workarounds.
Each line says why: by design (the protocol or the no-server rule rules it out, and it will not change) or later (not built yet).
| Missing | Why | What to do instead |
|---|---|---|
| Wiki | later | A docs/ folder in the repository (the web app renders Markdown), or a second repository such as <repo>-wiki |
| Discussions | later | Issues with a discussion label |
| Projects and boards | later | Labels, milestones, and dg issue list --label … --assignee … |
| Gists | later | A small public repository |
| Teams | by design | Membership is never delegated: only the owner adds members. Use an organization identity or add each person to each repository |
| Transferring a repository | by design | The owner is fixed. Create a repository under the new owner and push to it; dg repo edit --moved-to marks the old one |
| Deleting a repository, issue or pull request | by design | They are permanent, and the contracts have no moderation. Archive the repository, close the issue or PR |
| Editing files in the browser | later | Edit in a clone and push |
| Browser merges for private repositories | later | dg pr merge (the browser merges public repositories) |
| Notifications beyond an open tab | by design | There is no hosted notification service. The web app's Notifications work while a tab is open. Anyone can run forge-notify for email or Web Push, and a webhook can feed your own notifier |
| Search across repositories beyond a name prefix | by design | Repository search finds name prefixes, topics and owners. Issues and pull requests are searched inside one repository, in the browser or with dg search issues and dg search prs; dg search repos finds repositories. Code search is in the browser only. A user-run index may come later |
| A fixed boundary for making a repository public, whatever happens | later | Making a private repository public keeps what members write from the run's own key change on members-only. If a key change lands in the moments right before the repository turns public, or the computer or browser that started the run loses its record, Forge falls back to the boundary the repository states, which can be later. Run the whole conversion from one device, don't change the repository's key while it runs, and check the result with dg repo make-public <owner>/<repo> --check |
| Git LFS objects | later | Not supported; keep large binaries out of git or attach them to releases, which go to your own storage. Large files through pointers to your bucket are on the roadmap |
Also not available, and by design: hosted CI (bring a runner), pushing over https://, shallow clones, and GitHub Pages. Read-only https:// clones of public repositories work through the optional gateway. Moving from GitHub or GitLab lists every GitHub feature with no equivalent.
Yes: register a DPNS username in the web app (Settings → Choose a username), with dg auth name register <label>, or in the Dash bridge. Then forge.dashhq.org/alice/project, @alice in the web header's jump box, git clone dash://alice/project and dg … alice/project all resolve it, with a proof-verified DPNS read. dg repo list --owner and granting access (dg collab add) still take the identity id.
No. Your repositories are on Platform and in your storage. Your identity survives as long as you have its 12 words or a backup of the identity file. A browser key on the lost laptop can spend at most its remaining budget, only on Forge, until it expires; revoke it from another device to stop it sooner. See Backup and recovery.
Then that identity is gone. Nobody can recover it, and nobody can sign as it again. Everything it published stays readable and clonable. Its repositories can no longer gain or lose members, because only the owner can change membership. Members it already added can keep pushing. To carry on under a new identity, create a new repository and push your clone to it. Keep the words safe.
Chrome and Edge 103 or newer, Firefox 104 or newer, and Safari 16 or newer (macOS and iOS). That floor comes from what the app needs to run at all: WebAssembly under a strict content policy (wasm-unsafe-eval), IndexedDB, WebCrypto, AbortSignal.timeout and Array.prototype.findLast. It is declared as the browserslist in forge-web/package.json, which the build compiles for.
Protecting the browser vault with a passkey also needs WebAuthn's PRF extension, which depends on the browser (Chrome and Edge 116, Safari 18, recent Firefox), the operating system and the passkey provider (iCloud Keychain and Google Password Manager support it; some third-party managers and security keys do not). Where it is missing, use a passphrase instead; everything else works the same.
Run dg ipfs up. It downloads kubo (checked against a hash built into dg), runs it for your user, starts it at login, saves a storage profile called kubo, and opens the web app's connect page. Then dg storage use kubo sends your pushes there. It costs no DASH. Your node stores the bytes on your own disk. The node accepts the web app only from the websites you allow, with a token that can add, pin and unpin and nothing else. Run your own IPFS node has the details, including port forwarding so others can reach it.
Pin it to your IPFS node: dg ipfs pin owner/name, or press Pin on the repository's page. Add --follow and your node pins new pushes too, every 30 minutes. It pins the files that the repository's owner, maintainers, writers and bots recorded, checks each against its hash, and costs 0 DASH, since nothing is written to Platform. Your node tells the IPFS network that it holds the files, so your IP address is linked to the repository. For a private repository you must be a member and agree to that first. --dry-run shows the size before you pin. See Pin someone else's repo.
Safari doesn't let a secure site (https://forge.dashhq.org) talk to a node on your own computer, and the web app can't work around that. The page tells you so. Use dg to push to your node, or connect from Chrome, Firefox or Brave: they ask you to allow the site to reach apps on your device. See Connect the web app.
GitHub Issues for now. Every error dg prints has a code; errors.md explains each one.