Neon

Open coreDatabase

The backend for apps and agents, built to scale on Lakebase Postgres.

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: Free
usage-metered
Free tier: Yes
No card required.
Isolation: Virtual machine
hypervisor, or nothing at all
Regions: 8
US East (N. Virginia) · US East (Ohio) · US West (Oregon) · EU (Frankfurt) · EU (London) · Asia Pacific (Singapore) +2
Capabilities: 25 / 61
6 partial · 10 fail · 0 not assessed
Agent readiness: 10/11 · 11/11
read · drive, pre-login surface

Advertised for

Primary: OLTP Postgres, vector search, app/agent databases and branch per agent workflows. Backend services additionally include JS/TS Functions, S3 style Object Storage and prepaid AI Gateway.

Built for

Developers, then technical

· Hero tagline: 'The backend for apps and agents' — developer-facing product framing
· CLI-first setup: `npx neonctl@latest init`, `npm i -g neonctl`
· Deep technical docs: OpenAPI spec, SDK reference, architecture overview

01 Pricing usage-metered

Tier	EntryFree	Launch	TopScale
Price	$0/month	usage-based, no monthly minimum	usage-based, no monthly minimum
Transfer	5 GB	500 GB	500 GB
Storage	1 GB	—	—
Compute hours	100 h	—	—
Transfer overage	—	$0.1/GB	$0.1/GB
Storage overage	—	$0.35/GB	$0.35/GB
Compute hours overage	—	$0.106/h	$0.222/h

CU-hour (Compute Unit-hour = ~4 GB RAM + CPU × hours running); GB-month (storage + instant restore); egress GB·Card required: No·neon.com

Overages: Launch $0.106/CU-hour; Scale $0.222/CU-hour; Postgres $0.35/GB-month; restore $0.20/GB-month; snapshots $0.09/GB-month; Object Storage $0.023/GB-month; egress after 500 GB/project $0.10/GB; extra branches $1.50/branch-month.

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

Desktop landing and pricing use black surfaces, white sans-serif hierarchy and mint accents; the documentation switches to a white reading surface with structured navigation and pale-green instructional cards.

Corporate
Swiss-inspired

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Virtual machinehypervisor, or nothing at all

Persistence

durable-storage — WAL streamed to safekeepers (Paxos quorum), pages materialized to object storage; compute nodes are ephemeral/stateless

Snapshots / forks

Resources & limits

Storage

Postgres: Free 1 GB/project and 20 GB/account; paid $0.35/GB-month. Object Storage: Free 5 GB/project; paid $0.023/GB-month.

Limits & quotas

Free: 100 CU-hours/project, 1 GB Postgres/project and 20 GB/account, 5 GB egress/project, 10 branches/project, 100 projects. Launch $0.106/CU-hour; Scale $0.222/CU-hour; paid 500 GB egress/project. Functions/Object Storage/AI Gateway limited to four regions.

GPU

Access

Deploy interface

apicliconsole

SDK languages

TypeScriptPython

Network & secrets

Egress controls

IP Allow rules (Scale plan); PrivateLink / Private Networking (Scale plan); NAT gateway IPs documented for allowlist configuration

Secrets

DB roles and API keys; Functions receive DATABASE_URL automatically and support user-defined secrets/environment variables.

Bring your own cloud

Placement & use

Jurisdiction

AWS regions (US, EU, APAC, SA); Azure deprecated

Advertised workloads

Primary: OLTP Postgres, vector search, app/agent databases and branch-per-agent workflows. Backend services additionally include JS/TS Functions, S3-style Object Storage and prepaid AI Gateway.

04 Capabilities 25 pass · 6 partial · 10 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 4/4

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not applicable

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not applicable

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not applicable

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not applicable

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not applicable

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not applicable

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not applicable

Networking & delivery 3/6

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Not applicable

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not applicable

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Partially supported

Email send / receiveSend and/or receive email from the workload.

Not applicable

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 5/5

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not applicable

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not applicable

Git deployDeploy from a Git repo / push-to-deploy.

Not applicable

Private container registryHosted private image registry.

Not applicable

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not applicable

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Supported

AI & agents 4/8

Built-in coding agentShips a first-party AI coding agent in the product.

Not applicable

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not applicable

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not applicable

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not applicable

Data 4/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Supported

Platform & operations 2/5

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Partially supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not applicable

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Partially supported

Organisation & security 3/9

Built-in authPlatform-provided authentication / IAM for workloads.

Supported

SSO / SAMLEnterprise single sign-on.

Not supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Partially supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Partially supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

10/11

9 full · 1 partial · 91% of applicable checks

