Servers in Russia

The zero layer of your website

Free deployment of sites and apps to servers in Russia — one command, from Git, your terminal or an AI agent. No VPN, no throttling, no blocks

  • CLI
  • Agents
  • Claude Code
  • Cursor
  • Codex CLI
$npx layero@latest deploy
Start deploying
Documentation
Sign in by email or with Yandex CDN in Moscow, St Petersburg, Yekaterinburg HTTPS out of the box Deploys in 30–60 seconds
CDN inside Russia

Servers and traffic —
inside Russia only.

CDN points of presence in Moscow, St Petersburg and Yekaterinburg. No VPN, no throttling, no sanctions risk. Billing in roubles, and .ru domains work exactly as they should.

Moscow St Petersburg Yekaterinburg
MOW LED SVX
Four ways

How to publish a site

Every route gets you the same thing: a working address, HTTPS and a CDN — free.

From a folder

Drag the project folder straight into the dashboard — Layero unpacks it, detects the framework, builds and publishes. No git, no CLI, nothing to install. Works for static files and frameworks alike.

Drop a folder here

From a repository

Connect GitHub and pick a repo. Every push is a new build: a preview per branch, production from main. The webhook is installed only on the repository you choose.

demo/my-appmain · private
Import
demo/storefrontmain · public
Import
demo/marketingmain · public
Import

From the terminal

No git, no webhook, no global install. The CLI packs the folder, sends it to Layero, and Layero builds and publishes. Ideal for AI agents (Cursor, Claude Code), prototypes and CI.

$ npx layero@latest deploy
▸ detected: vite · packing · building
✓ Published

Through MCP

Add the Layero MCP server to your AI editor (Cursor, Claude Code, Codex) and deploy straight from the chat with @layero — without switching to a terminal.

@layero deploy the project to production
Runs inside the editor
Frameworks

Any framework fits

From a static landing page in plain HTML to a full-stack app on Next.js, Remix or FastAPI. More than 20 frameworks — Layero recognises yours and picks the build for it: static files, server-side rendering, a Node container or a Python one.

Vite
SPA
React, Vue, Svelte, Solid
npx layero@latest deploy
Details
Next.js (static)
SSG
output: export
npx layero@latest deploy
Details
Astro
SSG
Content sites, blogs
npx layero@latest deploy
Details
SvelteKit
SSG
adapter-static
npx layero@latest deploy
Details
Nuxt
SSG
generate / static
npx layero@latest deploy
Details
Create React App
SPA
react-scripts build → CDN
npx layero@latest deploy
Details
Gatsby
SSG
gatsby build
npx layero@latest deploy
Details
Prebuilt static
HTML
A folder of already-built files
npx layero@latest deploy
Details
Angular
SPA
ng build → CDN
npx layero@latest deploy
Details
Docusaurus
SSG
docs and knowledge portals
npx layero@latest deploy
Details
VitePress
SSG
fast docs on Vite
npx layero@latest deploy
Details
Storybook
SSG
UI component catalogue
npx layero@latest deploy
Details
Eleventy (11ty)
SSG
lightweight static site generator
npx layero@latest deploy
Details
Hugo
SSG
Go generator, extremely fast builds
npx layero@latest deploy
Details
Features

Everything you need day to day

No extra services, no extra subscriptions. What usually lives across three providers is in one interface here.

A preview for every branch

Push a feature branch and it gets its own subdomain. Send the link to a designer or a client without touching production.

A unique URL per deploy

An address like my-app-a3f8d2c.preview.layero.app for every commit — handy for PR review and for comparing versions.

One-click rollback

Something broke? Open the history and hit “Roll back”. Ten seconds later production is healthy again.

Live build logs

Build output streams to your browser. When something fails you see it right there, with no trip to someone else’s CI.

Encrypted secrets

Environment variables are stored under AES-256-GCM and injected only at build time. VITE_*, NEXT_PUBLIC_* — as usual.

Custom domains and HTTPS

Point a CNAME at cname.layero.app — we handle the rest. The certificate is issued and renewed automatically.

Sign in the way you prefer

A code by email or Yandex ID — no password. GitHub can be linked separately so you can deploy private repositories.

Password protection

Put a simple login form in front of a preview and nobody else gets in. Two clicks in the settings.

Deploy history

Every build is an artifact in storage. You can see who, when, from where and at which commit — and make any of them active.

Who it is for

People pick Layero when…

AI-built site

The site was built in Cursor or Claude

The assistant wrote the code and you want to show it now. npx layero@latest deploy straight from the chat with the agent, and you have a working address. No git repository, no push to GitHub, no “I’ll deploy it later”.

Solo MVP

Shipping without DevOps

There is no infrastructure engineer and you would rather not hire one. A single developer gets the product to users with no scaffolding in between.

Hackathon

A demo before the deadline

An hour before the pitch and you need a public URL. One git push or npx layero@latest deploy and the link is ready to show the judges.

Team

Previews for PR review

Every feature branch is a live link, not a screenshot. QA checks a specific build instead of “their own copy” from a local laptop.

Agency

Dozens of client projects

Each gets its own subdomain and dashboard. The client signs in, looks at the preview and approves it — no more “could you send me the link?” emails.

