Hosting & Infrastructure - Setup Guide

How to set up Neon

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Scale-to-zero means the first query after idle triggers a cold start (typically under 1 second on Launch and higher, longer on Free). This is fine for most apps but breaks the assumption of sub-10ms P99 latency for the first query of a session [source: neon.com/docs/introduction/scale-to-zero].
• Connection limits scale with compute size. Serverless environments (Vercel Functions, Lambda) can exhaust connections; use Neon's connection pooler (PgBouncer-based) or a serverless driver.
• Branching is not backup. If you drop a table on main, you lose it. Use point-in-time restore (paid tiers) for actual recovery.
• Databricks acquisition (2025) may change roadmap and pricing over the next 12-24 months; verify current plans if committing long-term.
• pgvector index build times can be slow on Free tier's small compute; upgrade for AI workloads.

The 7-step setup

1. 1

   Create your Neon account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Neon signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Neon pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Neon into the rest of your stack. The integrations that most people set up first: Vercel (native integration for preview branch per PR), Cloudflare Workers, AWS Lambda, Netlify Functions, Prisma, Drizzle, all standard Postgres drivers, Docker, Kubernetes, Terraform, GitHub Actions, Datadog, Grafana, pgvector (native), PostGIS, all standard Postgres extensions.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Neon deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Neon - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Neon for developers building SaaS on serverless stacks (Next.js on Vercel, Cloudflare Workers, Lambda) who want per-preview-branch databases and scale-to-zero cost efficiency. Recommend Supabase when the client also wants auth, storage, realtime bundled. Recommend PlanetScale for MySQL fans. Recommend AWS RDS or GCP Cloud SQL when the client needs enterprise-managed traditional Postgres.