Next.js on Exovon
Zero-configuration full-stack hosting for Next.js App Router and Pages Router. React Server Components, Server Actions, standalone output compilation, and edge static caching running in Google Cloud Mumbai (asia-south1).
Core Next.js Architecture
Unlike static-only hosts that force export mode or disable dynamic server logic, Exovon runs true full-stack Next.js with complete server runtime execution.
Regional Indian Compute (Mumbai)
SSR requests, Server Actions, and Route Handlers execute directly in Google Cloud Mumbai (asia-south1). This eliminates the 150ms+ cross-continental latency of US-hosted clouds for Indian and South Asian end users.
Hybrid Edge + Serverless Split
Static assets (/_next/static/*, CSS, SVGs, pre-rendered HTML) are delivered globally from Anycast edge points of presence. Dynamic route evaluations bypass cold paths and stream through warm serverless containers.
Automated Standalone Packaging
Exovon automatically leverages Next.js output: 'standalone'. By tracing and bundling only production dependencies, build output drops from over 1.2 GB to ~85 MB, yielding rapid container boots.
Native Image Optimization
The Next.js <Image /> component works out of the box using high-performance sharp in containers. Converted WebP and AVIF assets are automatically cached at the edge for sub-second retrieval.
Next.js Compatibility Matrix
Exovon supports all modern Next.js 13, 14, and 15+ capabilities across App Router and Pages Router.
| Feature | App Router | Pages Router | Runtime Pipeline |
|---|---|---|---|
| React Server Components (RSC) | Supported | — | Serverless Node.js streaming |
| Server Actions | Supported | — | Direct zero-downtime execution |
| API Routes & Route Handlers | Supported | Supported | Auto-scaling container runtime |
| Streaming & Suspense | Supported | — | HTTP chunked transfer streaming |
| Middleware & Edge Guards | Supported | Supported | Request intercept & header rewrites |
| Incremental Static Regeneration (ISR) | Supported | Supported | Dynamic background revalidation |
| Image Optimization | Supported | Supported | Containerized sharp + Anycast edge cache |
Deploying Next.js in 3 Steps
No Dockerfiles, custom YAML, or manual server provisioning required.
Connect Your Repository
Open the Exovon Dashboard, select New Project, and link your repository. Exovon automatically inspects your dependencies and detects Next.js.
Configure Environment Secrets
Import your environment variables via the dashboard bulk importer. Credentials are encrypted at rest with AES-256 GCM and injected into memory at runtime.
Deploy & Verify
Click Deploy. Exovon builds the standalone container on dedicated 4-core workers in Mumbai and exposes a secure .exovon.co.in domain with automated TLS 1.3 encryption.
Production Best Practices
Recommended patterns to maximize build speed, edge performance, and database throughput.
1. Configure Standalone Output
Declare output: 'standalone' in your Next.js configuration. This creates a lightweight bundle containing only necessary node_modules:
// next.config.ts
import type { NextConfig } from 'next';
const nextConfig: NextConfig = {
output: 'standalone',
images: {
formats: ['image/avif', 'image/webp'],
},
};
export default nextConfig;2. Wrap Client Search Queries in Suspense
When accessing URL query strings with useSearchParams() in App Router, wrap the client component in a <Suspense> boundary so the parent layout remains statically renderable:
import { Suspense } from 'react';
import SearchableClientComponent from './search-box';
import SkeletonLoader from './skeleton';
export default function Page() {
return (
<Suspense fallback={<SkeletonLoader />}>
<SearchableClientComponent />
</Suspense>
);
}3. Database Connection Pooling
Instantiate your ORM (Prisma, Drizzle) client as a singleton or attach a connection pooler (such as ExoStore Serverless Database with built-in pooling) to avoid exhausting active connections during burst autoscaling.
Observability & Telemetry
Real-time server logs and telemetry available in the project dashboard.
Stream server runtime logs and unhandled stack traces with severity filtering (INFO, WARN, ERROR).
Monitor real-world Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS) directly from visitor traffic.
Updating environment variables triggers an instant rolling restart (<2s) without re-running long compile passes.
Frequently Asked Questions
Do Next.js Route Handlers and Server Actions work?
Yes. Exovon deploys your application as an active serverless container. All Route Handlers and Server Actions execute natively with zero extra configuration.
Does Next.js Image Optimization work out of the box?
Yes. The Next.js Image component (<Image />) is fully supported with sharp in your container. Optimized WebP/AVIF variants are cached at the Anycast edge for high Core Web Vitals performance.
How do custom domains and SSL work?
Custom domains are available on paid plans (Starter, Pro, and Heavy). Exovon automatically provisions and renews TLS 1.3 certificates at no additional cost.
Where is the ExoStore database located?
ExoStore (managed Postgres) runs in Singapore (aws-ap-southeast-1) with ~35–60ms low-latency direct transit to our compute containers in Mumbai (asia-south1).