What about large assets and dist limits?

The entire content of dist is uploaded to Object Storage and distributed via CDN. Vite's asset inlining and code-splitting work as is. It is better to put heavy media on S3 or a third-party CDN and connect it via URL, rather than pushing it into the repository - this is a general recommendation for any front-end hosting.

Vite hosted in Russia

Hosting for Vite in Russia - Layero

Q: What Vite presets are supported?

All official Vite presets: React (@vitejs/plugin-react, @vitejs/plugin-react-swc), Vue (@vitejs/plugin-vue), Svelte, Preact, Lit, Solid, vanilla TS/JS. Layero is not tied to a specific preset - the very fact of a Vite project is determined by vite.config.{js,ts,mjs} and/or vite dependencies in package.json, npm run build is launched, and the contents of dist are published.

Q: How to forward VITE_* environment variables?

Add variables in the project settings on app.layero.ru. At the build stage, Vite inserts into the client bundle only variables with the VITE_ prefix - this is the behavior of Vite itself, not Layero. The remaining variables are available as build-time env, but are not sent to the client. For secrets that should not be leaked to the browser, do not prefix them with VITE_.

Q: How to set up a custom domain for a Vite site?

In the project panel, add a domain and register the CNAME to cname.layero.app with your DNS provider. An SSL certificate is issued automatically. Apex domains, subdomains and wildcards for preview environments are supported.

Vite is the fastest frontend builder: dev server on ESM, build on Rollup, any popular framework via a plugin. Layero collects Vite-project, distributes dist via CDN in Moscow, St. Petersburg and Yekaterinburg and connects a custom domain with auto-SSL. Deploy - with one command, without VPN and without foreign cards.

Start free Documentation

What Layero does with the Vite project

Vite on Layero is pure static on a fast Russian CDN. No server part, no cold-start, no hidden limits on the number of routes.

Auto-detect Vite

Layero sees for himself vite.config.js, vite.config.ts or dependency vite in package.json and selects the build command. There is no need to manually specify a preset.

Pure static on CDN

After vite build contents dist is uploaded to Object Storage and distributed via CDN with points of presence in Moscow, St. Petersburg and Yekaterinburg.

Any preset

React, Vue, Svelte, Preact, Lit, Solid, vanilla TS/JS - all official Vite presets are supported. The only thing that matters to the platform is that the project is built through vite build.

AI agent

Cursor, Claude Code and other agents deploy Vite projects via npx layero@latest deploy --json - Machine-readable mode returns a URL without interactive tooltips.

Opportunities for Vite projects

Everything a front-end developer needs on Vite works out of the box.

Feature	Layero	Comment
Auto-detection `vite.config.*`	Yes	Sees `.js`, `.ts`, `.mjs` and dependency `vite`
React / Vue / Svelte / vanilla	Yes	All official Vite presets
`npm run build` → `dist`	Yes	Standard Vite artifact, no custom scripts
Custom domain with auto-SSL	Yes	CNAME on `cname.layero.app`, the certificate is issued automatically
Preview environments on branches	Yes	Separate URL for each push to a thread
Env variables `VITE_*`	Yes	Substituted into the client bundle at the build stage
Preview URL in ~30 seconds	Yes	Typical Vite-SPA build - tens of seconds
AI-agent `--json`	Yes	Native deployment mode for Cursor / Claude Code

How to deploy Vite to Layero

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

Run deployment

In the Vite 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 git push.

Log in

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

Get URL

Layero will see vite.config.{js,ts}, will start vite build, will pick up dist and will distribute via CDN in Russia. The preview URL will appear approximately 30 seconds after the build starts.

What tasks is Vite on Layero suitable for?

Perfect

SPA on React / Vue / Svelte with client-side routing
Landing pages and promo pages - fast Vite-stack
Dashboards and admin panels - Vite + React Query / Pinia
Portfolio and personal sites
Documentation on Vite (VitePress, Vocs) - if Docusaurus is not needed
Demo projects, prototypes, MVP - quick publication of preview-URL

What Layero adds

CDN with points of presence in Moscow, St. Petersburg, Yekaterinburg
Preview environment for each branch - separate URL
Custom domain with automatic SSL via CNAME
Env VITE_* - configured in the project panel
Deployment via AI agent: npx layero@latest deploy --json
Free plan, payment in rubles

Frequently asked questions

What Vite presets are supported?

All official Vite: React presets (@vitejs/plugin-react, @vitejs/plugin-react-swc), Vue (@vitejs/plugin-vue), Svelte, Preact, Lit, Solid, vanilla TS/JS. Layero is not tied to a specific preset - the very fact of the Vite project is determined by vite.config.{js,ts,mjs} and/or dependencies vite in package.json, starts npm run buildand the content is published dist.

How to forward environment variables VITE_*?

Add variables in project settings to app.layero.ru. At the build stage, Vite inserts only variables with the prefix into the client bundle VITE_ is the behavior of Vite itself, not Layero. The remaining variables are available as build-time env, but are not sent to the client. Secrets that shouldn't leak to the browser, don't prefix them VITE_.

Is SSR supported on Vite?

Vite SSR is an experimental feature of Vite itself; on Layero there is no separate runtime for the naked Vite SSR. If you need server rendering, use add-ons on top of Vite: Nuxt 3 (Vue) or SvelteKit (Svelte). They run on Layero as full SSR applications. For pure vite build (SPA mode) - static on CDN, everything is normal.

How to set up a custom domain for a Vite site?

In the project panel, add a domain and write CNAME to cname.layero.app from your DNS provider. An SSL certificate is issued automatically. Apex domains, subdomains and wildcards for preview environments are supported.

What about large assets and limits on dist?

Contents dist is completely uploaded to Object Storage and distributed via CDN. Vite's asset inlining and code-splitting work as is. It is better to put heavy media (videos, large archives) on S3 or a third-party CDN and connect it via URL, rather than pushing it into the repository - this is a general recommendation for any front-end hosting.

How to migrate a Vite project from Netlify or Vercel?

There is no need to rewrite the code: Vite is built the same everywhere. Do npx layero@latest deploy in the project folder or link the GitHub repository to app.layero.ru. Transfer Variables VITE_* in the project settings, connect your domain via CNAME - the SSL will release itself. For SPA routing Vite (react-router, vue-router) Layero gives index.html to unknown default paths.

Deploy Vite project in a minute

There is a free plan. Log in by email or via Yandex and receive a preview-URL in ~30 seconds.

Start free CLI docs