Why Rinko Hub exists
Rinko Hub is the hosted platform for Nexa, a version control protocol built as an alternative to Git. The platform's information architecture follows from what that protocol actually does, rather than starting from an existing product's interface and fitting a new backend underneath it.
The protocol first
Nexa is a distributed, content-addressed, cryptographically sealable version control protocol. Objects are immutable and content-addressed. History is append-only. Confidentiality is enforced by encryption at the protocol layer, which holds even if a server is misconfigured — there's no permissions table sitting between an attacker and the data.
Rinko Hub is the platform built on top of it, designed to keep the protocol's actual capabilities — competing candidates, tree-level merges, sealed labels — legible and fast to use in their own terms, with their own interface, rather than translated into borrowed terminology from other tools.
What we optimize for
Speed, clarity, and low click counts. Every workflow is reachable by mouse, keyboard, or the integrated terminal, and exposes enough real semantic structure that an AI agent will eventually be able to operate the interface the same way a person does, without screen-scraping.
Durability by default
Every layer of Rinko Hub's backend — identity, data, and sync — is architected to run on more than one independent service from day one. It's a decision made up front, based on what it actually takes for a single provider's outage to stay a degradation rather than a lockout.
Team
Rinko Hub is built by a small team at Nexaji with a shared background in distributed systems and version control, and a clear view of how confidential code actually needs to be shared across a team.
Follow Nexaji on X for release notes and what we're working on, or write to contact@nexaji.com.