No host required
Keep the Git workflow and remove the part that was never essential: the host.
Git, stripped back to first principles
Git, stripped back to first principles.
gnostr-cloud takes the ordinary Git workflow and removes the part that was never essential: the host. The repo lives in the hash, the owner lives in the key, the transport lives among willing peers.
Why it matters:
GitHub-style convenience solved one problem while quietly reintroducing another: the central host became the place where collaboration,
visibility, policy, and access all bottlenecked.
Owner lives in the key
Identity and control come from keys, not a centralized account system.
Transport among peers
Sync moves across willing peers instead of through a permanent bottleneck.
No mandatory host
A hosted forge can be useful, but it should not be the thing the workflow depends on to exist.
Key-based ownership
Identity is carried by keys and signatures instead of platform accounts and organizational lock-in.
Peer-native transport
Repositories move across willing peers, so replication and coordination do not collapse into one provider.
Open by construction
The collaboration surface should remain compatible with free and open-source practice, not fenced behind rent or policy shifts.
Why this exists
Host-based Git platforms solved convenience, then reintroduced centralization.
Git did not require a permanent host to make sense. Over time, mainstream platforms turned collaboration into an account-bound, policy-bound, privacy-leaking bottleneck. Gnostr Cloud brings decentralization back to the process without abandoning the ordinary Git workflow people already know.
Decentralized by design
Adds decentralization back to a workflow that host-based platforms turned into a bottleneck.
Private by default
Reduces dependence on centralized infrastructure with its surveillance, policy, and access concerns.
Free and open
Keeps the workflow closer to first principles instead of renting permission to collaborate.
Still Git
Ordinary repos, hashes, commits, and workflows remain intact under a peer-native transport layer.
How it works in plain terms
Ordinary Git workflow. First-principles transport.
The point is not to replace Git with a platform. The point is to remove the hosted choke point: keep the repo in the hash, keep the owner in the key, and let transport happen across willing peers.
01
The repo lives in the hash
Content addressability stays at the center. The repository is anchored by its own history, not by a hosting provider.
02
The owner lives in the key
Control and authorship come from cryptographic identity instead of platform accounts and centralized trust.
03
The transport lives among peers
Replication and coordination move through willing peers, restoring decentralization to the actual workflow.
Minimal architecture
Identity
npub and nsec define ownership and signing authority.
→
Peer transport
Peers discover, answer, sync, and relay without a mandatory host.
→
Verified content
Hashes, Merkle structure, and signatures verify what arrives.
Protocol feel
Less dashboard. More toolchain.
CLI-native
terminal
$ cargo install gnostr-cloud-cli
$ gnostr-cloud-cli install --service
$ gnostr-cloud-cli identity store you@domain --nsec ...
$ git clone gnostr-cloud://npub1.../repo
identity resolves first, peers answer second, content verifies last
install
Install the CLI, optionally as a service daemon, and turn a local machine into a participant instead of a hosted account.
identity
Store a Nostr-native identity so the account lives in the key, not in a centralized username and password system.
clone
Use a native gnostr-cloud:// remote where identity resolves first and peer transport answers second.
verify
Content verifies as it arrives, so authenticity and integrity do not depend on trusting the relay surface.
Production top 20
The product should read like a protocol, not a hosted workspace.
These are the concrete features that make the thesis real: Nostr-native identity, peer transport, verifiable content, Git compatibility, threshold signing, open discovery, and install paths that stay aligned with the network instead of routing everything back through a central host.
Identity
Transport
Storage
Git
Ecosystem
Identity
Nostr-native identity
BIP-340 keys are your account: no signup flow, no password reset loop, no hosted identity silo.
FROST threshold signing
Group control can look like a single signer on the outside while remaining distributed in practice.
ROAST plus async FROST
Threshold ceremonies can accommodate offline or intermittent cosigners instead of assuming everyone is online together.
Server delegations
Group identities can delegate day-to-day operations to a server key without giving up first-principles ownership.
Transport
iroh QUIC transport
Direct, hole-punched peer connectivity with authenticated peer transport instead of a fake decentralization story.
Open peer tracker and gossip
Discovery can be reputation-ranked and gossip-driven with no lease-bound host acting as mandatory coordinator.
NIP-34 repo announcements
Repositories can announce themselves for discovery without depending on one provider-owned index page.
Public or private visibility
Flip read access policy when needed; private repos can disappear from gossip rather than lingering in a public hosted catalog.
Storage
Content-addressed storage
BLAKE3 Merkle trees stream and verify as they arrive, keeping integrity tied to content rather than platform trust.
Tri-hash compatibility
BLAKE3, SHA-256, and SHA-1 bridging helps gnostr-cloud interoperate across iroh, Blossom, and Git realities.
PostgreSQL index plane
A durable relational source of truth can back repos, refs, and hashes without redefining what the repository fundamentally is.
Signed release attestations
Source Merkle trees and signed manifests support more verifiable builds and sharper supply-chain trust.
Git
Git over gnostr-cloud://
Push and clone through a native remote helper so the workflow stays recognizably Git while the transport changes underneath.
First-push repo creation
A new push to a fresh URL can provision the repository automatically instead of requiring a hosted admin pre-step.
Git LFS daemon
A localhost proxy can turn repositories into LFS-backed stores with one setup path instead of a pile of hosted extras.
Server accept policies
Open, allowlist, delegated-only, or self-only gating gives operators clear control over who can participate.
Ecosystem
Blossom and GRASP bridge
Existing Blossom ecosystem pieces can interoperate instead of forcing a total greenfield migration.
Built-in Cargo registry
Publish, resolve, and install crates signed by your own key as part of the same network model.
QUIC binary install
Registry installs can fetch platform binaries peer-to-peer rather than leaning on a central package mirror.
Live Nostr activity feed
Pushes, creates, and admin actions can surface as live Nostr notes rather than disappearing into a hidden SaaS audit log.
What this restores
Open coordination, without the hosted bottleneck.
The visual system can stay mythic, but the product promise is concrete: less centralization, fewer privacy compromises, and a freer open-source workflow that does not depend on one company owning the collaboration surface.
The repo lives in the hash.
The owner lives in the key.
The transport lives among willing peers.
The workflow stays recognizably Git.
Deploy / participate
Run Git without the hosted choke point.
Deploy a peer, mirror important repositories, and move toward a workflow where coordination is distributed, identities are key-based, and the transport is not locked to a central service.
This page treats the art and logo as real brand assets, sharpens the decentralization thesis, and frames the product as a protocol-shaped Git coordination system rather than a hosted workspace.