CI

Deploy from GitHub Actions

npx layero@latest deploy --yes --prod --project <slug> in the pipeline. Publishing happens only once the tests pass, with no webhook on every push.

Pricing

Simple prices, no surprises

Free for personal projects. Pro adds custom domains, team organisations and analytics, and lifts the project limit.

Free
0 ₽ / month
  • Up to 5 projects
  • A preview for every commit and branch
  • HTTPS on *.layero.app subdomains
  • Deploy from git and via npx layero@latest deploy
  • Custom domains and SSL
  • Team organisations
  • Observability and web analytics
  • Lighthouse audits
  • Search-engine indexing
Mastercard Visa Mir Secure payment · 3-D Secure · YooKassa

Payment is taken from Russian bank cards through YooKassa. The subscription renews monthly and can be cancelled in one click from your account. Full terms are in the public offer (Russian).

FAQ

Short answers

What does it cost?
The free plan covers up to 5 projects, a preview for every commit, and *.layero.app subdomains with SSL. Pro is 990 ₽/month or 9,480 ₽/year (that works out at 790 ₽ a month): no project limit, custom domains, team organisations, observability, web analytics, Lighthouse audits and search-engine indexing. The first 14 days of Pro are free, and you can cancel before the first charge. Details in the Pricing section.
Why servers in Russia specifically?
The CDN runs on Yandex Cloud, with points of presence in Moscow, St Petersburg and Yekaterinburg. No exposure to sanctions, no throttling, billing in roubles, and .ru domains work as usual. Your visitors do not need a VPN to open your site.
What do I need to sign in?
An email address or a Yandex account is enough. Sign in with a code sent by email or through Yandex ID — no password, no separate registration.
Does it work with my framework?
Vite, Next.js (static and SSR), Astro, Nuxt, SvelteKit, CRA and Gatsby are auto-detected. Streamlit covers Python demos. Any npm run build that writes its output to dist works too.
Can I host a full-stack app?
Yes. If your backend answers HTTP requests — server-side rendering and API routes in Next.js, Nuxt or SvelteKit — Layero builds and runs the frontend and the backend together, on one address. There are no separate servers to configure.
What about a Telegram bot or a background worker?
No. Layero is serverless: it runs your code in response to a request rather than keeping a process up around the clock. Anything that has to stay running 24/7 does not fit — Telegram bots, workers and queues, WebSocket and game servers, self-hosted databases. Those need an ordinary server (VPS).
What if I have no git repository?
Run npx layero@latest deploy inside the project folder. The CLI packs your sources and sends them to Layero, which builds and publishes them. No webhook, no repository, no global install.
How do I deploy from Cursor, Claude Code or another AI agent?
Tell the agent: “deploy this through layero”. It runs npx layero@latest deploy --json in the project folder, auto-detects the framework (Vite/Next/Astro/SvelteKit/Nuxt/Gatsby/CRA/Docusaurus/static) and streams JSON events to stdout. On the first run the CLI prints {"event":"auth_required","url":"..."} — the agent shows you a link, you click once to authorise, and the final {"event":"ready","url":"..."} returns the preview URL. No git init, no push to GitHub, no global install. The full recipe for agents is at docs.layero.ru/en/cli/agents.
What if there is no code yet — can I build a landing page in the chat?
Yes — that is a separate tool: the @layero plugin for Cursor, Claude Code and Codex. It does not deploy an existing project, it builds a landing page from scratch: you describe the idea in one sentence, the plugin asks two or three short questions right in the chat, picks a structure and a design system, generates the files and publishes them. One-click install for Cursor from land.layero.app; one command for Claude Code and Codex. How it works: docs.layero.ru/en/plugin/intro.
Can I connect my own domain?
Yes. Add the domain in the project settings and Layero shows which DNS records to create at your registrar: a CNAME for a subdomain, an A record plus a TXT record for ownership verification on an apex domain. The SSL certificate is issued and renewed automatically.
Where are secrets stored?
Environment variables are encrypted with AES-256-GCM using a unique nonce per record. The encryption key is not stored in the database, so a dump on its own reveals nothing; the key never reaches your containers — only the decrypted values of your own variables do. They are available both at build time and inside the runtime container. Only prefixed variables such as VITE_* and NEXT_PUBLIC_* reach the client bundle.
How soon does the site open after a deploy?
Immediately. The project address is live the moment the build reaches the ready status — there is no warm-up to wait through. The layero.app zone resolves straight to the platform load balancer, so both the first deploy of a new project and every branch preview open right away. This used to take 5–15 minutes while the address warmed up on the CDN; the CDN is out of the path for user sites now, and the wait went with it.
Is Layero the same thing as Layer0 or Edgio?
No, these are different products. Layero is a Russian platform for deploying sites and full-stack apps, with a CDN inside Russia: Moscow, St Petersburg, Yekaterinburg. Layer0 was the earlier name of a PaaS by Moovweb, later renamed Edgio; it has no relation to Layero — different owners, different infrastructure.

Publish a site in a minute

A minute to sign up, a minute for the first deploy. Use an account you already have.

You can sign in by email or with Yandex