How a visit reaches a site

Every Keel site is served through Cloudflare, so every request takes the same path, over HTTPS all the way.

  1. A visitor’s browser

    Asks for a page at your site’s address.

  2. Cloudflare

    Answers from its cache when it can, close to the visitor. Anything else goes on to Keel, and Cloudflare checks Keel’s certificate before it sends anything.

  3. Keel, in Canada

    Works out which site the address belongs to and renders the page from that site’s own content. Images and files come from private storage, through Keel.

Signing in

Nobody signs in to Keel with a password, and every session has an end.

  • No passwords

    People sign in with a sign-in link we email them, or with a passkey: their device’s fingerprint, face or PIN. Keel stores no passwords, and it won’t start if one is ever found in its database.

  • Sign-in links that can’t be reused

    Each link works once and expires after 15 minutes. Keel stores only a fingerprint of it, never the link itself, and the link never appears in our logs.

  • Passkeys tied to Keel

    A passkey works only on app.keelpage.com, so a look-alike site can’t use it to sign in as you.

  • Sessions that end

    A session ends after 12 hours without use, and 7 days after you signed in at most, however active you are. Sign out everywhere ends your other sessions within a minute.

Access and records

Who can get in, what agents may do, and the record Keel keeps of all of it.

  • Keel’s own team

    Our system administrators sign in with their Microsoft work accounts, and only accounts on an allow-list get in. Keel checks that list again whenever they use their access.

  • Agents without long-lived keys

    AI agents get 15-minute tokens for one site, only after a person approves them, and they can’t manage people, domains, bots or system settings. How agent access works

  • An audit log of everything

    Every action in Keel, by a person or an agent, is recorded: who, what, which site, when, and whether it was allowed. Refused attempts are recorded too. Site administrators can read their own site’s log.

  • No raw IP addresses

    The audit log and contact messages keep a keyed fingerprint of an IP address, never the address itself. Rate limits check the address in memory and never store it.

Where your site lives

Where Keel runs, and how it keeps each site’s content, files and secrets.

  • Hosted in Canada

    Keel’s servers, database and file storage are in Microsoft Azure’s Canadian regions. Every site is served through Cloudflare, which keeps cached copies of public pages and images around the world so they load quickly.

  • Each site kept apart

    Keel works out which site to show from the web address alone. An address it doesn’t know gets a “page not found” page, never another site’s content.

  • No public storage

    Every storage container Keel uses is private. Images and files reach visitors through Keel, never through a public storage link.

  • Secrets in a vault

    The keys Keel uses to reach other services are kept in Azure Key Vault, not in its code.

Privacy on this site

This site has no advertising and no third-party analytics. When you use the contact form, we receive what you type, the time you sent it, your browser’s user agent and a keyed fingerprint of your IP address, and your details go into our customer-relationship tool so we can follow up. We send product news only if you tick the box for it. A Cloudflare Turnstile check runs in your browser to stop automated spam. The privacy notice has the details.

Questions about security?

Ask us how Keel would handle your site and your data. We’ll reply by email.