Deploy Next.js on your own server with Postgres and HTTPS

Next.js can run anywhere Node runs, yet most guides pretend your only two options are paying per seat on a front-end cloud or spending a weekend configuring Nginx, Docker, Certbot and systemd on a raw Linux VPS.

There is a third option: run Next.js on a dedicated server you own, where Aria sets up the server, database, HTTPS and deploys from one aria.yaml file. You get a long-running Node server (no serverless cold starts or function timeouts), Postgres and Redis on the same machine, and one flat monthly bill.

Why developers move Next.js onto a dedicated server

Front-end platforms are built around stateless functions and edge caching. That model shines for marketing sites, but full-stack Next.js products (App Router, Server Actions, API routes, background jobs and a relational database) run into three friction points:

1. Database round-trips across the internet. When your Next.js server functions run in one cloud and your Postgres database lives in another, every sequential query pays network latency. Putting Next.js and Postgres on the same server drops local connection latency to sub-millisecond loopback speeds.
2. Function timeouts and background work. Streaming AI responses, generating PDFs, processing webhooks or running cron jobs shouldn’t require stitching together third-party queue services. On your own server, your Next.js web process runs alongside a persistent worker process from the same repo.
3. Predictable flat pricing. Instead of watching per-seat charges, bandwidth tiers and serverless execution units, you pay one flat monthly price for the server (from £8/month ex VAT on Aria, draft).

What a full-stack Next.js setup looks like in aria.yaml

With Aria, you don’t write Dockerfiles unless you want to. Your coding agent (Claude Code, Cursor or any other) reads your Next.js repository and writes an aria.yaml file at the root of your project:

name: my-nextjs-product
services:
  web:
    type: web
    port: 3000
    domain: app.example.com
  worker:
    type: worker
    command: node dist/worker.js
databases:
  db:
    type: postgres
  cache:
    type: redis

When you push or deploy:

• Railpack or your Dockerfile builds your Next.js app cleanly without manual build-script babysitting.
• Postgres and Redis are provisioned on the same server and their connection strings (DATABASE_URL, REDIS_URL) are wired into your web and worker services automatically.
• Automatic HTTPS is configured for your custom domain.
• Two-second rollback lets you switch back to the previous image if a release misbehaves.
• Smart GitOps redeploys only the services a commit actually touches.

Every Next.js feature works when you own the server

A common myth is that Next.js features break outside Vercel. In reality, running Next.js as a standard Node server (next start or standalone output) supports the full framework:

Next.js feature	On your own Aria server
App Router & React Server Components	Runs natively in the persistent Node process
Server Actions & Route Handlers	Full Node runtime with no 10-second or 60-second serverless timeout
Incremental Static Regeneration (ISR)	Cached directly on your server’s fast local NVMe disk
Image Optimization (next/image)	Runs on your server CPU with zero per-image optimization fees
Middleware	Runs in front of your routes on the server
WebSockets & long-lived streams	Supported natively because it is a real server, not a short-lived lambda

What you trade off (and when to stay on Vercel)

Honesty matters when choosing infrastructure:

• Single-region vs global edge. An Aria plan is one dedicated cloud server in the location you choose. If you need dynamic server rendering replicated across 30 countries simultaneously, use an edge platform. (For most SaaS apps, putting the server in the same region as your database and primary users is faster than edge functions calling a distant database anyway.)
• Fixed server memory. A server has a finite amount of RAM (4 GB on Starter at £8/mo, 8 GB on Developer at £15/mo, up to 32 GB on Scale Plus at £60/mo). Aria estimates your stack’s memory from aria.yaml before you deploy and alerts you when it is time to move up a plan.

FAQ

How do I deploy Next.js to my own server without Docker or Nginx setup?

Connect your repository to Aria and let your coding agent generate aria.yaml. Aria provisions and hardens the server, builds your Next.js app with Railpack (or your Dockerfile), sets up Postgres, wires DATABASE_URL, and configures HTTPS automatically.

Does next/image and ISR work on a self-hosted server?

Yes. When Next.js runs as a Node server on Aria, both next/image optimization and Incremental Static Regeneration (ISR) cache directly to your server’s NVMe disk with no extra configuration and no per-image billing.

Which Aria plan fits a Next.js app with Postgres?

A single Next.js app with a Postgres database fits on Starter (2 vCPU, 4 GB RAM, 40 GB NVMe, £8/month ex VAT, draft). If you run multiple apps, background workers or full self-hosted Supabase alongside Next.js, start with Developer (4 vCPU, 8 GB RAM, £15/month ex VAT).

Can I run multiple Next.js apps on one Aria server?

Yes. Aria does not charge per app or per site. You can run as many Next.js apps, APIs and databases on one server as its memory holds.

Ship your Next.js app on a server you own

Compare Aria vs Vercel, read our Vercel alternative guide, or see pricing.