What problem does it solve?
When building applications with Neon Postgres, using a separate third-party object storage provider creates a disconnect between your database records and stored files across development, preview, and production branches, requiring extra work to keep them in sync and manage two separate systems.
Core Features & Use Cases
- S3-compatible API: Works with existing AWS SDKs, boto3, AWS CLI, and presigned URLs with no proprietary client required.
- Branch-synced storage: Every Neon branch gets its own isolated, copy-on-write storage state, so files and database rows stay perfectly in sync across all environments, with no data duplication when forking branches.
- Preview feature for Neon projects: Currently only available for new Neon projects in the us-east-2 region, with the same credential system used for Neon Functions and the AI Gateway.
- Ideal for file-heavy apps: Perfect for storing user uploads, images, documents, avatars, and generated assets when you already use Neon and want to avoid managing a separate storage provider.
Quick Start
Use the neon-object-storage skill to configure a branch-synced S3-compatible bucket for your Neon project and implement a working upload and presigned download flow for user-generated files.