Deploying from GitHub
Connect a repository and every git push publishes a new version automatically.
Environments, previews and production
One stable apex per project, preview links for branches and an explicit promote — the Vercel-like domain model in Layero.
layero.json — configuration in the repository
A file in the repository sets the framework, the install and build commands, the output folder and the Node version. Versioned in git, readable by agents (Claude, Cursor), stronger than any dashboard setting.
Environment variables
Env vars are encrypted with AES-256-GCM and available at build time and inside the runtime container.
Custom domains
Attach a domain you own to a project and Layero issues the Let's Encrypt HTTPS certificate itself — no manual certbot, no steps in the Cloudflare panel.
Custom HTTP headers
Add your own HTTP response headers (HSTS, X-Frame-Options, CSP, etc.) to a static site via a _headers file in the build output. Netlify-style syntax with path and wildcard support.
The 404 page and the SPA fallback
How a static site on Layero answers URLs that do not exist. Your own 404.html with a real 404 status (Next export, Astro, Hugo), or an index.html SPA fallback for apps with client-side routing. Controlled through the _redirects file.
Node.js and Python versions
Which versions are supported, how to pin one, and what happens when a version is retired.