epicenterhq/epicenter

Open-source, local-first apps.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 14th, 2026
Created on March 16th, 2023
Open Issues & Pull Requests: 208 (+0)
GitHub issues: Enabled
Number of forks: 381
Total Stargazers: 4,802 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.2 hours
Mean response time: 34.1 days
90th percentile: 104.5 days
Tracked items: 405

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "audio" is answered fastest, typically in about an hour, while "system" waits about 10 days. 79% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. 64% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 126
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 307 days
Stale 30+ days: 112
Stale 90+ days: 107

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (130)
  • feature request (112)
  • enhancement (39)
  • linux (23)
  • audio (21)
  • windows (18)
  • api provider (17)
  • backend (15)

Most active issues this week

Detailed Description

Epicenter is a framework for building local-first applications where data lives on your device as a single CRDT document that syncs across your own devices without a server holding the only copy.

The core problem Epicenter solves is synchronization in local-first apps. Rather than managing separate SQLite files on each device, it represents a database as one Yjs document that replays in full before any operation, making the surface synchronous. Reads are property accesses rather than round trips, eliminating the need for cache invalidation or race condition protection. Data definitions are pure JSON field descriptors declared per application with no migration burden. Rich content like text merges at the character level through pluggable codecs. Sync happens through one Cloudflare Durable Object per account and application, with device sign-in as the entire sharing model—no pairing, invitations, or approvals needed.

Epicenter suits developers building note-taking apps, task managers, or other document-centric applications where offline-first capability and multi-device sync matter. The project includes Honeycrisp, a notes app built on the framework, demonstrating the approach in practice. Adoption makes sense if you want to own your data storage and avoid server-side lock-in, and if your application's data model fits the document-oriented, CRDT-based approach rather than requiring complex relational queries.

The project shows active development with ongoing architectural decisions documented in architecture decision records. Work spans both the core data synchronization layer and example applications built atop it, indicating the maintainers are refining the framework through real usage rather than theory alone.