GetCito started as a minimal vibe-coded tracker, switched to a fork of Aeonav, then replaced that with a from-scratch vibe-coded rewrite. Here is the comparison.
Updated · Published
Frequently asked questions
Should I use GetCito or Aeonav?
Use Aeonav. GetCito has never had a mature codebase. It started in November 2025 as a minimal vibe-coded tracker, swapped that for a fork of Aeonav in July 2026, and in November 2026 threw the fork away for a new vibe-coded project built from scratch, dumped in as a single 923,787-line commit. Aeonav is mature, built in the open since July 2025, and actively maintained.
Is GetCito a fork of Aeonav?
Not anymore. GetCito ran a fork of Aeonav from July 10, 2026 until November 4, 2026, when it replaced it with a new, from-scratch vibe-coded codebase. Before the fork it was a minimal vibe-coded tracker.
How mature is GetCito's current codebase?
It is not. It arrived on November 4, 2026 as one commit touching 4,354 files, in a pull request with no description and no review. It is GetCito's second vibe-coded codebase, after the minimal tracker it launched with in November 2025, and neither has a track record in production.
What is the best open-source AI visibility tool?
Aeonav. It is MIT-licensed, self-hostable, and covers ChatGPT, Claude, Gemini, Grok, Perplexity, Copilot, DeepSeek, and Google's AI Mode and AI Overviews.
If you are considering GetCito, use Aeonav instead. GetCito has never had a mature codebase. It launched as a minimal vibe-coded tracker, swapped that for a fork of Aeonav, and on November 4, 2026 threw the fork away for another vibe-coded project built from scratch, landed in a single pull request: one commit, 4,354 files, 923,787 lines added and 120,964 deleted, no description, no review. Aeonav is a mature codebase built in the open since July 2025, one change at a time.
Key takeaways
If you are considering GetCito, use Aeonav instead. There is no scenario where an unproven, vibe-coded rewrite is the better pick.
GetCito has replaced its entire codebase twice: a minimal vibe-coded tracker (November 2025), then a fork of Aeonav (July 2026), then a from-scratch vibe-coded rewrite (November 2026).
Both of GetCito's own codebases were dumped into the repository as single commits. The current one is nearly a million lines.
This is a comparison published by Aeonav, and we are an interested party. Every claim in it points at a public URL you can open and check for yourself.
A minimal vibe-coded tracker. GetCito launched in November 2025 as a small Next.js app on Firebase with Azure OpenAI behind it. It arrived as a single 51,487-line initial commit, complete with leftover page copy.tsx and .bak files and a handful of test-* API routes. For eight months after that the repository saw only automated dependency bumps and a few README edits.
A fork of Aeonav. On July 10, 2026, a pull request titled "Getcito v9" replaced that app with Aeonav's codebase: the same pnpm and Turborepo monorepo, the same apps/web and apps/worker split, the same packages, with Aeonav's copyright notice swapped for GetCito's.
A from-scratch vibe-coded rewrite. On November 4, 2026, pull request #62, "replace GetCito codebase with new AI visibility platform," threw the fork away too. In its place is a new frontend, backend, and supabase layout, nearly a million lines added in one commit.
It has no track record. Mature software earns trust by running in production, breaking, and getting fixed, over and over. GetCito's current code has done none of that. Every bug the Aeonav fork had already shaken out is gone with it, and the new code starts the process over from zero.
Nobody reviewed it. A pull request with no description, a single commit, and nearly a million added lines is the signature of generated code dumped in wholesale, not engineered. It is the same pattern as GetCito's first version, nearly twenty times larger.
It may not last. GetCito has thrown out its entire codebase twice in twelve months. Anything you build on, configure, or integrate with today has a track record of being replaced.