RRepoGEO

REPOGEO REPORT · LITE

garden-co/classic-jazz

Default branch main · commit c37b0030 · scanned 6/20/2026, 8:51:44 PM

GitHub: 2,537 stars · 113 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface garden-co/classic-jazz, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README's opening to clarify its database purpose and address the 'classic' name

    Why:

    CURRENT
    > [!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.**
    COPY-PASTE FIX
    # 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:

    COPY-PASTE FIX
    ## 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

    Why:

    CURRENT
    Homepage: classic.jazz.tools
- Docs: classic.jazz.tools/docs
    COPY-PASTE FIX
    - Homepage: [classic.jazz.tools](https://classic.jazz.tools)
- Docs: [classic.jazz.tools/docs](https://classic.jazz.tools/docs)

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface garden-co/classic-jazz
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
firebase/firebase-js-sdk
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. firebase/firebase-js-sdk · recommended 2×
  2. Redis · recommended 1×
  3. Socket.IO · recommended 1×
  4. Amazon ElastiCache for Redis · recommended 1×
  5. Azure Cache for Redis · recommended 1×
  • CATEGORY QUERY
    How to manage synchronized application state across frontend, backend, and cloud environments?
    you: not recommended
    AI recommended (in order):
    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 recommended 26 alternatives but never named garden-co/classic-jazz. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a database with offline-first capabilities and real-time synchronization for collaborative apps.
    you: not recommended
    AI recommended (in order):
    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 recommended 8 alternatives but never named garden-co/classic-jazz. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

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

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

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

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

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

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of garden-co/classic-jazz. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/garden-co/classic-jazz.svg)](https://repogeo.com/en/r/garden-co/classic-jazz)
HTML
<a href="https://repogeo.com/en/r/garden-co/classic-jazz"><img src="https://repogeo.com/badge/garden-co/classic-jazz.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

garden-co/classic-jazz — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite