What kan.fyi is

You give kan.fyi a folder of static files — HTML, CSS, images, whatever a browser can read on its own. It gives you back a link. That is the whole product.

There is no build step, no framework, and no configuration file. A file, a folder, or a .zip becomes a URL.

What a site is

A site is one hosted thing: one owner, one address, one lineage of releases. Each time you send new files, you create a release — an immutable snapshot — and publishing swaps the site over to it. The old release stops being served the moment the new one lands, and the swap is atomic, so nobody ever sees a half-updated site.

Your site’s address never changes. See your site’s URL.

Two things are true at once

Every site carries a status and a visibility, and they answer different questions.

Status answers may this site serve at all? That is the on/off switch — held by you when you take a site down, and by us when a site is banned.

Visibility answers who may reach it once it does? That is your sharing decision: public, link-only, or private.

They are independent. A site can be switched off and private. Taking a site down does not erase your sharing choice, and changing your sharing choice does not switch anything on. Almost every “why can’t I see my site?” question is really a question about which of these two is in play, which is why Why isn’t my site live? is organised around them.

What it is not

kan.fyi does not run code. There is no server-side language, no database, no build pipeline, and no way to execute anything on our machines. If your project needs any of those, it needs a different host.

It also does not host anything that isn’t a website. The limits are shaped for pages, not for file storage.