Nuxt hosting in Russia

Hosting for Nuxt in Russia - Layero

Layero itself determines the Nuxt project and assembles it in accordance with the settings ssr and nitro.preset and distributes the result: static after nuxi generate runs through a CDN in Moscow, St. Petersburg and Yekaterinburg, and SSR is served by a scale-to-zero runtime with HTML caching on the edge.

What Layero is doing with the Nuxt project

There is no need to write any separate configs or platform adapters. Layero focuses on standard nuxt.config and selects the distribution path for the build type.

Auto-detect Nuxt

Layero finds nuxt.config.ts or nuxt.config.js, detects the Nuxt version and build mode and selects a command without manual configuration.

Static generation via CDN

If enabled nuxi generate or ssr: false, ready-made HTML and assets are uploaded to Object Storage and distributed via CDN in the Russian Federation.

SSR on scale-to-zero runtime

For the SSR build, Layero raises a container with a Nitro server, which sleeps without traffic and wakes up on the first request. HTML is cached on edge for 5 minutes.

CDN within Russia

Points of presence in Moscow, St. Petersburg and Yekaterinburg - low latency for the Russian audience, the site opens without a VPN.

Layero features for Nuxt

What is included in the standard deployment workflow - no additional charges.

Feature Layero
Auto-detection nuxt.config.*Yes
Static via nuxi generateYes - distribution via CDN
SSR at runtimeYes — scale-to-zero
Nitro presets - generatedYes — preset is chosen by Nuxt itself
useFetch/server/api endpointsYes in SSR mode
Custom domainYes - auto-SSL
Preview on branchesYes
Env variablesYes - encrypted, NUXT_PUBLIC_* on the client
AI-agent --jsonYes - machine readable CLI

How to deploy Nuxt to Layero

Three steps from a local project to a public URL in the .ru zone.

Run deployment

In the Nuxt project folder, run npx layero@latest deploy —no need to install anything. Or link the GitHub repository in the panel app.layero.ru, and the build will proceed for each push.

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 distribute the project

Layero will detect Nuxt by nuxt.config, will build the project in accordance with the settings ssr and nitro.preset: result nuxi generate is distributed via CDN, and the SSR build is distributed via scale-to-zero runtime. The finished URL will appear in the panel in a few minutes.

What tasks is it suitable for?

Perfect fit

  • SSR applications with a focus on SEO - server-side rendering for crawlers
  • Multi-page sites on Nuxt with routing pages/
  • E-commerce: catalog + shopping cart with server-side page rendering
  • Content sites on Nuxt Content - Markdown pages and blogs
  • Documentation and onboarding sites with static build
  • Landing pages, corporate websites and portfolios

What is added

  • CDN with points of presence within Russia
  • HTML Edge Cache 5 minutes for SSR - no cold start again
  • Preview environments for each branch
  • Custom domains with automatic SSL
  • Encrypted env variables, NUXT_PUBLIC_* on the client
  • Machine readable --json for Cursor / Claude Code

Frequently asked questions

Static generation Nuxt (nuxi generate) works on Layero?
Yes. If in nuxt.config set ssr: false or the project builds with the command nuxi generate, Layero takes the resulting static HTML and assets and distributes them via a CDN with points of presence in Moscow, St. Petersburg and Yekaterinburg. There is no need to run any server processes - statics are served directly from edge.
Is SSR supported in Nuxt?
Yes. For SSR builds, Nuxt Layero raises scale-to-zero runtime: the container starts on the first request and goes to sleep when there is no traffic. HTML responses are cached on edge nginx for 5 minutes - repeated requests for the same content are sent quickly, without cold-start.
Server routes /server/api will they work?
Yes, in SSR mode. Server routes from the directory /server/api live inside the same Nitro application as SSR, and are accessible through the same paths as in dev mode. With static generation, the server does not rise - server routes are not available in this configuration.
Which Nitro preset should I choose for Layero?
No special preset is required. Nuxt itself selects a Nitro preset depending on the target and environment variables, and Layero distributes the resulting artifact: static - via CDN, server build - via runtime. If you don’t configure anything, everything is built using standard Nuxt tools.
How to set environment variables for Nuxt?
In panel app.layero.ru The project has an Environment Variables section. The values are stored encrypted and are inserted into both the build and runtime. Variables with prefix NUXT_PUBLIC_ are available on the client - Nuxt, by agreement, forwards them to runtimeConfig.public. Server variables remain only on the SSR-runtime side.
What happens to large SSR loads?
A separate runtime container is raised under SSR Nuxt. Edge-nginx caches HTML for 5 minutes, so bursts of traffic to popular pages are driven by the edge, not the SSR. For long-term high load, write to support - we will discuss a suitable runtime configuration. The platform is suitable for front-end product volumes.

Deploy a Nuxt project in a minute

There is a free plan. Log in by email or via Yandex - Layero will detect Nuxt and roll out the project.