The standard

An open standard for household computing.

Like IMAP for mail or XMPP for chat — but for your home. Build on it freely.

Quickring is a protocol first and a product second. The wire contract — not any one SDK — is the portability boundary, so anyone can build a conformant Quickring home or app in any language.

What's published

  • The protocol. Session lifecycle, pub/sub, pairing, presence, and the feed convention, carried on the messagekit envelope. Protobuf over WebSocket, with a JSON profile for platforms without protobuf.
  • Federation. How two homes discover each other, cross identity and capability grants, and stay private between consenting peers.
  • The namespace. A Plan 9–inspired model — resources as files, namespaces per person composing into households and families. 9p in spirit, not on the wire.
  • Conformance. A test suite and versioning policy so independent implementations can verify themselves.

Start here

Protocol docs

The Current fabric protocol, in depth.

Read protocol.md →

Proto definitions

The quickring.v1 wire schema.

Browse proto/ →

Fabric Kit

The Quickring SDK — Rust core with Dart, Swift/Kotlin, and C bindings.

Fabric Kit on GitHub →

Governance

Apache-2.0 source, CC-BY-4.0 specs. Open protocol; reserved brand.

Our principles →

Draft site — spec pages and the conformance suite are being published as the standard work lands.