Install yorkie with Homebrew

Project links

• Homepage
• Repository

Commands and aliases

• yorkie

Project history

The public Yorkie repository was created in October 2018 and presents the project as a Go server plus client SDK ecosystem for collaborative documents. The README describes the core architecture as Client, Document, and Server, with documents exchanged as changes and stored as snapshots/changes in the server-side store.

Yorkie evolved around the practical problems that appear once CRDTs move from papers into applications: offline editing, synchronization, conflict resolution, document watches, administration, and deployment. Its documentation now separates getting-started guides, SDK docs, CLI tooling, internals, and deployment material, which is a sign of a project aimed at application builders rather than only CRDT researchers.

Adoption history

Yorkie sits in the wave of collaboration infrastructure popularized by multiplayer editors, shared whiteboards, and local-first software. Its adoption story is smaller than Yjs or Automerge, but package managers matter here because a self-hostable server and CLI make CRDT collaboration something teams can run as infrastructure instead of embedding only a browser library.

The surrounding organization maintains related pieces such as a JavaScript SDK and dashboard, and the GitHub metadata in July 2026 showed active development with hundreds of stars and forks. That points to a modest but real community around self-hosted collaborative document infrastructure.

How it is used

Practically, Yorkie is used by developers who want to add shared state to an application: run or deploy the Yorkie server, connect clients through the Go, JavaScript, iOS, or Android SDKs, attach to documents, apply updates locally, and let Yorkie synchronize the CRDT changes.

The CLI is part of the package-manager story: it gives operators and developers a local command for interacting with Yorkie projects and documents while the server handles storage, synchronization, and conflict resolution.

Why package nerds care

Yorkie is interesting because it packages CRDT collaboration as server infrastructure, not just as an npm library. For package nerds, it represents the move from single-user command-line tools to installable collaboration backends that still fit normal open-source distribution channels.

Timeline

• 2018-10-24: The public yorkie-team/yorkie GitHub repository is created.
• 2020s: Yorkie develops around CRDT documents, SDKs, a CLI, server deployment, and administrative tooling.
• 2026-07: GitHub metadata shows continuing activity and a small but established community around the project.

Related projects

• Automerge and Yjs are adjacent CRDT/local-first collaboration libraries in the broader ecosystem.
• yorkie-js-sdk is the JavaScript client SDK for browser and Node applications.
• Yorkie Dashboard is the administrative companion for managing projects and documents.

Sources

• https://api.github.com/repos/yorkie-team/yorkie
• https://github.com/yorkie-team/dashboard
• https://github.com/yorkie-team/yorkie
• https://github.com/yorkie-team/yorkie-js-sdk
• https://yorkie.dev/docs
• https://yorkie.dev/docs/internals/crdt-concepts