# Neon makes Functions and Object Storage branch with Postgres Neon is extending database branching into a broader backend stack: Functions and S3-compatible Object Storage can now follow Postgres branches, giving preview and test environments isolated compute, data and files together. Neon’s beta backend now combines Postgres branches with Node.js Functions and S3-compatible Object Storage that inherit branch semantics. For builders, that makes ephemeral preview/test environments more complete: database state, backend code and object data can move together instead of requiring separate production-adjacent services. - Status: Active - Published: 2026-08-20T21:23:40+12:00 - Updated: 2026-08-20T21:23:40+12:00 - Categories: Cloud & Infrastructure, Cloud Platforms, Deployment & DevOps, Databases & Storage - Tags: Neon, Neon Functions, object storage, Postgres - Canonical HTML: https://beyondthe.news/dossiers/neon-functions-object-storage-branchable-backend-postgres ## What changed Neon launched Functions in beta on August 17, adding Node.js 24 backend compute that runs in the same region and branch context as a Neon Postgres database, with `DATABASE_URL` injected automatically and configuration available through `neon.ts`. Earlier in August, Neon detailed S3-compatible Object Storage whose buckets and objects participate in database-style branch workflows. These features build on Neon’s July backend beta, where Postgres, Better Auth, Object Storage, Functions and an AI Gateway were presented as one branch-aware application stack. ## Why it matters Database branching is useful for previews and tests only up to the point where the rest of the application still points at shared services. Neon is trying to extend the isolation boundary so a branch can include backend logic and object data as well as Postgres. That can reduce setup glue for preview deployments, safer agent-created environments and tests that would otherwise risk touching production buckets or shared backend services. The trade-off is deeper coupling to Neon while the products remain beta, with regional, durability, observability and future-pricing details still unsettled. ## Functions run beside the database branch Neon Functions are Node.js 24 functions exposed over HTTPS and run in the same region as the associated Postgres branch. Neon injects the branch-specific `DATABASE_URL`, which removes a common source of preview-environment configuration drift. The runtime is designed for more than short request handlers: Neon says it can support streaming, Server-Sent Events and WebSockets, including agent loops that stay active for longer interactions. ## Object Storage extends branch semantics to files Neon’s Object Storage is S3-compatible but tied to Neon’s branch model. When a child branch is created, object-storage state can follow the branch instead of forcing every environment to share one external bucket. That matters for tests and previews that need realistic file state: deleting, overwriting or generating objects in an ephemeral branch does not have to touch the production object set. ## Backend configuration is becoming declarative Neon’s `neon.ts` configuration is intended to define backend resources alongside code. Combined with branch-aware Postgres, Functions and Object Storage, this gives teams a path toward reproducible backend environments that can be created for pull requests, tests or agent tasks and removed afterward. The practical value is less bespoke provisioning logic between database, compute and storage services. ## The agent use case is unusually concrete Branchable backend state is particularly useful for coding agents because an agent can be given an isolated environment with realistic data and files, make changes, exercise backend code and then discard the branch. That reduces the temptation to give autonomous tooling broad access to shared development or production services. Builders still need to control external credentials and third-party APIs, which do not automatically become branch-isolated just because Neon resources do. ## Beta boundaries still matter Neon’s July beta initially limited the broader backend stack to us-east-2 and said Functions and Object Storage would be free during beta, with final pricing to come later. Neon also described short log retention during the beta and noted that Functions are not positioned as a general background-job runner. Teams should therefore treat the current stack as an architectural preview, not assume its present limits or economics are production contracts. ## Key details - Neon Functions entered beta on August 17, 2026. - Functions run Node.js 24 and are associated with the same Neon branch and region as Postgres. - Neon automatically provides a branch-specific `DATABASE_URL` to Functions. - The runtime supports HTTPS endpoints and Neon documents support for streaming, SSE and WebSockets. - Neon Object Storage is S3-compatible and participates in branch workflows with Postgres. - Neon’s broader backend beta combines Postgres, Better Auth, Object Storage, Functions and an AI Gateway. - The July beta initially targeted us-east-2; Functions and Object Storage were free during beta and final pricing had not been announced. - Neon says Functions are not intended to replace a dedicated background-job system. ## Builder takeaways - Use branch-aware storage and compute for previews/tests that currently need to share production-like buckets or backend services; isolation is most valuable where test writes are risky. - For coding agents, create disposable Neon branches with scoped external credentials rather than granting access to shared development or production resources. - Keep third-party services outside the Neon stack in your threat model: branch isolation does not automatically isolate Stripe, email, queues or other external APIs. - Treat `neon.ts` and branch provisioning as infrastructure code and exercise branch create/reset/delete flows in CI before depending on them for automated agent work. - Do not model long-term costs from beta pricing. Revisit unit economics when Neon publishes GA pricing for Functions and Object Storage. - Keep a separate queue/background-worker path for workloads that need durable asynchronous execution rather than stretching request-oriented Functions beyond their documented role. ## What to watch - GA timing, regional expansion and production SLAs for Neon Functions and Object Storage. - Final pricing and metering for function execution, object storage, egress and branch copies. - Whether Object Storage branch operations preserve performance and consistency at larger object counts and data volumes. - Whether Functions gain durable background-job or event-trigger primitives, or remain primarily request/streaming compute. - Improvements to logs, metrics and retention beyond the beta defaults. - How easily the branch-aware backend integrates with external preview-deployment systems and CI providers. ## Uncertainties - Functions and Object Storage are beta products, so limits, pricing and APIs may change before GA. - Neon’s performance and workflow claims are based on its own product material; BTN did not find independent large-scale benchmarks for branch-aware object storage or Functions. - The initial backend beta was region-limited and had short log retention; current availability should be rechecked before production adoption. - Branch semantics simplify Neon-owned resources but do not provide automatic isolation for external SaaS dependencies or credentials. ## Sources - [Neon Functions: backend logic next to your data](https://neon.com/blog/neon-functions-backend-logic-next-to-your-data) — Neon · official_announcement · 2026-08-17T00:00:00+12:00. Primary source for the Functions beta, Node.js 24 runtime, branch/region coupling, injected database URL, streaming support and intended use cases. - [Building Neon Object Storage](https://neon.com/blog/building-neon-object-storage) — Neon · official_announcement · 2026-08-06T00:00:00+12:00. Primary source for S3 compatibility and branch-aware object-storage design. - [Test out Neon backend: Object Storage, Functions, AI Gateway are beta](https://neon.com/blog/neon-backend-is-beta) — Neon · official_announcement · 2026-07-15T00:00:00+12:00. Primary source for the broader backend beta, initial region, beta pricing posture, log retention and integrated stack.