know.2nth.ai is one of two canonical 2nth.ai surfaces — a knowledge tree where every technology explainer is free, no signup, no email gates, no soft paywalls. Member access is auto-approved on signup — instant unlock for the operational depth; Partner is bespoke. Built modern; deliberately simple.
The access promise is plain: conceptual explainers are free. The "what it is", "how it works", and decision-frame parts of every leaf are open to anyone — humans browsing, agents loading, partners scoping. The conceptual layer is load-bearing for the public web; we don't gate it, ever.
Member is the operational layer on the same pages. Anywhere we share real patterns, code, and specifics — the install commands, the wrangler config, the sage-x3 GraphQL query, the dbt model, the validated env-var table — that's behind a free Member signup. One email, instant unlock, no password. We don't make people pay to learn what something is; we ask people to identify themselves before they take the implementation home.
Partner is a bespoke commercial frame for organisations whose own IP becomes a co-branded branch of the tree. Different conversation, different intake.
We don't gate the conceptual layer. We don't dim the page mid-thought. We don't run popups asking for newsletter signups. The Open / Member split is honest: read the explainer freely, sign up if you want the implementation. Both sides of the line are real; neither side is a tease.
No shared user accounts, no SSO across legacy properties. Each tier is its own conversion surface on know.2nth.ai — the knowledge tree itself, Member signup, and the partner inbox. Simple by design.
Read the tree. No account. No friction. The same content humans read, agents load, and partners build on.
Operational depth authored for teams who ship. Drop your email at /join — we'll email when the first batch lands.
Your IP operationalised as a skills tree. Private branches, co-branded nodes, agent context packages keyed to your stack. [email protected]
The signup at know.2nth.ai/join.html is a free, instant, no-password form — one email, one consent checkbox, you're on the early-access list. No content is currently gated; the form is how we know who's reading and who to notify when the operational content classes ship.
What happens when you submit the form:
localStorage["2nth-know-member"]) that gate.js watches for the future — the hook stays in place but no element on the site currently uses it.know.2nth.ai is deliberately decoupled from the legacy 2nth.ai auth surface. There is no account to manage, no password to recover, no cross-domain cookie to debug. When real Member content ships and warrants real gating, magic-link verification (Phase 2) is the path — not a return to the legacy stack.
Partner is for organisations whose methodologies, internal frameworks, or domain expertise should live as a co-branded branch of the 2nth.ai tree. It's a longer commercial conversation; intake is a real conversation.
Partner intake is at [email protected]. Conversations typically cover:
The access surface is small on purpose. A few things that could be here aren't — because not building them is itself the design choice.
Every leaf, every section, every line of code on the tree is fully readable without signup. The data-tier="member" markers were pulled site-wide on 2026-05-10 — we'd rather show the work while real auth is still being built than half-gate content with a soft overlay that creates friction without delivering on the promise. The signup form on /join still exists for early-access updates and so we can see who's reading.
No "Sign In", no password, no profile page, no avatar. The legacy 2nth.ai auth surface caused real maintenance pain; the new properties (2nth.ai and know.2nth.ai) consciously skip that pattern. If accounts become necessary, they will be authored fresh, on these properties' own terms.
Member is currently a free signup — the form is for tracking who's interested, not for billing. Pricing follows value; value follows the content classes that haven't been authored yet (operational nodes, role-based bundles, deployment templates). When that arrives, gating returns properly.
Real Member gating returns when the magic-link verification flow is built (Cloudflare Worker for signed tokens + email send + cookie-set verification). Cross-device sessions, real email verification, no passwords, no SSO. The gate.js hook stays in place; re-tagging code-bearing sections as data-tier="member" is one perl command when Phase 2 lands. Until then, content is the priority.