Source: https://seerepo.com/compare/FuelLabs/fuel-core/vs/neondatabase/neon
Markdown source: https://seerepo.com/compare/FuelLabs/fuel-core/vs/neondatabase/neon.md
Description: fuel-core and neon share 12 technologies: tower, axum, aws-sdk-s3, Redis, AWS S3, Tokio, ed25519-dalek, parquet, tracing, prometheus-client, tracing-subscriber, and tracing-appender. Both are written in Rust.

# fuel-core vs neon

fuel-core and neon share 12 technologies: tower, axum, aws-sdk-s3, Redis, AWS S3, Tokio, ed25519-dalek, parquet, tracing, prometheus-client, tracing-subscriber, and tracing-appender. Both are written in Rust.

- [FuelLabs/fuel-core](https://seerepo.com/r/FuelLabs/fuel-core): Rust full node implementation of the Fuel v2 protocol.
- [neondatabase/neon](https://seerepo.com/r/neondatabase/neon): Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.

## What they share and what sets them apart

- In common: tower, axum, aws-sdk-s3, Redis, AWS S3, Tokio, ed25519-dalek, parquet, tracing, prometheus-client, tracing-subscriber, tracing-appender
- Only in fuel-core: rocksdb, lru, quick_cache, wasmtime, crossterm, indicatif, termion, tracing-core
- Only in neon: asyncpg, pg8000, psycopg2-binary, Postgres, moka, clickhouse-connect, Sentry, werkzeug, AIOHTTP, jsonwebtoken, hmac, pyjwt, jinja2, opentelemetry-semantic-conventions, prometheus, env_logger, opentelemetry-otlp, tracing-opentelemetry, psutil, boto3, OpenTelemetry, log

## Side by side

| | fuel-core | neon |
|---|---|---|
| Size | 197,248 lines written, 566 code files | 379,885 lines written, 659 code files |
| Who writes it | 0.7% of its commits signed by AI. With Claude Code and Cursor | 0.1% of its commits signed by AI. With Devin |
| Activity | Last push November 5, 2026, 1,513 commits, 56,767 stars | Last push August 31, 2026, 8,459 commits, 23,296 stars |
| Tests | 166 test files. 33% of its code files have a test that imports them | 281 test files. 12.4% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, fuel-core or neon?

neon, with 379,885 lines written; fuel-core has 197,248.

The proof: [neondatabase/neon's code at commit fa50421](https://github.com/neondatabase/neon/tree/fa504217c61bbcaf5c512d75830564541f917f8f)

### Which has more GitHub stars, fuel-core or neon?

fuel-core, with 56,767 stars; neon has 23,296.

The proof: [FuelLabs/fuel-core on GitHub](https://github.com/FuelLabs/fuel-core)

### Which has more tests, fuel-core or neon?

neon, with 281 test files; fuel-core has 166.

The proof: [neondatabase/neon's code at commit fa50421](https://github.com/neondatabase/neon/tree/fa504217c61bbcaf5c512d75830564541f917f8f)

### Which was updated more recently, fuel-core or neon?

fuel-core: its last push was on November 5, 2026, and neon's on August 31, 2026.

The proof: [FuelLabs/fuel-core's commits on GitHub](https://github.com/FuelLabs/fuel-core/commits)

### Which has more commits signed by AI, fuel-core or neon?

fuel-core: an AI signed 0.7% of its commits, with Claude Code and Cursor; in neon, 0.1%.

## Sources

- FuelLabs/fuel-core: Read on November 5, 2026, at commit ffd6563 (https://github.com/FuelLabs/fuel-core/tree/ffd6563763582f8b0d9073a7cc115b57002ee684)
- neondatabase/neon: Read on November 4, 2026, at commit fa50421 (https://github.com/neondatabase/neon/tree/fa504217c61bbcaf5c512d75830564541f917f8f)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.