Describe the site. It goes live.
You talk to Loom, it writes the pages and publishes them at a public address of your own. No server to rent, no deploy to configure, no FTP.
How it works
Three steps, and the third is one click.
You ask
In plain language — "a page for my bakery, with the menu and a WhatsApp button". No template to pick, no builder to learn.
Loom builds it
The pages appear inside your project — yours, visible, editable. Change the colour, the words, the order. Nothing is public yet.
You publish
Pick the address and it is live in seconds — from the panel, or by asking Loom: "publish this".
The address
The name is yours, and it does not move when the site does.
Choose any name that is free. Updating the site creates a new version at the same address — the link you already shared keeps working, and previous versions are kept.
Public address
entelecy.store/corner-bakery
Letters, numbers and hyphens. The address is yours while the site exists, and stays the same on every republish.
Guarantees
The tedious part is already done.
Publishing a site normally means choosing a host, pointing DNS, issuing a certificate — and repeating it on every change. None of those steps exist here.
HTTPS, unasked
Certificate and padlock handled for you. No "not secure" warning.
Updating keeps the link
Each publish is a new version at the same address.
You can go back
Previous versions are kept. A bad publish is one step back, not a rebuild.
Offline when you say so
Reversible and immediate. The content stays yours.
Checks what goes with it
A scan looks for a password or key left in the code — and refuses the publish instead of exposing it.
Your files stay yours
The source stays in your project. Publishing takes a copy; it moves nothing.
If the scan finds a credential, the publish is refused and nothing goes up. A leaked secret cannot be recalled: the second it was public, it may already have been read.