Deployloft hosts your static build — HTML, CSS and JavaScript — over HTTPS. Sign up with your email, create a project with a slug, drop the folder from your computer and it goes live at https://<slug>.deployloft.com. Every deployment is kept, so you can roll back.
Files go into a draft deployment and each one is re-read from storage and byte-checked against what you declared. The pointer that your address resolves through only moves once every file has verified, so an upload that fails never changes what is live.
Each deployment keeps its own files, so moving the pointer back to a past version is one click in the panel. Attempts that did not make it are recorded with the reason they stopped, and a half-uploaded draft left behind is cleaned up automatically.
Your content is served from <slug>.deployloft.com with a Content-Security-Policy: sandbox, so third-party JavaScript on a hosted page cannot read the session cookie of the panel. Responses also carry nosniff, a closed referrer policy and real cache headers. A project of your own can take its origin back with the “Browser storage” switch, to keep visitor data in the browser.
Tu contenido se sirve desde <slug>.deployloft.com con Content-Security-Policy: sandbox, de modo que el JavaScript de terceros de una página alojada no puede leer la cookie de sesión del panel. Las respuestas llevan además nosniff, referrer cerrado y cabeceras de caché reales. Un proyecto tuyo puede recobrar su propio origen con el interruptor «Datos en el navegador», para guardar datos del visitante.
Votre contenu est diffusé depuis <slug>.deployloft.com avec une Content-Security-Policy: sandbox, si bien le JavaScript tiers d’une page hébergée ne peut pas lire le cookie de session du tableau de bord. Les réponses transportent aussi nosniff, une politique de referrer fermée et de vrais en-têtes de cache. Un projet à vous peut reprendre sa propre origine par le commutateur « Données dans le navigateur », pour garder des données chez le visiteur.
Seu conteúdo é servido por <slug>.deployloft.com com Content-Security-Policy: sandbox, então o JavaScript de terceiros em uma página hospedada não consegue ler o cookie de sessão do painel. As respostas também trazem nosniff, referrer fechado e cabeçalhos de cache reais. Um projeto seu pode pedir a própria origem no interruptor «Dados no navegador», para guardar dados do visitante.
Files, versions and links: every project is one slug, one folder of verified files and one address of its own.
Portfolios, documentation sites, landing pages, game builds, internal pages: anything that ends up as plain files in a folder.
Open the panelUpload the output folder of any static generator, or a hand-written folder with a single HTML file. The address goes live once the last file is verified.
Uploads land in a draft deployment. Nothing becomes public until every file has checked out, and a draft you walk away from is removed on a schedule.
The slug you choose becomes the hostname: https://<slug>.deployloft.com. Slugs are unique across the whole system, so no two projects share an address.
A path like /contacto redirects to /contacto/ and serves the index.html inside it. Ship your own 404.html and it is served with status 404 instead of a blank error.
Start free. When you run out of room, buy capacity: a one-time pack that stays yours for good, or an annual plan that is cheaper and lasts twelve months.
0 USDforever
5 USDone-time
12 USDone-time
35 USDone-time
22 USDper year
Every payment is invoiced by Lemon Squeezy (Stripe), our merchant of record: they calculate and remit sales tax or VAT for your country, send you the receipt and keep a portal where you can download it again. Deployloft only reads the payment and adds the capacity to your account. Prices are in US dollars. Every site serves under a budget of requests per minute, ten times larger on a paid plan, and all the sites share one pool of requests per day.
Three steps, and every line below is what the code running today does.
# Step 1 — an account of your own: email and password
POST /api?action=register { email, name, password }
POST /api?action=login { email, password }
# 10 characters minimum, stored as a salted PBKDF2 hash
# the session cookie is HttpOnly, Secure and SameSite=LaxNo roadmap items: every line below is in the code that serves your files right now.