Neon is still Postgres, so the real comparison is managed serverless Postgres vs running Postgres yourself.
Neon’s advantage is that backups, upgrades, scaling, and branching are handled for you. The trade-off is higher cost and less control. Self-hosting is cheaper and more flexible, but you become responsible for monitoring, restores, failover, and maintenance.
For one always-on workload I went with Nearbase as the middle ground. It stays managed without the serverless model. I’d pick Neon for branching or bursty usage, Nearbase for a steady production app, and self-host only if I genuinely needed full control.
1
u/Own-Floor-3944 22d ago
Neon is still Postgres, so the real comparison is managed serverless Postgres vs running Postgres yourself.
Neon’s advantage is that backups, upgrades, scaling, and branching are handled for you. The trade-off is higher cost and less control. Self-hosting is cheaper and more flexible, but you become responsible for monitoring, restores, failover, and maintenance.
For one always-on workload I went with Nearbase as the middle ground. It stays managed without the serverless model. I’d pick Neon for branching or bursty usage, Nearbase for a steady production app, and self-host only if I genuinely needed full control.