Neon on X

The praise is specific. Realtime, which keeps a SQL query live inside Postgres, is called powerful and simple enough that an agent can use it; branches are named as a favourite feature, spun up for a migration and tossed after; the free tier and the free project count come up; one reports about $20 a month for three Laravel apps with the database on the free tier.

Dissatisfaction is about money and limits. A user writes that they keep getting charged $200 a month "for zero reason" with emails asking to cancel unanswered; another says bills "can spike unexpectedly" and would not recommend it; the 1GB free storage cap is named. One doubts Realtime's approach of putting workflow data in Postgres hot storage rather than S3, and one asks whether Neon holds the record for the longest downtime.

The switchers give pricing, constant new features and a friend's recommendation. The undecided had not heard of Neon, bookmarked it for a next project, or are waiting on reports from people using it.

The money complaints are concrete. One user reports $200 a month charged for an account they have asked repeatedly to cancel, with no reply; another says bills "can spike unexpectedly"; a third warns that expiring free credits lower today's bill while hiding what the same usage costs later. The 1GB free storage cap is named as a limit.

Breakage is small in numbers and varied: Realtime in beta enabled in the Neon dashboard but not showing true in Vercel, with no environment variable written; a Terraform provider whose latest version is older than the one already in use; pull-request previews failing because the Vercel integration writes the database URLs but not the AWS storage variables.

Migration friction is summed up as "the annoying part", and one person expects to redo a lot of code. On capability, a partner says Neon does not support Tokyo yet, and one team says it cannot build what it wants because Neon lacks the way to do it.

People weigh Neon against Supabase as a place to move to or from. Those moving to Neon cite its free project count, weekly pausing and a two-project ceiling on Supabase's side, and price: one says Neon is much cheaper if you run multiple projects, while another says cost is almost the same and points to scale-to-zero and startup credits. One presents Neon's per-customer database as a smaller blast radius if data is breached, calling that risk Supabase's.

PlanetScale is named instead of Neon, in one case for anything "real". Self-hosted Postgres on Hetzner or your own box is offered as the cheaper, more controllable route; the person weighing it says they are building solo and would rather not manage backups, upgrades and recovery.

Single voices name Cloudflare D1, Convex, and managed auth services, which one person finds all about equally fine. One migrated to Neon specifically for ElectricSQL.

The move questions are practical: is it really worth switching and how does the switch go, is there a strategy, skill or bot to migrate with, what would make switching easier — a skill, a CLI command or better docs — and how much friction there will be moving RLS policies and Auth, including those using auth.uid(). One asks simply whether Supabase to Neon can be done, and one asks what specific issues to know about first.

The comparison questions want a price comparison with Supabase, whether Neon is similar or completely different, and in what ways it is better. Cost questions cover object storage billed at the same rate or extra, egress limits, and how storage adds up across projects; one person reads the offer as "100 * 1 GB, 100GB of storage?" and one asks how to get the startup credits.

Smaller threads ask what Realtime is and how long it stays in beta, whether Neon Auth with TanStack Start is coming, who resolves a person and an agent editing the same record, and what the developer experience is like beyond the project count. One person asks how to run migrations when the staging branch is ahead of production.

Two people want a capability Neon does not have so they can build what they have in mind; one of them says they have put in a feature request, and the other says they would build it if Neon had the way.

The rest are single asks, each concrete. One admirer of branching wants database-level copy-on-write branches per tenant, without cloning the whole database each time. One wants a student discount or free premium access, and one asks why there is no X sign-in among the social auth methods.

Two requests are about the Vercel and agent side: write the AWS storage variables in the Vercel integration so pull-request previews stop failing on a missing environment variable, and build a demo where a person edits a record while an agent is working from its old value, showing the conflict and the agent rebasing its change. One asks what Neon could do to make loading data in easier.