Next.js
We've deployed thousands of Next.js applications at scale and have optimized the sherpa.sh infrastructure for maximum Next.js performance.
When deploying Next.js to sherpa.sh you get additional performance and scalability benefits you wouldn't get when self-hosting - with zero-configuration - thanks to our framework-defined architecture
Next.js Quickstart
To deploy your first Next.js application, follow our quick start guide. Your app will be live in ~2 minutes.
What you get out of the box:
Zero-configuration deployments that just work
Automatic HTTPS and custom domain support
Built-in performance optimization
Global, production-ready infrastructure that can scale.
Never pay for idle instances. Only pay for what you use.
Supported Versions
Next.js 15
Next.js 14
Supported Features
App Router
Page Router
Middleware functions
Edge V8 Isolates
Enterprise Only
Incremental Static Regeneration (ISR)
Server Side Rendering (SSR)
Static Site Generation (SSG)
Partial Pre-Rendering (PPR)
Beta
Layout (Nested, Parallel, Error)
Data Fetching Revalidate (10, 60)
Data Fetching (no-store, POST default, POST without cache)
Routing (default, no-cache)
Static Metadata
Dynamic Metadata (SSG, SSR)
Image Optimization
Architecture
To maximize performance - and savings - we use framework defined infrastructure to deploy your app. You can read about our infrastructure setup in more detail on the Next.js Architecture page.
Configuration
We believe in convention over configuration. Your existing next.config.js works immediately - no additional setup required. When you need customization, our platform stays flexible.
next.config.js overrides
To prepare your application for our infrastructure, the sherpa.sh platform will override some of the values in your projects next.config.jsfile. Below you will find descriptions of the overridden values:
assetPrefix: We deploy your static assets to a specialized static CDN. We override the
assetPrefixso your app knows to ask the CDN for your static files.generateBuildId: We set a unique hash for each build that correlates with a deployment in the sherpa.sh portal.
cacheHandler: We maintain a globally distributed cache to enhance performance of PPR, ASO, and other caching functionality of Next.js. Each application gets a slice of the cache. This is our custom handler for read/write/delete to your applications portion of the cache.
cacheMaxMemorySize: Set to 0 because your application will use the global cache.
headers: We append a
cache-controlheader to your existingnext.conf.jsheaders for static asset caching best practices. If you need custom control over this header, you can configure it from inside the portal.output: This always is set to
standaloneto minimize deployment bundles and make deployments compatible with our global infrastructure.allowedOrigins: Set to a wildcard of your apps domain
*.[YOUR_DOMAIN]to ensure your server actions and other Next.js functionality works in the global deployment setup.
Image Optimization
By default, sherpa.sh supports image optimization and respects all your Next.js config settings. Optimized images are stored in our global cache infrastructure and then served by our CDN until the content goes stale based on the cache-control headers sent by Next.js to the CDN.
Enterprise Features
Have a unique need? Our enterprise features deliver additional capabilities:
Edge runtime capabilities: Run your middleware at the edge in v8 isolates.
Custom deployment configurations: Have a special need? We can customize our platform.
Advanced security features: If you need SOC II, HIPAA, or FedRamp certified deployments.
Dedicated support staff: Dedicated account manager and support engineers for your company's unique needs.
Last updated