every.link is in private beta. Request access

Security

Security by boundary

Customer-authored sites and the management application use separate origins with a browser-enforced app cookie boundary.

Uploaded code cannot share the app session

Customer sites run on *.every.link. Authentication, billing, and administration run on app.every.link. The dashboard session uses a Secure, host-only __Host- cookie, which browsers reject when a subdomain tries to attach a parent-domain attribute. The marketing apex is static and never sets application cookies.

Tenant resolution is account-scoped

A content request resolves the account from its host and the account-unique site from the first path segment, then recovers the site's owning workspace. Dashboard queries retain both account and workspace scope.

Publishing keeps history

Deploys are immutable. Site assets live in private object storage and are delivered only after the current deploy and viewer authorization have been resolved. Rollback selects an older deploy rather than modifying or replacing files.

Access is evaluated on every request

Sites can be public, password-protected, limited to signed-in viewers, restricted by verified email domain, or governed by SAML rules. Every site remains beneath its account host and project path.

Report a vulnerability

Send a concise reproduction, affected URL, and potential impact tosupport@every.link. Please do not include live credentials or personal data in the first message.