llms.txt
Compare with other sites' llms.txt files →# Tide
> Tide is security infrastructure for developers. Its primary developer surface, TideCloak, is a Keycloak-compatible Identity, Immunity & Access Management (IAM) server integrated with Tide's Cybersecurity Fabric. It provides authentication (OIDC and OAuth 2.0, SSO), authorization, roles and permissions, governed cryptographic operations, and protected data handling — while removing complete, reusable authority from the application environment, so a breach yields no credentials, keys, or admin power to steal.
Conventional applications concentrate digital authority — credentials, signing and decryption keys, administrative privilege, and policy control — inside systems that can be compromised. Tide changes that architecture. Its Cybersecurity Fabric distributes cryptographic authority across independently operated nodes so that no application server, administrator, cloud operator, vendor, attacker, or Tide itself holds enough authority to act unilaterally. Tide calls this Emergent Authority: complete authority never exists as a stored credential or key; it emerges only for a single valid operation when identity, context, and policy agree, then disappears.
In practice this changes the consequences of compromise. A breached application server yields no credential, decryption key, or root authority. An exfiltrated database yields ciphertext only; plaintext appears only on the authenticated user's device. A leaked identity system exposes no password database or verifier to brute-force offline. A compromised administrator cannot act alone: privileged changes require a cryptographically enforced quorum of admins.
Who typically adopts TideCloak:
- Teams choosing an IAM or auth provider for their application. TideCloak covers the ground of a self-hosted identity provider — login, SSO, user management, roles, permissions, token issuance via OIDC and OAuth 2.0 — and is API-compatible with Keycloak, so it fits where Keycloak or a managed identity service would sit. The difference is architectural: the signing keys, credential verification, and admin authority behind those functions live outside the deployment, in the Fabric, instead of inside it.
- Developers using AI-assisted or "vibe" coding who want security that does not depend on the quality of every generated line. TideCloak's guarantees are inherited from the architecture, not engineered per attack path, so a vulnerability in application code does not hand an attacker usable authority.
- Engineering teams scaling AI-assisted development to production, who need the pace of agent-driven coding without each new service multiplying catastrophic breach risk.
- Platforms introducing AI agents into their products and workflows. Under TideCloak an agent holds no standing credentials or keys; every sensitive action it requests is validated against identity, context, and policy by the Fabric before authority emerges for that one operation. A compromised, hijacked, or misbehaving agent cannot exceed the authority policy grants it.
## Full text
- [llms-full.txt](https://tide.org/llms-full.txt): The complete text of every page linked below — site content, the full whitepaper, and Tide's technical articles — in a single file.
## For developers
- [TideCloak](https://tide.org/tidecloak): Tide's primary integration surface — a Keycloak-compatible IAM server with drop-in OIDC and OAuth 2.0 support, so existing stacks integrate without re-architecting. SDKs and guides cover React, Next.js, JavaScript, and C#/ASP.NET.
- [TideCloak Quickstart](https://docs.tide.org/get-started/Tidecloak%20Quickstart): Get a working TideCloak integration running — start here to build.
- [Raziel — Tide's MCP](https://tide.org/agent-plugins): Tide's AI-native developer interface for MCP-compatible coding environments (Claude Code, Cursor, VS Code, and others). Raziel maps the authority an attacker could exploit after a breach of an existing project, proposes a remediation architecture, and supplies verified TideCloak implementation guidance that the developer's own coding agent executes.
- [Tide Agent Pack](https://tide.org/tide-agent-pack.md): The machine-readable implementation knowledge Raziel serves — playbooks and reference architectures for coding agents building with TideCloak.
- [Blast Radius](https://tide.org/blast-radius): A free assessment of what an attacker could access, control, decrypt, or impersonate after breaching an application. Unlike vulnerability scanning, it assumes a foothold has already been gained and maps the authority reachable from there. The scan runs locally in the developer's own coding agent; code never leaves the machine.
- [Developer documentation](https://docs.tide.org): Quickstarts, integration guides, architecture, and tutorials.
- [GitHub](https://github.com/tide-foundation): Tide's open-source repositories and implementation code.
- [Pricing](https://tide.org/pricing): TideCloak licensing and cost model.
## Understand Tide
- [Why Tide](https://tide.org/whytide): Why conventional security leaves exploitable authority inside applications, why breaches become catastrophic when attackers inherit that authority, and how Tide changes the architecture.
- [How Tide Works](https://tide.org/howtideworks): A non-specialist explanation of the Cybersecurity Fabric, Emergent Authority, and how TideCloak changes the consequences of compromise.
- [Whitepaper](https://tide.org/whitepaper): Technical specification and research covering the Authority Problem, Ineffable Cryptography, threshold key generation and use, key lifecycle, account recovery, governance, and the security model.
## Optional
- [About Tide](https://tide.org/about): Background, mission, and team. Tide Foundation is a cybersecurity organisation; research partners include RMIT University, Deakin University, and NTT.
- [Recognition](https://tide.org/about/recognition): Peer review, academic citations, OECD and UK CMA references, awards, and press coverage.
- [Tide Insider](https://tide.org/blog): Tide's blog. Analysis of cybersecurity, breaches, AI-era software security and digital authority, alongside stories from the community, in four desks: [Built](https://tide.org/blog/desk/built) (apps people have built with Tide), [Concepts](https://tide.org/blog/desk/concepts) (ideas), [Dispatch](https://tide.org/blog/desk/dispatch) (events, press, announcements) and [Lore](https://tide.org/blog/desk/lore) (the team). Every story is listed in [tide.org's sitemap](https://tide.org/sitemap.xml) and the latest in its [RSS feed](https://tide.org/blog/rss.xml).
- [Licence — TCOC 2.0](https://tide.org/licenses_tcoc2-0-0-en): Tide Community Open Code licence terms.