llms.txt
Supported
“https://neon.com/llms.txt — 41791 bytes; substantive current documentation index.”
llms-full.txt
Supported
“https://neon.com/llms-full.txt — 6688616 bytes; complete documentation retained as capped pointer with hash.”
robots.txt AI policy
Supported
“robots.txt has `Content-Signal: ai-train=yes, search=yes, ai-input=yes` — explicit AI allow signal. Allow: / with minor exclusions (/home$, /docs/auth/legacy/).”
JSON-LD
Not supported
“https://neon.com/ — 2 application/ld+json blocks observed.”
Sitemap
Supported
“robots.txt points to Sitemap: https://neon.com/sitemap.xml; sitemap-index references neon.com/sitemap-0.xml, blog-sitemap.xml, sitemap-postgres.xml. Non-trivial.”
Meta tags
Supported
“https://neon.com/ — descriptive title Neon — Postgres backends for apps and agents; complete description and OpenGraph tags observed in fresh HTML.”
Markdown negotiation
Supported
“https://neon.com/docs/introduction/architecture-overview — Accept: text/markdown returned HTTP 200 Content-Type: text/markdown; clean markdown. Also pricing.md and docs .md variants.”
Content efficiency
Partially supported
“https://neon.com/ — 429380 HTML bytes; 5985 readable text bytes excluding script/style/noscript (1.39%; 1–5% rubric band). June ratio incorrectly counted embedded scripts.”
Docs discoverable
Supported
“Docs link prominent in navigation. llms.txt confirms docs at neon.com/docs. Pricing page accessible at /pricing.”
Machine-readable pricing
Supported
“https://neon.com/pricing.md — structured Free/Launch/Scale table, current per-unit rates and allowances.”
No anti-bot wall
Supported
“All required public pages/docs fetched without challenge; rendered trust portal accessible. Obsolete quickstart 404 and authenticated MCP 401 are not bot barriers.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

11/11

11 full · 0 partial · 100% of applicable checks

Public API
Supported
“https://api-docs.neon.tech/reference/getting-started-with-neon-api — documented public REST API, 98 paths, interactive Try It.”
OpenAPI spec
Supported
“https://neon.com/api_spec/release/v2.json — fresh valid OpenAPI; 129 paths.”
MCP server
Supported
“https://mcp.neon.tech/mcp — hosted MCP endpoint. `npx add-mcp https://mcp.neon.tech/mcp`. Documented: Neon MCP Server overview at neon.com/docs/ai/neon-mcp-server.md. Supports OAuth + API key auth.”
SDK packages
Supported
“https://neon.com/docs/reference/sdk.md — TypeScript client and management SDKs; Python management SDK. @neon/sdk is current.”
Auth documented
Supported
“API key types documented (personal, org, project-scoped). Bearer token auth. OAuth for MCP. neonctl auth command documented.”
Self-serve credentials
Supported
“https://neon.com/docs/reference/claimable-neon.md — anonymous provisioning with scoped token flow; normal CLI login/API keys documented at https://neon.com/docs/cli/quickstart.md.”
Webhooks
Supported
“https://neon.com/docs/auth/guides/webhooks.md — Handle authentication events with custom server logic.”
CLI tool
Supported
“https://neon.com/docs/cli/quickstart.md — current Neon CLI (npx neon@latest); legacy neonctl reference retained only as historical-compatible surface.”
Error model
Supported
“https://neon.com/docs/reference/typescript-sdk.md — typed api/not_found/auth/rate_limit/timeout/network errors; https://neon.com/docs/reference/claimable-neon.md structured error code/origin/message/retryable/request_id.”
Rate limits documented
Supported
“Documented: 700 requests per minute (~11/sec), 40 req/sec burst per route, 10 req/sec for org API key creation. HTTP 429 documented with retry guidance.”
Agent config files
Supported
“https://neon.com/auth.md plus https://neon.com/docs/ai/agent-skills.md and documented MCP client setup provide multiple agent-specific configuration surfaces.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 13

Claude Code Anthropic
Supported
“Claude Code plugin for Neon — Includes Claude Code Skills for Neon, Neon MCP integration, and context rules. npx neonctl@latest init configures Claude Code.”
Source neon.com
Cursor Anysphere
Supported
“Cursor plugin for Neon — Install the Neon Cursor plugin to use Neon Skills and Neon MCP integration directly in Cursor.”
Source neon.com
Codex CLI OpenAI
Supported
“Codex is listed as a supported agent for add-mcp: `npx add-mcp --agent codex https://mcp.neon.tech/mcp`”
Source neon.com
Gemini CLI Google
Supported
“Gemini CLI listed as supported agent for add-mcp: `--agent gemini-cli` (alias: `gemini`).”
Source neon.com
GitHub Copilot GitHub
Supported
“Neon agents for GitHub Copilot — Custom agents for safe database migrations and query optimization in VS Code.”
Source neon.com
Cline Cline
Supported
“Cline (VS Code extension) and Cline CLI listed as supported agents for add-mcp.”
Source neon.com
Windsurf Codeium
Supported
“Manual configuration covers Windsurf: 'Connect MCP clients such as Cursor, Claude Code, VS Code, ChatGPT, and other tools including Windsurf.'”
Source neon.com
Zed Agent Zed
Supported
“Zed listed as supported agent for add-mcp: `--agent zed`.”
Source neon.com
OpenCode opencode
Supported
“OpenCode listed as supported agent for add-mcp: `--agent opencode`.”
Source neon.com
Antigravity Google
Supported
“Antigravity is listed in the Supported agents (add-mcp) table.”
Source neon.com
Goose Block
Supported
“Goose is listed in the Supported agents (add-mcp) table.”
Source neon.com
Kilo Code Kilo
Supported
“Kilo Code is listed in the Supported agents (add-mcp) table.”
Source neon.com
Kiro CLI Amazon Web Services
Supported
“Kiro CLI is listed in the Supported agents (add-mcp) table.”
Source neon.com

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 8

