Why Rinko Hub exists
Most version control platforms converged on the same interface a decade ago. We didn't start from an existing product's information architecture and bolt a new backend underneath it — we started from the protocol.
The protocol first
Nexa began as a distributed, content-addressed, cryptographically sealable version control protocol — not a hosting product looking for a backend. Objects are immutable and content-addressed. History is append-only. Confidentiality is enforced by encryption, not by a permissions table that a misconfigured server could bypass.
Rinko Hub is the platform built on top of it — made to keep its actual capabilities, competing candidates, tree-level merges, sealed labels, legible and fast to use, rather than papering over them with borrowed terminology.
What we optimize for
Speed, clarity, and low click counts. Every workflow is designed to be reachable by mouse, keyboard, or the integrated terminal — and to expose enough real semantic structure that a future AI agent can operate the interface the same way a person does, without screen-scraping.
Durability by default
We've all lost work to a service that went down at the worst moment. Every layer of Rinko Hub's backend — identity, data, and sync — is architected to run on more than one independent service from day one, not bolted on after an outage taught us a lesson the hard way.
Team
Rinko Hub is built by a small team at Nexaji who spent too many years fighting force-pushed branches and permission tables that didn't match how confidential code actually needs to be shared.