garden-co/classic-jazz

• highreadme#1

  Reposition the README's opening to clarify its database purpose and address the 'classic' name

  原因：

  当前

  > [!IMPORTANT]
  > This is Classic Jazz - we recommend using Jazz v2 for new projects (repo, homepage, what's different)
  
  # Jazz - The database that syncs
  
  **Jazz is a new kind of distributed database that runs across your frontend, containers, serverless functions and its own cloud.**

  复制粘贴的修复

  复制

  # Classic Jazz: A Distributed Database for Modern Apps
  
  **Classic Jazz is a unique distributed database designed to sync data, files, and LLM streams instantly across your frontend, containers, serverless functions, and its own cloud storage.**
  
  It feels like reactive local JSON state and includes built-in auth, orgs, multiplayer, edit history, permissions, encryption, and offline support.
  
  *(Note: This is Classic Jazz. For new projects, we recommend Jazz v2.)*

  待办完成忽略
• mediumreadme#2

  Add a 'Why Classic Jazz?' comparison section to the README

  原因：

  复制粘贴的修复

  复制

  ## Why Classic Jazz?
  
  Unlike traditional databases (e.g., Redis, PostgreSQL) or even other real-time solutions (e.g., Firebase, PouchDB), Classic Jazz is built from the ground up as a *distributed database* that runs natively across your entire application stack—frontend, backend, and cloud. It offers true local-first capabilities with instant sync, built-in multiplayer, and end-to-end encryption, making it ideal for complex collaborative applications where other solutions require significant custom integration.

  待办完成忽略
• lowreadme#3

  Format homepage and docs links in the README as explicit hyperlinks

  原因：

  当前

  Homepage: classic.jazz.tools
  - Docs: classic.jazz.tools/docs

  复制粘贴的修复

  复制

  - Homepage: [classic.jazz.tools](https://classic.jazz.tools)
  - Docs: [classic.jazz.tools/docs](https://classic.jazz.tools/docs)

  待办完成忽略

本次扫描解析到的品类 GEO 通道：google/gemini-2.5-flash, deepseek/deepseek-v4-flash

• 品类问题

  How to manage synchronized application state across frontend, backend, and cloud environments?

  你：未被推荐
  AI 推荐顺序：

  1. Redis
  2. Socket.IO
  3. Amazon ElastiCache for Redis
  4. Azure Cache for Redis
  5. Google Cloud Memorystore for Redis
  6. Apache Kafka
  7. Confluent Kafka
  8. Amazon MSK
  9. Azure Event Hubs
  10. Google Cloud Pub/Sub
  11. GraphQL
  12. Hasura
  13. Apollo Server
  14. PostGraphile
  15. Apollo Client
  16. Relay
  17. WebSockets
  18. ws
  19. gorilla/websocket
  20. Spring WebFlux
  21. CRDTs
  22. Yjs
  23. Automerge
  24. Server-Sent Events
  25. Database Change Data Capture (CDC)
  26. Debezium

  AI 推荐了 26 个替代方案，却始终没点名 garden-co/classic-jazz。这就是要补上的差距。

  查看 AI 完整回答
• 品类问题

  Looking for a database with offline-first capabilities and real-time synchronization for collaborative apps.

  你：未被推荐
  AI 推荐顺序：

  1. Realm (mongodb/realm-js)
  2. PouchDB (pouchdb/pouchdb)
  3. CouchDB (apache/couchdb)
  4. Firebase Realtime Database (firebase/firebase-js-sdk)
  5. Cloud Firestore (firebase/firebase-js-sdk)
  6. WatermelonDB (nozbe/WatermelonDB)
  7. RxDB (pubkey/rxdb)
  8. Supabase (supabase/supabase)

  AI 推荐了 8 个替代方案，却始终没点名 garden-co/classic-jazz。这就是要补上的差距。

  查看 AI 完整回答

• Metadata completeness

  pass

• README presence

  pass

• Compared to common alternatives in this category, what is the core differentiator of garden-co/classic-jazz?

  pass
  ✓AI 明确点名了 garden-co/classic-jazz

  AI 的回答可能信誓旦旦却是错的。请按事实核对：技术栈、目标人群、差异化点是不是和你实际的对得上？

• If a team adopts garden-co/classic-jazz in production, what risks or prerequisites should they evaluate first?

  pass
  ✓AI 明确点名了 garden-co/classic-jazz

  AI 的回答可能信誓旦旦却是错的。请按事实核对：技术栈、目标人群、差异化点是不是和你实际的对得上？

• In one sentence, what problem does the repo garden-co/classic-jazz solve, and who is the primary audience?

  pass
  ✓AI 明确点名了 garden-co/classic-jazz

  AI 的回答可能信誓旦旦却是错的。请按事实核对：技术栈、目标人群、差异化点是不是和你实际的对得上？