nself vs Vercel (Postgres)

Vercel is a frontend deployment platform that added Postgres (via Neon serverless Postgres), Redis (via Upstash), Blob storage, and KV store. nself is a self-hosted full-stack backend. These address different problems: Vercel optimizes for deploying Next.js frontends with adjacent data services. nself is the backend stack itself.

Feature matrix

See the [full comparison table](/compare) for a side-by-side view across nself, Supabase, Nhost, Firebase, and Appwrite.

Where Vercel is better

Best-in-class frontend deployment. Vercel's edge network, preview deployments, and CI/CD integration for Next.js (and other frameworks) are unmatched. If you are building a Next.js app, Vercel's deployment pipeline is faster and simpler than any self-hosted alternative. Source: [Vercel platform](https://vercel.com/docs).

Edge-native data. Vercel KV, Blob, and Postgres (via Neon) are designed to work at the edge with minimal latency from serverless functions. If your app uses Vercel Edge Functions, Vercel's data layer integrates without configuration. Source: [Vercel storage](https://vercel.com/docs/storage).

Zero ops for frontend teams. Deploy a Git repo, set environment variables, done. Vercel handles CDN, TLS, scaling, and DDoS protection. No Nginx, no Docker, no servers. Source: [Vercel deployment](https://vercel.com/docs/deployments/overview).

Preview environments per PR. Every pull request gets an isolated preview URL with its own edge network copy. Frontend teams get immediate visual review without spinning up backend infrastructure. Source: [Vercel preview deployments](https://vercel.com/docs/deployments/preview-deployments).

Where nself is better

Full PostgreSQL without connection limits. Vercel Postgres is serverless Postgres via Neon, which uses connection pooling with limits per plan (max 256 connections on Pro). nself runs standard Postgres with PgBouncer and no artificial connection ceilings. Source: [Vercel Postgres limits](https://vercel.com/docs/storage/vercel-postgres/limits), [nself Postgres](https://docs.nself.org/guides/postgres).

Not edge-only. Vercel's storage services are designed for serverless/edge runtimes, not traditional long-running server processes. nself runs full Postgres (no connection-per-request overhead), supports persistent connections, background jobs, and server-side rendering without edge constraints.

Plugin ecosystem. nself has 87 plugins for AI assistants (nClaw), media processing (nTV), real-time chat (nChat), billing (Stripe), monitoring (Grafana/Prometheus), and email (16 providers). Vercel has integrations but they add per-service cost and vendor dependency. Source: [nself plugins](https://docs.nself.org/plugins).

Predictable cost at scale. Vercel Pro costs $20/mo per seat, then compute time, bandwidth, and edge invocations add up. At 1M page views/mo with database calls, costs can reach $100-500/mo+. nself on a $20/mo VPS has no per-request charges. Source: [Vercel pricing](https://vercel.com/pricing), [nself pricing](https://nself.org/pricing).

Not a frontend-only platform. Vercel's Postgres, KV, and Blob are supplementary data services attached to a frontend platform. nself is a full backend stack (Postgres, GraphQL, Auth, Storage, Functions, Monitoring). If your app needs backend-heavy logic, nself is architecturally better suited.

Data sovereignty. Vercel stores your data in AWS regions they control. nself stores data on your server. Source: [Vercel privacy](https://vercel.com/legal/privacy-policy).

Side-by-side pricing

*Prices from Vercel's public pricing, verified April 2026.*

| Scale | nself | Vercel + Postgres |

|-------|-------|------------------|

| **Hobby / Dev** | $5/mo VPS | Free (with tight limits) |

| **Small app (10K MAU)** | $5/mo VPS | $20/mo Pro + storage costs |

| **Growth (100K MAU)** | $10-20/mo VPS | $50-200/mo (compute + bandwidth + DB) |

| **Scale (1M+ page views)** | $30-100/mo | $200-1,000+/mo |

Choose nself if...

1. You need a full backend stack, not just a database attached to a frontend platform

2. You want predictable flat monthly costs without per-request billing

3. Data ownership and sovereignty matter

4. You need GraphQL, Auth, and Storage fully integrated with your Postgres database

5. Your app is backend-heavy (background jobs, long-running processes, media processing)

Choose Vercel if...

1. You are building a Next.js app and want the best possible frontend deployment experience

2. Your backend is lightweight (mostly edge functions with simple database reads)

3. You want preview deployments per pull request with zero configuration

4. Your team does not want to manage servers at all

5. You are already on Vercel's platform and want co-located data services

Migration guide

Moving backend data from Vercel Postgres to nself. Vercel Postgres is standard Postgres under the hood (via Neon), so migration is straightforward.

### Step 1: Export from Vercel Postgres

# Get your Vercel Postgres connection string from the project dashboard
pg_dump \
  "postgres://USER:PASSWORD@HOST/DATABASE?sslmode=require" \
  --format custom \
  --no-owner \
  --no-acl \
  --file vercel_dump.pgdump

### Step 2: Install nself

curl -fsSL https://install.nself.org | sh
nself init my-project
cd my-project
nself start

### Step 3: Restore into nself Postgres

nself db restore vercel_dump.pgdump
nself db psql -c "\dt"

### Step 4: Migrate Vercel Blob storage

# Download blobs via Vercel Blob API
# Then upload to nself MinIO storage
nself storage upload ./downloaded-blobs/ /bucket-name/

### Step 5: Update your Next.js app

// Before (Vercel Postgres)
import { sql } from '@vercel/postgres'
const { rows } = await sql`SELECT * FROM posts WHERE id = ${id}`

// After (nself / Hasura GraphQL)
const { data } = await client.query({
  query: gql`
    query GetPost($id: uuid!) {
      posts_by_pk(id: $id) { id title content }
    }
  `,
  variables: { id },
})

FAQ

**Can I still deploy my frontend to Vercel while using nself for the backend?**

Yes. This is a common pattern. Deploy your Next.js app to Vercel, point API routes at your nself backend. Vercel handles frontend; nself handles data, auth, and storage.

**Does nself replace Vercel entirely?**

No. nself is a backend platform. It does not serve frontend assets at a global CDN, generate preview deployments, or optimize Next.js builds. Use them together or pick an alternative frontend host like Cloudflare Pages.

**Is Vercel Postgres real Postgres?**

Yes. It is Neon serverless Postgres, which is standard Postgres with a serverless connection model (connections are pooled and recycled per request). Your SQL works identically. The difference is connection behavior and pricing model.

**What about Vercel KV (Redis)?**

nself includes an optional Redis service (nself service enable redis). It is not serverless but it is co-located with your backend, has no per-request pricing, and works with any Redis client.

[Install nself](https://install.nself.org) | [View pricing](/pricing) | [See all comparisons](/compare)