neondatabase/neon

Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 2nd, 2026
Created on March 26th, 2021
Open Issues & Pull Requests: 558 (+0)
GitHub issues: Enabled
Number of forks: 1,086
Total Stargazers: 23,050 (+0)
Total Subscribers: 121 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.6 hours
Mean response time: 64.7 days
90th percentile: 222.3 days
Tracked items: 1,702

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "a/test" is answered fastest, typically in about an hour, while "a/tech_debt" waits about 4 days. 53% of tracked open issues have had no activity in three months. Only 1% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 204
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 729 days
Stale 30+ days: 193
Stale 90+ days: 179

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • t/bug (942)
  • c/storage/pageserver (674)
  • c/compute (230)
  • migrated_to_jira (215)
  • triaged (200)
  • c/storage (161)
  • c/storage/safekeeper (152)
  • t/Epic (128)

Most active issues this week

Detailed Description

Neon is a serverless Postgres database platform that separates storage and compute to enable autoscaling, database branching, and scale-to-zero functionality.

Neon addresses the limitations of traditional monolithic PostgreSQL by decoupling storage from compute nodes. The architecture replaces PostgreSQL's built-in storage layer with a distributed system where stateless compute nodes are backed by the Neon storage engine. This engine consists of two components: a pageserver that provides scalable storage for compute nodes, and safekeepers that form a redundant write-ahead log service, receiving WAL from compute nodes and storing it durably until the pageserver processes and uploads it to cloud storage. This separation enables independent scaling of storage and compute resources.

Neon suits teams building applications that need elastic database scaling without managing infrastructure, particularly those with variable workloads that benefit from scale-to-zero capabilities. The platform supports standard PostgreSQL clients and tools, making it accessible to developers familiar with Postgres. It offers both a managed free tier and the ability to run locally for development and testing. Local installation requires Rust, protobuf compiler version 3.15 or higher, and platform-specific build dependencies; the project maintains detailed setup instructions for Linux and macOS environments.

The project maintains a pinned Rust toolchain version in a toolchain file that integrates with rustup for consistent builds across contributors and CI systems. Development activity shows regular attention to the codebase with structured documentation in developer guides covering the architecture and components. The project provides clear build instructions with platform-specific dependency lists and acknowledges compatibility considerations for different Rust versions and build environments.