know.2nth.ai About
About · access & the project

Open stays open. No legacy auth. No soft paywalls.

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 a waitlist while the next content classes ship; Partner is bespoke. Built modern; deliberately simple.

Live Open / Member / Partner No legacy SSO HubSpot waitlist JHB · built local

Open stays open.

The access promise is plain: technology explainers are free. Every leaf in the existing tree — framework deep-dives, decision guides, the agent-context format itself — reads without an account, without an email gate, without a banner asking you to subscribe. That promise is on the access page; it is load-bearing.

Member is not a paywall on existing depth. It is a separate content class that does not yet exist publicly: operational skill nodes, role-based context bundles, deployment templates, curated learning paths. Member-tier content takes ongoing curation; explainers are a different shape and stay free.

Partner is a bespoke commercial frame for organisations whose own IP becomes a co-branded branch of the tree. Different conversation, different intake.

What we deliberately don't do

We don't email-gate explainers. We don't dim the second half of a page. We don't run popups asking for newsletter signups. The Open / Member / Partner architecture lets the access page tell the truth: everything labelled "All technology explainers" actually is.

Three tiers. Each its own surface.

No shared user accounts, no SSO across legacy properties. Each tier is its own conversion surface on know.2nth.ai — the knowledge tree itself, the waitlist, and the partner inbox. Simple by design.

Tier · default

Open

Read the tree. No account. No friction. The same content humans read, agents load, and partners build on.

  • + All technology explainers
  • + Framework deep-dives
  • + Decision guides
  • + Agent context format
Tier · waitlist

Member

Operational depth authored for teams who ship. Drop your email at /join — we'll email when the first batch lands.

  • + Everything in Open
  • + Operational skill nodes
  • + Role-based context bundles
  • + Deployment & integration templates
  • + Community access
Tier · intake

Partner

Your IP operationalised as a skills tree. Private branches, co-branded nodes, agent context packages keyed to your stack. [email protected]

  • + Everything in Member
  • + Private skills tree branches
  • + Co-branded domain nodes
  • + Agent context packages for your IP
  • + Institutional knowledge capture

From "Join" to "in your inbox".

The waitlist is the conversion surface for Member access until the first batch of operational content ships. It's a HubSpot form on know.2nth.ai/join.html — email and first name, one POPIA-compliant consent checkbox, that's it.

What happens when you submit the form:

  1. Your email lands in the 2nth.ai HubSpot CRM as a new contact, lifecycle stage Subscriber.
  2. Your browser stores a small flag (localStorage["2nth-know-member"]) so any future tier-gated section recognises you on this device.
  3. When the first batch of Member content ships, you get a launch email — one email, not a sequence.
  4. Existing explainers stay readable for everyone the entire time.

No accounts, no passwords, no SSO

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. The HubSpot waitlist is the Member-tier signal until real content needs more. Smaller blast radius; less maintenance.

When a private branch makes sense.

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:

  • Domain shape — whether your IP maps into an existing top-level domain (Business / Data / Design) or stands alone
  • Authoring cadence — private branches are kept fresh by either your team or ours; the choice shapes the commercial terms
  • Agent context packaging — how the resulting content is exposed to AI agents (alongside or instead of the public tree)
  • Institutional knowledge capture — many Partner engagements include translating tacit org knowledge (in heads or wikis) into the canonical-skill-node format

What's deliberately not built yet.

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.

No user accounts

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.

No paid tiers (yet)

Member is a waitlist, not a billing surface. The first batch of operational content will determine what Member access actually buys; pricing follows value, not the other way around.

No tier gates on existing explainers

The hook exists in gate.js — any element with data-tier="member" would be gated for non-members — but no element on any explainer page carries the marker. When Member content ships, it'll be new files, gated at the section level.

For the curious.