{"id":"org_jijZZ_rvW3PaqosM0mKUu","slug":"neon","name":"Neon","domain":"neon.tech","description":null,"category":null,"tags":[],"sourceCount":4,"releaseCount":590,"releasesLast30Days":7,"avgReleasesPerWeek":3.2,"lastFetchedAt":"2026-04-19T07:01:42.933Z","trackingSince":"2023-03-01T00:00:00.000Z","aliases":[],"accounts":[{"platform":"github","handle":"neondatabase"}],"products":[],"sources":[{"id":"src__jPVFuSQu0-D5gs9BvJ-F","slug":"neon-blog","name":"Neon Blog","type":"feed","url":"https://neon.com/blog","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":201,"latestVersion":null,"latestDate":"2026-04-16T22:06:03.000Z","latestAddedAt":"2026-04-17T01:03:26.332Z","productSlug":null,"productName":null},{"id":"src_FAwdpN0Du_eN0EeGVkPwu","slug":"neon-changelog","name":"Neon Changelog","type":"feed","url":"https://neon.com/docs/changelog","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":203,"latestVersion":null,"latestDate":"2026-04-17T00:00:00.000Z","latestAddedAt":"2026-04-17T20:03:44.923Z","productSlug":null,"productName":null},{"id":"src_9Y9FN2gPqoq3TQTqqubQ5","slug":"neon-core","name":"Neon Core","type":"github","url":"https://github.com/neondatabase/neon","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":100,"latestVersion":"release-proxy-8853","latestDate":"2025-07-29T11:01:51.000Z","latestAddedAt":"2026-04-03T19:02:19.130Z","productSlug":null,"productName":null},{"id":"src_hEju3pSHmpQXFNJsBzgZT","slug":"neonctl","name":"neonctl","type":"github","url":"https://github.com/neondatabase/neonctl","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":86,"latestVersion":"v2.22.0","latestDate":"2026-03-16T18:48:06.000Z","latestAddedAt":"2026-04-03T19:02:21.104Z","productSlug":null,"productName":null}],"overview":{"scope":"org","content":"Neon has shifted focus to agentic provisioning and infrastructure-as-code patterns, while solidifying foundational features like authentication and multi-tenant database isolation.\n\n**AI agents now spin up isolated Postgres databases on-demand.** Neon integrated with Stripe Projects and Vercel's agent workflow tooling to let coding agents provision databases as part of app scaffolding. The `npx neonctl init` command now supports Claude, Cursor, v0, and other agents; Neon published an Agent Skill spec for teaching assistants Neon best practices; and a Cursor plugin launched for live org access. This reflects a hard pivot away from manual setup toward zero-touch infrastructure provisioning.\n\n**Zero-downtime patching lands through prewarming.** Neon shipped Part 1 of a zero-downtime patching system that prewarns database connections before maintenance, ensuring continuous availability in large-scale systems without unplanned failover events.\n\n**Organization and authentication got stricter and more collaborative.** Two-factor authentication rolled out across accounts. The Neon Auth SDK simplified with unified entry points for Next.js. Organization management expanded: unlimited free-plan members, domain-based member invitations, and a new Plugins tab in Auth org settings for managing third-party integrations. Neon Auth now webhooks to Resend and auto-configures trusted domains in Vercel preview deployments.\n\n**Data access and observability improved.** A consumption history API shipped for programmatic usage tracking on paid plans. The Data API Advisors tool surfaces optimization hints. The new Compute Autoscaling Report lets users review scaling behavior. Connect modal defaults to connection string for faster copy-paste workflows.\n\n**Postgres and extensions kept pace.** Minor versions bumped across the board (14.21, 15.16, 16.12, 17.8, 18.2). TimescaleDB support extended to Postgres 18. The MCP Server setup simplified, and the VS Code extension now auto-detects connection strings in your repo.","releaseCount":39,"lastContributingReleaseAt":"2026-04-10T00:00:00.000Z","generatedAt":"2026-04-16T15:16:30.048Z","updatedAt":"2026-04-16T15:16:30.048Z"},"knowledgePage":{"scope":"org","content":"Neon has shifted focus to agentic provisioning and infrastructure-as-code patterns, while solidifying foundational features like authentication and multi-tenant database isolation.\n\n**AI agents now spin up isolated Postgres databases on-demand.** Neon integrated with Stripe Projects and Vercel's agent workflow tooling to let coding agents provision databases as part of app scaffolding. The `npx neonctl init` command now supports Claude, Cursor, v0, and other agents; Neon published an Agent Skill spec for teaching assistants Neon best practices; and a Cursor plugin launched for live org access. This reflects a hard pivot away from manual setup toward zero-touch infrastructure provisioning.\n\n**Zero-downtime patching lands through prewarming.** Neon shipped Part 1 of a zero-downtime patching system that prewarns database connections before maintenance, ensuring continuous availability in large-scale systems without unplanned failover events.\n\n**Organization and authentication got stricter and more collaborative.** Two-factor authentication rolled out across accounts. The Neon Auth SDK simplified with unified entry points for Next.js. Organization management expanded: unlimited free-plan members, domain-based member invitations, and a new Plugins tab in Auth org settings for managing third-party integrations. Neon Auth now webhooks to Resend and auto-configures trusted domains in Vercel preview deployments.\n\n**Data access and observability improved.** A consumption history API shipped for programmatic usage tracking on paid plans. The Data API Advisors tool surfaces optimization hints. The new Compute Autoscaling Report lets users review scaling behavior. Connect modal defaults to connection string for faster copy-paste workflows.\n\n**Postgres and extensions kept pace.** Minor versions bumped across the board (14.21, 15.16, 16.12, 17.8, 18.2). TimescaleDB support extended to Postgres 18. The MCP Server setup simplified, and the VS Code extension now auto-detects connection strings in your repo.","releaseCount":39,"lastContributingReleaseAt":"2026-04-10T00:00:00.000Z","generatedAt":"2026-04-16T15:16:30.048Z","updatedAt":"2026-04-16T15:16:30.048Z"},"playbook":{"scope":"playbook","content":"# Neon — Playbook\n\n> Agent reference for fetching and maintaining **Neon** (`neon`) changelog sources.\n\n**4** active sources · domain: neon.tech\n\n## Sources\n\n| Name | ID | Type | URL | Last Fetched |\n|------|-----|------|-----|--------------|\n| Neon Changelog | `src_FAwdpN0Du_eN0EeGVkPwu` | feed | https://neon.com/docs/changelog | Apr 18 |\n| Neon Blog | `src__jPVFuSQu0-D5gs9BvJ-F` | feed | https://neon.com/blog | Apr 18 |\n| Neon Core | `src_9Y9FN2gPqoq3TQTqqubQ5` | github | https://github.com/neondatabase/neon | Apr 18 |\n| neonctl | `src_hEju3pSHmpQXFNJsBzgZT` | github | https://github.com/neondatabase/neonctl | Apr 18 |\n\n## Agent Notes\n\n### Extraction patterns\n\n- **neon-changelog** is the canonical release source. It uses a dedicated docs changelog page with an RSS feed at `neon.com/docs/changelog/rss.xml`. Entries are structured and release-focused — prefer this for tracking product updates.\n- **neon-blog** has an RSS feed at `neon.com/blog/rss.xml` but contains mixed content (engineering posts, company news, tutorials, product announcements). Will likely need `parseInstructions` to filter for product-relevant announcements only.\n- **neon-core** (neondatabase/neon) is a standard GitHub releases source for the core Postgres storage engine. Straightforward extraction via the GitHub API.\n- **neonctl** (neondatabase/neonctl) is a standard GitHub releases source for the CLI tool. Straightforward extraction via the GitHub API.\n\n### Known quirks\n\n- The blog source (neon-blog) is noisy — many posts are not product releases. Consider setting `parseInstructions` to focus on posts that announce new features, version releases, or platform changes, and skip purely editorial or tutorial content.\n- Both scrape sources have discovered RSS feeds, so they should be fetched via the feed adapter path rather than falling back to Cloudflare + AI scraping.\n- No products are defined for this org. All four sources sit directly under the Neon org. If the project grows (e.g., Neon Authorize, Neon Branches become distinct product lines), consider adding products to group sources.\n\n### Source coverage\n\n- **Platform changelog:** Covered by neon-changelog (canonical, structured).\n- **Blog announcements:** Covered by neon-blog (needs filtering for release-relevant content).\n- **Core database engine:** Covered by neon-core via GitHub releases.\n- **CLI tool:** Covered by neonctl via GitHub releases.\n- No gaps in coverage for the current source set. The four sources span the docs changelog, blog, core engine, and CLI — the main surfaces where Neon publishes release information.\n","updatedAt":"2026-04-18T20:42:35.842Z"}}