Stringers
limelit-co/open · limelit-co

Half of the 400 stars were bought: Limelit Open, a GEO company, used an open-source library to do GEO

What it is A small program installed on your own computer that uses your own keys to periodically query ChatGPT, Claude, Perplexity, Gemini, Google AI Overview, and others, checking whether their answers mention your brand, what rank you get, and whose content they cite.

Why it blew up It wasn't organic community discovery: stars and forks jumped in two batches, and the accounts were almost all new accounts registered this year. Paid press releases went out and it was listed in various "open-source AEO tools" roundups, riding the hot GEO trend to turn the GitHub page into social proof for the cloud product.

DWhat you can do with it Don't build another general-purpose open-source AI visibility dashboard. If you do, go after the piece nobody has nailed: track Chinese AIs like Doubao, Kimi and DeepSeek, or ship it as a Claude Code skill / MCP that Claude Code can call directly, with the README written the same way.

D grade: the stars are mostly bought, and the people who follow can't copy a real organic star method. This slot already has seven or eight open-source repos and dozens of VC-funded commercial platforms. Canonry, which has the same positioning but no paid promotion, has barely gotten any stars. Few people know about this yet
Data (updated daily) · Repo created 2026-09-11 · 434 stars · 7 days +167
GitHub · stars
10020030040010-0910-1610-2411-0111-08434
Data 2026-10-09 → 2026-11-08 (31 days, 30 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Limelit Open is an open-source, self-hosted "AI visibility" tracker. You bring your own API keys, it asks ChatGPT, Claude, Perplexity, Gemini and Google AI Overview, and it counts whether your brand shows up in the answers, where it ranks, and who it cites. In 56 days the repo picked up about 400 stars, and over the last 7 days it added +155, so it looks like it's gaining traction. Broken down, roughly the first 190 stars and nearly all 172 forks came from the same batch of freshly registered empty accounts, backed by a paid press release and a ring of GEO sites linking to it. It's a traffic funnel for the commercial product limelit.co, not an open-source project that developers found on their own. This slot is already crowded too.

Sep 29: 108 stars and 109 forks in one day

In 2026, on Sep 11, an account called limelit-geo that had been registered the day before created the repo (later renamed limelit-co/open). By Sep 28 it had 44 stars and 43 forks. On Sep 29, the day it published macOS and Linux binaries on GitHub, it jumped to 152 stars and 152 forks in a single day (per the star history on githubrepo.cloud).

Stars and forks rose in lockstep, which almost never happens with a normal open-source repo, where forks are about a tenth of stars. Here the ratio is 45%. Look at the accounts that forked it:

  • The timing clusters: Sep 28 had 36, Sep 29 had 109, Oct 19 had 25, and they bunch up in the same hour (for example, 25 of them in the 12 noon hour on Oct 19), matching the day's star jump of +26.
  • The names look mass-generated: LanaCarson, FelixAndrade, Heather1Murphy, Tina1Johnson, Joyce11Keeling, and so on.
  • Of the 172 fork accounts I could still look up, 167 were registered between 2026 and 6 September, and only 1 have more than 5 followers. Of the 5 I spot-checked, all were registered on the same day in Aug 30, all have 0 followers, and most have a couple dozen other repos that are also forks.
  • Another 14 accounts have already been banned or deleted by GitHub.

GitHub API, checked 11-06. This is the classic "stars plus forks sold as a package" botting service.

DatestarsforkWhat happened
09-1100Repo created
09-284443First batch
09-29152152Binaries published, +108 stars and +109 forks in one day
10-09186147Paid ABNewswire press release the day before (10-08)
10-20218172Another batch: +26 stars and +25 forks
10-30224171Only 6 new stars over ten days
10-31→11-06246→379171→172+10 to 28 stars a day, forks flat
11-06 daytime403173

GitHub stars and forks.

The stretch after Oct 31 is the only part I can't explain: about twenty stars a day, very evenly spread, with forks flat. It could be real traffic from the "open-source AEO tools" listicle pages, or they may have switched to a service that only buys stars and not forks. GitHub no longer publishes the list of users who starred a repo, so I can't check individually. The steady daily rate looks more like the second option (an inference, with moderate confidence).

What it actually is

It's a single Go binary with no Docker, no Node and no Postgres. On first launch it creates its own SQLite database and serves a dashboard at localhost:1515. You enter a set of questions users might ask an AI, and it periodically asks seven AIs: ChatGPT, Claude, Perplexity and Gemini through their official APIs with web search enabled, and Google AI Overview, AI Mode and Bing Copilot, which have no API, through scraping. It then calculates your visibility and share of voice against competitors, average ranking, and whose sites get cited.

This goes by four names in marketing circles: AEO, GEO, AIO and LLMO. The README spells out all four on the first screen.

The execution is serious. Every number is labeled with its sample size. Every AI answer can be opened in full, with the brand mentions highlighted. The demo site demo.limelit.co runs the repo's code as-is, and the banner shows the current commit. It ships an MCP server with 14 read-only tools and a Claude Code plugin marketplace, so /plugin marketplace add limelit-co/open installs it. The README also includes a comparison table against commercial platforms, a glossary and an FAQ. In Oct 4 a GEO content site published a long source-code audit, which confirms the code is readable.

The last command is the reason it exists: limelit upgrade --key <cloud key> moves all your local data to the paid limelit.co cloud version. Cloud plans start at $19.99 in prepaid credits (limelit.co/pricing).

Beyond stars, what else was promoted

  • Paid press release: In Oct 8 ABNewswire published "Agent-first platform Limelit releases Limelit Open…", which a string of news sites such as StreetInsider and FinancialContent republished. PRWeb also ran a piece on "automating GEO for AI agents with 211 tools." ABNewswire's homepage itself says "paid press release distribution, guaranteed pickup on 500+ high-authority news sites."
  • Listicles and directory pages: cloro.dev's "2026 best AEO tools" lists it among 7 open-source tools. It's on repocloud with one-click deploy, and automated directories such as openalternative and ossradar include it. From the outside, there's no way to tell which of these were paid.
  • Discord, 44-second short videos, and a demo site.
  • No community buzz: Hacker News has no results, nobody has mentioned it on X in the last 60 days, and Reddit search comes up empty too.

The purpose is easy to guess. A GEO company sells the promise of getting AI to mention you in its answers. Press releases, comparison tables, listicle sites and a high-star GitHub page are exactly the kinds of pages AI search engines like to cite. They're doing GEO on themselves, and the open-source repo is the highest-weight page in that set.

How crowded this slot is

Crowded. The commercial players include Profound (publicly reported 2025 Series A and B totaling $55M), Peec AI (Series A of about €21M), Otterly, and Scrunch (from $250/month). Ahrefs and Semrush have also bundled similar features. There are at least seven or eight open-source "self-hosted trackers," and nearly all follow the same playbook: open-source core plus a cloud version.

ProjectStarsHow Limelit Open differs
elmohq/elmo5702025-08 build, cloud from $29/month, heavier stack
getcito449Calls itself the "first open-source AEO tool"
limelit-co/openAbout 400Single binary, 7 engines, MCP first; half the stars are bought
geo-aeo-tracker320Relies on Bright Data for scraping, which Bright Data's own blog has written about
oneglanse250
ansvisor231Leans toward "let agents run the optimization"
CanonryVery fewNearly identical positioning: agent-first, SQLite, bring your own key. Two Show HN posts scored 1 points each

GitHub stars, 11-06.

The last line says the most. Canonry and Limelit Open have almost the same idea and architecture. One has a few hundred stars and the other has almost none. The difference isn't the product, it's the promotion budget. The biggest player in this space is the SEO/GEO library packaged as "skills" (open-seo-mcp-skills, for example, has 8,800 stars). The "self-hosted tracker" slot is stuck at a few hundred stars for everyone.

If it were you

Verdict: D. These stars weren't discovered by developers. A company bought them and pushed them with press releases. The slot already has seven or eight open-source repos and dozens of VC-funded commercial platforms, and Canonry, with the same positioning but no paid promotion, has barely gotten any stars. Trying to build a reputation by making yet another open-source AI visibility tracker isn't worth it.

Who it suits: small teams already building GEO or SEO tools that have a paid product and want an open-source entry point to bring in customers, or people who want to learn how to write a README that works as a landing page.

Who it doesn't suit: solo developers hoping an open-source project will gain stars and reputation organically, and anyone without a promotion budget or an audience of their own.

How to do it (if you still want to build in this category): stop building a dashboard that tracks everything. (1) Take the piece it does poorly. It covers 11 data sources with only 6 of them done well, so build a small tool that only scrapes the three engines without APIs (AI Overview, AI Mode and Copilot), or do the same tracking for Chinese AIs (Doubao, Kimi, DeepSeek, Yuanbao). I haven't seen anyone own this in open source yet, though I haven't checked each one (inference). (2) Change the form: ship it as a Claude Code or Codex skill or MCP that the tools call directly, not a web dashboard. Skill-style repos nearby have more than ten times the stars of the trackers. (3) Copy its README practices: run the demo on unmodified code and label the commit, label every number with its sample size, keep the comparison table honest, and put all four synonyms on the first screen.

How to get users: in your Show HN and X launch posts, include a real side-by-side screenshot of how AI answers questions about your product versus competitors. Also publish the repo as a Claude Code plugin marketplace to use this new distribution channel. And write a data piece like "we tested a popular category and these 10 sites are what AI cites most" because that spreads further than product descriptions. Don't buy stars: stars and forks arriving in the same hour, accounts registered on the same day, and forks making up 40% of stars are easy for experienced people to spot, and the numbers drop once the accounts get banned.

How much time you have: for the Chinese AI slot, probably a few months, before GEO companies in China bring the same open-source playbook over. For a general English-language tracker, the window has already closed.

What would show you're wrong: (1) After November, Limelit Open keeps adding twenty to thirty stars a day for several weeks without new press releases, and people start discussing it on Hacker News and X unprompted, which would mean the product is pulling people in on its own. (2) Canonry or another unpromoted competitor naturally reaches a thousand stars within a few months, which would mean the slot isn't saturated. (3) Public data shows limelit.co's cloud version gained a meaningful number of paying users through the open-source repo, which would mean the "open-source core plus paid acquisition" route is worth copying for small teams.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
ProfoundWeb2024Publicly reported Series A of $20M and Series B of $35M (not verified for this review)Closed-source enterprise hosting with prompt-volume estimates; Limelit Open is free and self-hosted
Peec AIWeb2025Publicly reported Series A of about €21M (not verified for this review)Closed-source subscription hosting
Otterly.AI / Scrunch AIWeb2024-2025Scrunch from $250/monthClosed-source hosted
Ahrefs Brand Radar / Semrush AI ToolkitBig-company features2025Bundled into major SEO suitesHas existing SEO data, closed-source
elmohq/elmoOpen source2025-08570 stars, 150 forksAlso open-source with a cloud version ($29/month), but a heavier stack; Limelit is a single binary and covers AI Overview, AI Mode and Copilot
getcitoOpen source2025-11449 starsEarlier open-source AEO tool
danishashko/geo-aeo-trackerOpen source2026-02320 starsRelies on Bright Data for scraping; Limelit uses each vendor's API plus its own relay
CanonryOpen source2026-03Small (two Show HN posts, 1 points each)Nearly the same positioning (agent-first, SQLite, BYOK) but no stars, which shows the star gap comes from promotion, not the product
ansvisor / oneglanse / cloro geo-trackerOpen source2025-2026231 / 250 stars / unknownagentic execution, or just MCP/REST with no dashboard
Where users come from
  • Verified Star and fork farming: 09-29 gained +108 stars and +109 forks in one day; 10-19 12 at one point, 25 forks in one hour corresponded to +26 stars. The fork accounts were registered between 2026-06 and 09 167/172. A spot check of 5 accounts found 08-30 registered the same day, with 0 followers, FirstLast-style usernames, and 14 already suspended.
  • Verified paid press release: an ABNewswire 2026-10-08 release was syndicated by FinancialContent, StreetInsider, and others; a separate PRWeb release
  • Verified GEO content sites / listicles / auto-generated rankings: thegeocommunity 10-04 source audit, cloro.dev Best AEO Tools listicle, repocloud, ossradar, openalternative listings; whether they charge is unverified
  • Verified Claude Code plugin marketplace / MCP: repos from 10-05 can be added with /plugin marketplace add, 3 plugins, 14 MCP tools
  • Inferred HN / X / Reddit community spread: no entries in the hackernews database, 60 days and 0 posts on x-radar, and nothing found on Reddit.
  • Inferred steady 20+ stars per day after 10/31 (stars only, no forks): source unknown, since GitHub no longer exposes the stargazer list publicly. The daily rate is very even, so it could be a star-only farming service, or organic traffic from the listicle pages.

limelit-co/open (Limelit Open) research report

Data as of 2026-11-06. Sources: our github database (repo_day / repo_profile), the GitHub API (forks, user profiles, GraphQL), the githubrepo.cloud star-history CSV, ossradar.net, press releases (ABNewswire / PRWeb / StreetInsider), cloro.dev, thegeocommunity.com, the hackernews database, and x-radar.

One line

Limelit Open is the open-source core of limelit.co, a commercial GEO/AEO SaaS. It is a single Go binary with SQLite. Using your own API keys, it runs ChatGPT / Claude / Perplexity / Gemini / Google AI Overview / AI Mode / Bing Copilot, tracks brand mentions, rankings and cited sources, ships a built-in MCP server and a Claude Code plugin marketplace, and limelit upgrade moves you to the paid cloud in one command.

Verdict

It's not an open-source project that "ran up" organically. It's a SaaS company's marketing asset: the first 190+ stars and nearly all 172 forks are mass-produced by batches of fake accounts (stars and forks land in sync, in batches within the same hour; accounts 2026-06~09 newly registered, 0 followers, 14 already banned by GitHub). On top of that: paid press-release wire stories, GEO content sites run by the company and its rivals, and indexing of "open-source AEO tools list" articles. From 10/31 on it gains +20~28 stars a day with forks flat. We can't verify where that stretch comes from (GitHub no longer exposes the stargazer list publicly). It could be organic traffic, or they may have switched to a star-only service that doesn't touch forks. There's no discussion on HN or X at all. The recall scoring note said "fork/star ratio is high, verify for inflated traffic." Verdict: confirmed.

1. Data and curve

DatestarsforkNotes
2026-09-1100Repo created (originally under limelit-geo, registered 2026-09-10; former names limelitgeo/open)
09-23~09-26—7First batch of forks
09-284443githubrepo.cloud CSV, stars ≈ forks
09-29152152+108 stars and +109 forks in one day, stars and forks matched one-to-one
10-09186147Our database deeply sourced
10-19→10-20192→218147→172Another +26 stars and +25 forks; all forks landed in the 10-19 12 o'clock hour
10-30224171Plateau
10-31→11-06246→379171→172+10–28 stars a day, forks flat (gain_7d=155, prev_7d=6)
11-06 daytime403173Live GitHub API

Bot evidence (fork side, checked live via the GitHub API)

  • Creation times of the 187 forks: 09-28 fall in one window (36 forks), 09-29 in another (109 forks), 10-19 in another (25 forks), clustered in specific hours such as 09-28 10 o'clock and 10-19 12 o'clock.
  • The usernames look batch-generated: LanaCarson, FelixAndrade, BentleyBerg, AbagailAnderson, Heather1Murphy, Tina1Johnson, Joyce11Keeling, and so on.
  • Spot check of 5 09-28 fork accounts: all were registered on the same day, 2026-08-30, each has 22–28 public repos (mostly batch forks) and 0 followers.
  • Of the 172 fork accounts I could look up, 167 were registered between 2026-06 and 09, and only 1 have ≥5 followers. 14 more accounts can no longer be found (banned or deleted), such as Cael1Powell and Ryan1York.
  • Stars and forks jumped together on 09-29 and 10-20, which suggests a 'stars plus forks' bundle service. Forks/stars ≈ 45%, far above what comparable new repos show (in our database, the median fork ratio for new repos with ≥5000 stars is about 11%).
  • The stargazer details are unavailable: GitHub's stargazers endpoint now returns 404, and GraphQL returns an empty list. The same happens for other repos such as elmohq/elmo, so it is a platform change, not something specific to this repo. The source of the 'stars only, no forks' stretch after 10/31 therefore cannot be confirmed and is marked unverified.

II. Competitors

Commercial platforms (from the README's own comparison table)

ProductFormLaunchedScaleHow Limelit Open differs
Profound (tryprofound.com)Web SaaS2024Publicly reported: Series A 2025, 20M; Series B 35M USD (not verified this round)Enterprise-grade, closed source, expensive, with prompt-volume estimates
Peec AIWeb SaaS2025Public reports: 2025-11 Series A of about €21M (not verified for this report)Closed-source hosted, subscription pricing
Otterly.AI / Scrunch AIWeb SaaS2024–2025Scrunch starts at $250/month (per cloro.dev citing their pricing page)Closed-source hosted
Ahrefs Brand Radar / Semrush AI ToolkitBig-company features2025Bundled into established SEO suitesHas existing SEO data, closed-source
limelit.co's own cloud versionWeb SaaS2026Prepaid credits from $19.99 (limelit.co/pricing)This open-source repo is the funnel into it

Open-source peers (our github database, 2026-11-06)

LibrarystarsforkRepo createdNotes
elmohq/elmo5701502025-08Open-source AEO, cloud from $29/month; 2026-05 Show HN, 2 points
ai-search-guru/getcito449972025-11Self-described 'world's first open-source AIO/AEO/GEO tool'
danishashko/geo-aeo-tracker320752026-02Built on Bright Data scraping, which Bright Data's official blog has written about
oneglanse/oneglanse250442025-09
ansvisor/ansvisor2311082026-05agentic AEO
Canonry(AINYC/canonry)Not in the top 30—2026-03Same agent-first, SQLite, BYOK approach and the closest positioning; two Show HN posts on HN with 1 points each
cloro-dev/geo-tracker——2026MCP + REST, no dashboard
Others include genwolf-oss, Citatra, and the WorkSmartAI ai-visibility-monitorSmall2026

Next to it, the bigger projects are SEO/GEO 'skills' libraries (Ryze-AI-Adgent/open-seo-mcp-skills with 8861 stars, GEOFlow with 4028 stars). The category is hot, but in the 'self-hosted tracker' slot, most projects sit at a few hundred stars.

Conclusion: this slot is crowded, with at least 7 open-source trackers and dozens of commercial platforms, and most follow the same 'open-source core plus cloud' playbook. Limelit Open's star count is mid-to-upper among open-source peers, but that position was bought.

3. Growth tactics (evidence)

  1. Star and fork farming (confirmed): see above. 09-29 saw +108/+109,10-19 on one day, then another batch of +25/+26.
  2. Paid press release (confirmed): ABNewswire 2026-10-08, 'Agent-first platform Limelit releases Limelit Open…', reprinted by FinancialContent, StreetInsider, Saint Paul Chronicle and other wire sites; PRWeb ran another, 'Limelit gives AI agents 211 tools to automate GEO workflows'. The purpose of these wires is mainly to get AI engines and search engines to 'see' the brand, a GEO company doing GEO on itself.
  3. GEO content sites and listicle inclusions (verified): thegeocommunity.com ran a long-form source code audit 2026-10-04; cloro.dev's "Best AEO Tools 2026" lists it among 7 open-source tools; repocloud.io has it as a one-click deploy; auto-generated list pages on openalternative, ossradar.net, vibecrowd, githubrepo.cloud and others include it. pulseagent.io and the Instagram account "Entry 023" also repost it. Whether these sites are paid by or built by Limelit is unverified.
  4. Claude Code plugin marketplace / MCP ecosystem (existence confirmed, effect unknown): from 10-05, the repo itself is installable via /plugin marketplace add limelit-co/open and ships 3 plugins; the MCP server exposes 14 tools with the same names as the cloud version. This is a distribution play riding MCP and Claude Code plugin interest.
  5. Discord, demo site demo.limelit.co, and 44-second launch clips (existence confirmed).
  6. HN / X / Reddit: no limelit entries in the hackernews database; x-radar shows 0 posts in the last 60 days; Reddit search finds nothing. There is no evidence of organic community spread.
  7. The steady 20+ stars a day since 10/31: source unverified. It could come from the listicle pages above or ossradar's 'this week +154' ranking, or from another star-only service (no forks, very even daily volume, which looks more like the latter, but without stargazer details it cannot be settled).

4. Why it 'took off'

  • The numbers are fake: the first ~190 stars and ~170 forks came from the same batch of freshly registered fake accounts, meant to provide social proof for limelit.co's cloud version and to rank the GitHub page well for 'open source AI visibility tracker'-type searches and AI answers.
  • The category is genuinely hot: AEO/GEO funding was dense in 2025–2026 (Profound, Peec and others), marketers want cheaper alternatives, and 'free, self-hosted, BYOK' is a natural hook.
  • The product itself is serious: a single binary, SQLite, 7 engines (including AI Overview / AI Mode / Copilot scraping), sample sizes shown next to every number, answer-position highlighting, MCP first, and an honest README with a comparison table and FAQ. A third party (thegeocommunity) could write a source-level audit of it, which shows it is readable.
  • GEO firms doing GEO on themselves: press releases, comparison tables, listicles, llms.txt. The whole playbook is getting AI engines to cite you, and the GitHub repo is one of the high-weight pages.

5. Differentiation

Vs. commercial platforms: open source, self-hosted, auditable metric code, data in your own SQLite file, bring your own keys. Vs. open-source peers: a Go single binary with zero dependencies (most peers are Next.js + Postgres), coverage of AI Overview / AI Mode / Copilot without public APIs (via the Limelit cloud relay), MCP tool names that match the cloud version, and one command to migrate to the cloud. But these differences are not why it got its stars. Canonry's positioning is nearly identical (agent-first, SQLite, BYOK) and it didn't get stars. The gap in star counts comes from inflated numbers and PR placements, not from the community discovering the product.

6. How many people see it

It's circulating in a small circle, and it's self-promoted: only press-release sites, GEO content sites, and auto-generated GitHub leaderboard pages. No discussion on HN, X, or Reddit. Revenue is undisclosed (cloud pricing is public at limelit.co/pricing, and G2 has a product page). Nobody is copying it. It's just one latecomer among many "open-source core + cloud" players in this niche.

VII. What to take away

  • "Open-source core → one-command cloud migration" as a conversion funnel: limelit upgrade --key copies your data without sending provider keys, lowering migration anxiety.
  • The README works as a landing page: a demo site running the unmodified code with a banner showing the commit, an honest comparison table, a glossary (it claims all four terms AEO/GEO/AIO/LLMO for search), and an FAQ.
  • The repo doubles as a Claude Code plugin marketplace, riding a new distribution channel.
  • Lesson from the other side: bundled star+fork inflation is very easy to spot (same hour, same-day account creation, FirstLast usernames, fork/star ≈ 45%, batch-banned accounts). To people who know the space, it's a negative signal.

8. Not sure

  • Whether the 20+ stars per day from 10/31 onward were fake (GitHub no longer publishes stargazer lists, so this can't be verified).
  • Whether the inflation was bought officially or was a side effect of a third-party star service farming accounts (the latter is common for new repos, but 09-29 is the day it shipped its binary and 10-08 published the press release, so the timing looks more like an official launch push).
  • Whether thegeocommunity and the cloro listicles are paid placements.
  • Actual cloud users and revenue.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.