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
DocumentationServers and traffic in Russia
Sites and web apps work all across Russia — no VPN, no throttling, no sanctions risk. Billing in roubles with Russian cards, and support in Russian.
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.
From a repository
Connect GitHub, GitVerse, GitLab, GitFlic or SourceCraft, then pick a repository. Every push is a new build: a preview per branch, production from main. The webhook is installed only on the repository you choose.
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.
Through an AI agent
A skill and an MCP server for any agent: say “deploy this site to layero.ru” in your editor. Got a repository — the agent connects it; got a folder — it deploys through the CLI; the site is already live — it reads the logs, rolls back, connects a domain.
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.
Features
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 demo-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 suits
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”.
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.
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.
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.
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.
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
Free for personal projects. Pro adds custom domains, team organisations and analytics, and lifts the project limit.
- ✓Up to 5 projects
- ✓A preview for every commit and branch
- ✓HTTPS on
*.layero.appsubdomains - ✓Deploy from git and via
npx layero@latest deploy - —Custom domains and SSL
- —Team organisations
- —Observability and web analytics
- —Lighthouse audits
- —Search-engine indexing
billed yearly at 9,480 ₽. Or 990 ₽ a month
- ✓Everything in Free
- ✓Unlimited projects
- ✓Custom domains with automatic SSL
- ✓Team organisations
- ✓Observability and logs
- ✓Web analytics
- ✓Lighthouse audits
- ✓Search-engine indexing
- ✓No Layero branding
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
What does it cost?
*.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?
.ru domains work as usual. Your visitors do not need a VPN to open your site.Can I publish a site without an account?
What do I need to sign in?
Does it work with my framework?
npm run build that writes its output to dist works too.Can I host a full-stack app?
What about a Telegram bot or a background worker?
What if I have no git repository?
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?
npx skills add LayeroInfra/layero-agents. In Claude Code the layero@layero plugin takes its place; in Cursor and Codex, the MCP server. From there the agent picks the path itself. A connected repository: a push to a branch gives a preview, a push to main goes to production. A folder with code: npx layero@latest deploy --json; on the first run the CLI prints a sign-in link, and the final ready event returns the site address. A site already on Layero: through MCP the agent reads logs, diagnoses a failed build, rolls back, connects domains, edits variables, reads analytics and the Data API. Details: docs.layero.ru/en/agents.What does the Layero MCP server do?
https://mcp.layero.ru/mcp (Streamable HTTP) gives the agent site and build status, logs and diagnosis of a failed build, rollback, domains, environment variables, analytics, publishing of prebuilt static files and the Data API. One click in Cursor; in any other agent — npx -y add-mcp https://mcp.layero.ru/mcp; commands for every client are collected at docs.layero.ru/en/agents/install. Sign-in is OAuth in the browser; CI and headless environments use the LAYERO_TOKEN token.Can I connect my own domain?
Where are secrets stored?
VITE_* and NEXT_PUBLIC_* reach the client bundle.How soon does the site open after a deploy?
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?
Publish a site in a couple of minutes
A minute to sign up, a minute for the first deploy.