Pricing for Single Project with 1,000 Tenant Databases
Hi Neon Team,
I'm evaluating Neon for a multi-tenant SaaS application where we plan to use:
- 1 Neon project
- 1,000 separate databases (one per tenant)
- Each database requires minimal resources (~0.25 CU equivalent)
My understanding is that compute usage is shared across databases in a project. Could you clarify:
Compute Allocation:
If we set the project to 0.25 CU, is this shared across all databases?
Or can we configure separate compute limits per database?
This architecture is critical for our cost efficiency. Any guidance would be greatly appreciated!
1 Reply
rare-sapphire•6mo ago
There are three options to consider in your case:
1. Single project, single branch:
All tenant databases live under the same branch. You cannot set different compute limits per database — compute is shared across all databases in the project. This is the most cost-efficient setup, especially if each tenant requires minimal resources.
2. Single project, one branch per tenant:
This allows you to set different compute limits per branch, but it’s not an intended use case for branches. Branches are designed more for development workflows, not for isolating production tenants. Managing 1,000 branches would be complex and potentially unstable.
3. One project per tenant (1,000 projects):
Each project has its own database and compute, so you can configure different compute limits per tenant. However, this is only available starting from the Minimum Scale plan, and it’s the most expensive option.
My personal recommendation is Option 1, as it’s the simplest and most cost-effective. Option 2 is technically possible but not advisable due to how branches are designed. Option 3 offers full isolation and flexibility but comes at a higher cost and management overhead.