---
title: GetCito vs Aeonav
description: 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.
canonical: https://www.aeonav.fivecoder.com/blog/getcito-vs-elmo
updated: "2026-11-04"
---

# GetCito vs Aeonav (/blog/getcito-vs-elmo)

**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](https://github.com/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/pull/62): one commit, 4,354 files, 923,787 lines added and 120,964 deleted, no description, no review. [Aeonav](https://aeonav.fivecoder.com/) 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.

## GetCito vs Aeonav at a glance [#getcito-vs-aeonav-at-a-glance]

| | GetCito | Aeonav |
|---|---|---|
| Current codebase since | November 4, 2026 | July 2025 |
| Codebases since November 2025 | 3 | 1 |
| How the current code landed | One unreviewed 923,787-line commit | 1,269 commits, built up incrementally |
| Stack | Next.js, Express, and Supabase | TanStack Start, pg-boss, and PostgreSQL |
| Maturity | Vibe-coded rewrite with no track record | In production since 2025 |
| Best for | Nothing we can identify — use Aeonav | Owning your AI visibility data long term |

Figures reflect the public GitHub repositories as of November 4, 2026.

## Three codebases in a year [#three-codebases-in-a-year]

**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"](https://github.com/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/pull/19) 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](https://github.com/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/pull/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.

## Why a vibe-coded rewrite is the worse tool [#why-a-vibe-coded-rewrite-is-the-worse-tool]

**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.

## Which should you choose? [#which-should-you-choose]

Use Aeonav. It is a mature, actively maintained codebase built by the people who run it, not a vibe-coded rewrite with no history.

For the wider field, see our roundup of the [best AI visibility tools](/blog/best-ai-visibility-tools) and the [best open-source AEO tools](/ai-visibility-tools/category/open-source) in our directory. To go deeper on the practice itself, start with our guide to [answer engine optimization](/answer-engine-optimization), then see [how to track your brand in AI search](/answer-engine-optimization).