OpusFlow, a Dutch ERP platform for solar energy installers, needed strict per-customer data isolation in Postgres but found Amazon RDS too costly and operationally burdensome. Running one RDS instance per tenant required dedicated DevOps and heavy overprovisioning. They switched to Neon's serverless Postgres, where each customer gets their own isolated Neon project. Compute scales automatically and goes idle when unused, cutting costs. Neon's database branching enables instant point-in-time restores, per-developer isolated environments, and mirrors their Git workflow. Their full stack is serverless: Next.js, Clerk, Hasura (GraphQL over Postgres), AWS Lambda, and Neon as the database layer.

5m read timeFrom neon.com
Post cover image
Table of contents
Multi-tenancy in Amazon RDS: a complex and costly designThe alternative: a fleet of Postgres in NeonThe OpusFlow serverless stackGive Neon a try