ISO/IEC 27001
certifiedhosted
“ISO 27001 is an internationally recognized standard for information security management systems (ISMS). Our compliance with this standard demonstrates that we follow a systematic and risk-based approach to managing sensitive information.”
Source neon.com
ISO/IEC 27701
certifiedhosted
“ISO 27701 extends ISO 27001 to include data privacy requirements, helping organizations establish, implement, and maintain a privacy information management system (PIMS) in accordance with GDPR and other privacy laws.”
Source neon.com
SOC 2 Type II
certifiedhosted
“We have successfully attained SOC 2 Type 1 and Type 2 compliance.”
Source neon.com
HIPAA
self-attestedhostedHIPAA is a regulatory framework, not a certification. Scale plan and BAA required; only hosted deployment covered.
“Neon offers HIPAA compliance as a self-serve feature available to customers on the Scale plan. Customers can accept a Business Associate Agreement (BAA) and enable PHI protection at the organization and project level.”
Source neon.com
SOC 2 Type I
certifiedhosted
“We have successfully attained SOC 2 Type 1 and Type 2 compliance. These compliances, validated by independent auditors, confirm that our systems adhere to the AICPA trust service criteria.”
Source neon.com
SOC 3
certifiedhosted
“The SOC 3 report is a public-facing version of the SOC 2 report, providing assurance to external parties about our system's ability to meet the trust service criteria without disclosing sensitive details.”
Source neon.com
CCPA
self-attestedhosted
“Neon is committed to complying with CCPA, ensuring transparency and control for users over their personal information.”
Source neon.com
GDPR
self-attestedhosted
“Neon adheres to GDPR requirements, ensuring the rights and data privacy of our users across the EU.”
Source neon.com

Regions 8

US East (N. Virginia)aws-us-east-1
US East (Ohio)aws-us-east-2
US West (Oregon)aws-us-west-2
EU (Frankfurt)aws-eu-central-1
EU (London)aws-eu-west-2
Asia Pacific (Singapore)aws-ap-southeast-1
Asia Pacific (Sydney)aws-ap-southeast-2
South America (São Paulo)aws-sa-east-1

Eight AWS project regions; each project is single-region and cannot be moved in place. Postgres/Auth in all eight; Functions/Object Storage/AI Gateway currently only us-east-1, us-east-2, eu-central-1, ap-southeast-1. Azure deprecated; inactive Free projects subject to deletion from 2026-10-05.

Legal

Privacy notice Terms of service

08 Open source Apache-2.0 · fetched by machine, not quoted from marketing

Licence & repository

Licence: Apache-2.0OSI
Primary language: Rust
Stars: 23,206
Forks: 1,114
Created: 26 Mar 2021
Archived: No

Activity

Last commit: 31 Aug 2026
Latest release: release-proxy-8853 · 29 Jul 2025
Issues open / closed: 312 / 2831 · 90% closed

Latest eight GitHub release objects are component release tags from July 2025. Do not confuse this historical release-object list with ongoing repository pushes or the hosted service changelog.

Fetched via gh on 15 Oct 2026.

Self-hosting

Methods: composesource-build
You operate: postgresobject-storage

Self-hosting the full Neon stack (pageserver + safekeeper + storage_broker + proxy + compute) is technically possible via docker-compose (docker-compose/docker-compose.yml in the repo, uses MinIO for object storage). The autoscaling / NeonVM component (neondatabase/autoscaling repo) requires Kubernetes + QEMU and is explicitly marked 'not officially supported externally'. The README says 'Neon can be run on a workstation for small experiments and to test code changes' — self-host is a dev/test path, not a production-grade self-host. No official self-host docs on neon.com. Self-host cost = free under Apache-2.0 + operator's own infra.

Documentation signals 7/8

SupportedQuickstart
SupportedAPI reference
Not supportedSelf-host guide
SupportedChangelog
SupportedOpenAPI
Supportedllms.txt
SupportedExamples
SupportedArchitecture doc

09 Company & presence Facts only, not scored

Company

Headquarters: Not disclosed
Founded: 2021
Team size: Not disclosed
Hiring: Hiring through Databricks

Activity

Last release: 2026-10-09 neon.com
Last blog post: 2026-10-07 neon.com

Presence 6

Links found on the public surface scanned; not an exhaustive search.

10 Sources & method How this entry was produced

Public surface only

Everything here was read from neon.com's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Database products →