Partially. The revalidate mechanics work within the SSR runtime, but the full set of ISR features (on-demand revalidation, tags, background rebuild) is still limited on the platform. For most scenarios, a standard SSR with an HTML edge cache for 5 minutes is sufficient.

Hosting for Next.js in Russia

Hosting for Next.js in Russia - Layero

Q: Does Image Optimization work?

Yes, through the standard loader Next.js - the next/image component delivers optimized images via SSR-runtime. If you need maximum performance, you can use unoptimized or an external loader (for example, images from your storage).

Q: How to migrate Next.js from Vercel?

There is no need to change the code: the same App Router/Pages Router, the same next build. It is enough to link the GitHub repository to app.layero.ru or run npx layero@latest deploy in the project folder. Environment variables are transferred to the Layero panel (values are encrypted with AES-256-GCM, only NEXT_PUBLIC_* are included in the client bundle), the custom domain is connected via CNAME to cname.layero.app - SSL will be released automatically.

Where to deploy Next.js so that the site opens for Russian audiences quickly and without a VPN? Layero - Russian hosting for Next.js: auto-detect of the framework, support for App Router and Pages Router, SSR via scale-to-zero with HTML cache on edge, CDN in Moscow, St. Petersburg and Yekaterinburg. Deploy with one command npx layero@latest deploy or from GitHub.

Start free Documentation

What Layero does with the Next.js project

Layero handles Next.js the way the framework itself expects: static segments on the CDN, SSR routes on the runtime, which wakes up on request and goes to sleep when idle.

Auto-detect Next.js

Layero itself recognizes Next.js by package.json and config - for App Router, Pages Router and next export. There is no need to select any separate presets.

Statics + SSR via scale-to-zero

Static pages and assets are distributed from CDN within Russia. SSR routes are served by a container that wakes up when requested and goes to sleep when idle—the platform does not support an expensive always-on process.

SSR cache on edge

HTML SSR responses are cached on edge for 5 minutes, so repeat requests are returned in ~200 ms. Upon activation of the deployment, the cache is automatically invalidated so that users immediately see the new version.

Mode for AI agents

In Cursor, Claude Code and other agents, just say “backup via layero” - the CLI will start in mode --json, will return a structured result with a ready-made URL and errors in machine-readable form.

Next.js features on Layero

Which parts of Next.js run on the platform and in what mode.

Next.js feature	Layero
App Router (Next.js 13+/14/15)	Yes
Pages Router	Yes
Static export (`next export`)	Yes
SSR (server rendering)	Yes - via runtime, scale-to-zero
ISR (incremental static regeneration)	Partially
Image Optimization (`next/image`)	Yes - via standard loader
Custom domain with auto-SSL	Yes - CNAME on cname.layero.app
Preview environments for each branch	Yes
Environment variables (build + runtime)	Yes - AES-256-GCM, NEXT_PUBLIC_* to client

How to deploy Next.js to Layero

Three steps - from the project folder to the public URL.

Run deployment

In the Next.js project folder, run npx layero@latest deploy —no need to install anything. Or link the GitHub repository in the panel app.layero.ru: each push to the main branch will be collected and published automatically, and preview environments will be raised in the branches.

Log in to your account

Log in by email or through Yandex. An account is created automatically when you first log in - no separate registration is needed.

Layero will collect and publish

The platform will detect Next.js, execute next build, will decompose statics onto CDN, raise SSR routes to runtime from scale-to-zero. Environment variables are configured in the panel (values are encrypted with AES-256-GCM); only NEXT_PUBLIC_* - the rest are available only to server components and Route Handlers.

What tasks is Next.js hosting on Layero suitable for?

Perfect fit

Landing pages and promotional pages - static on CDN, instant TTFB
Corporate websites with .ru domains
Documentation and blogs on App Router
Marketing pages and SEO projects with server rendering
SSR applications (personal accounts, dashboards) - runtime wakes up on request
E-commerce on App Router - server components, dynamic routes, HTML cache on edge

What's included out of the box

CDN in Moscow, St. Petersburg and Yekaterinburg
Preview environments for each branch and pull request
Custom domains via CNAME → cname.layero.app, auto-SSL
Environment variables with AES-256-GCM encryption
Sign in by email or with Yandex
Machine Readable Mode --json for AI agents

Frequently asked questions about Next.js on Layero

Layero holding SSR Next.js?

Yes. Next.js server rendering works through a scale-to-zero runtime: the container with the SSR application wakes up to a request, HTML responses are cached on edge for 5 minutes. Cold start after warming up the cache is about 200 ms.

Is App Router working?

Yes. Layero supports both App Router (Next.js 13+/14/15) and Pages Router. Server components, layouts and Route Handlers are executed on SSR-runtime, static segments are served via CDN.

ISR supported?

Partially. revalidate-mechanics work within the SSR-runtime, but the full set of ISR features (on-demand revalidation, tags, background rebuild) on the platform is still in a limited form. For most scenarios, a standard SSR with an HTML edge cache for 5 minutes is sufficient.

Does Image Optimization work?

Yes, through the standard loader Next.js component next/image delivers optimized images via SSR-runtime. If you need maximum performance, you can use unoptimized or external loader (for example, images from your storage).

How much does Next.js hosting cost for a production load?

Free - 0 ₽: up to 5 projects, previews for each commit, *.layero.app subdomains with SSL; SSR-runtime and CDN are included in the free plan. Pro - 990 ₽/month or 9,480 ₽/year (790 ₽ per month): your own domains, unlimited projects, analytics and indexing in search engines. The first 14 days of Pro are free.

How to migrate Next.js from Vercel?

No need to change the code: same App Router/Pages Router, same next build. It is enough to link the GitHub repository to app.layero.ru or run npx layero@latest deploy in the project folder. Environment variables are transferred to the Layero panel (the values are encrypted with AES-256-GCM, only the NEXT_PUBLIC_*), the custom domain is connected via CNAME to cname.layero.app — an SSL certificate is issued automatically.

Deploy Next.js to Russian hosting in a minute

There is a free plan. Log in by email or via Yandex and publish your first Next.js project.

Start free CLI docs