Documentation

MEMBERSHIP TIERS, ACCESS & PARTNER PROGRESSION

How the 2nth platform membership works — from free Explorer through to Investor and Board. Including partner onboarding, access control, and authentication across all properties.

1. MEMBERSHIP TIERS

TierPriceTokensEmail TypeTarget
ExplorerFree50KPersonal OKPlatform exploration, first brief
Starter$100 / R1,850500KPersonal OKLanding pages, focused sprints
Designer$500 / R9,2003MOrganisation requiredWeb apps, brand systems
Builder$1,000 / R18,5008MOrganisation requiredFull SaaS MVPs with APIs
PartnerCustom1M–10MOrganisation requiredWhite-label, revenue share
InvestorBy invitationWhitelist-gatedBoard, data room, IP dashboard
Personal emails: Accepted for Explorer and Starter tiers only. This allows solo founders and individuals to explore the platform. Designer tier and above requires an organisation email to verify the business relationship.

2. PLATFORM ACCESS BY TIER

PropertyExplorerStarterDesignerBuilderPartnerInvestor
2nth.ai
mem.2nth.ai
2nth.io
developers.2nth.ai
2nth.org
2nth.me Independent — own auth, optional bridge to 2nth.ai
2nth.io access: Only Builder tier and above get infrastructure provisioning. Starter and Designer cannot deploy servers. They must upgrade to Builder to access managed hosting.

3. AUTHENTICATION MODEL

Per-Property Authentication

PropertyAuth MethodSession CookieIdentity Source
2nth.aiMagic link + JWT2nth_session on .2nth.aiOwn D1 database
mem.2nth.aiEmail + OTP2nth_mem_sessionOwn KV store
2nth.ioOTP via 2nth.ai SSO2nth_io_session2nth.ai OAuth
2nth.orgOTP via 2nth.ai SSO2nth_org_token2nth.ai OAuth + whitelist
developers.2nth.aiID + 4-digit PINdev_access / 2nth_sessionHardcoded + KV fallback
2nth.meEmail + OTP2nth_me_sessionOwn KV store (independent)

SSO Architecture

2nth.ai (Identity Provider)
├── OAuth2/OIDC endpoints
├── JWT signing (HS256)
├── User accounts in D1
│
├── 2nth.io ──── SSO via OAuth redirect
├── 2nth.org ─── SSO via OAuth redirect + email whitelist
├── developers ─ JWT session on .2nth.ai domain + PIN fallback
├── mem.2nth.ai ─ Own OTP auth (planned: SSO Phase 3)
│
└── 2nth.me ──── Independent (own OTP, own KV, no SSO)
    
Future SSO (Phase 3, May 2026): mem.2nth.ai will authenticate via 2nth.ai OAuth. The user signs in once on 2nth.ai and the session carries across to mem, io, developers, and org. Currently each property has its own auth for dev testing.

4. MEMBER JOURNEY

New Member Onboarding

Enter email
OTP code
Profile setup
Pick tier
Accept terms*
Account active

* Terms acceptance required for Starter tier and above. Explorer skips this step.

Tier Upgrade Path

Explorer
Starter
Designer
Builder
Partner
Investor
TransitionHowWhat Changes
Explorer → StarterSelf-service payment ($100)+450K tokens, terms acceptance required
Starter → DesignerSelf-service payment ($500)+2.5M tokens, org email required, production deployment
Designer → BuilderSelf-service payment ($1,000)+5M tokens, 2nth.io access, developer portal access
Builder → PartnerApplication + admin approvalPartner hub, showcases, skills, revenue share, partner terms
Any → InvestorInvitation only2nth.org access, data room, IP dashboard, board observer

5. PARTNER PROGRESSION

Becoming a Partner

Partnership is not a tier you buy — it's a relationship. Builders who demonstrate domain expertise and want to contribute to the ecosystem can apply for partnership.

Builder tier active
Apply via mem portal
Admin reviews
Partner terms signed
Partner active

What Partners Get

AssetWhereDescription
Partner Profiledevelopers.2nth.aiDedicated page with team, capabilities, skills, contract details
AI Showcasedevelopers.2nth.aiInteractive demo page showing AI transformation for their domain
Concept Demosdevelopers.2nth.aiWorking prototypes (e.g. SkiSpot, Boris, Toolpath Optimiser)
Skill Contributionsskills.2nth.aiDomain skills added to the 2nth skill tree (agentskills.io format)
Partner Hub Sectiondevelopers.2nth.aiScoped section in the hub — only visible to them + admins
Token Allocationmem.2nth.aiCustom allocation (1M–10M) based on partnership agreement
Revenue SharePartner agreement5–30% on client referrals (ZAR)

Partner Hub Access Control

WhatHow
Each partner has a scopedata-scope attribute on their hub group (e.g. scengineering)
Server-side filteringMiddleware strips HTML groups before serving — partners can't see other partners' sections
Path-level access/partners/gananda.html returns 403 for non-gananda users
Admin can grant/revokeCheckboxes on each group header — persisted via API to KV
View As impersonationAdmin dropdown to preview hub as any user

Partner Authentication

MethodDetails
ID + PIN4-digit PIN assigned on onboarding. Quick sign-in for daily use.
ScopeComma-separated list of sections visible (e.g. dronescan,scengineering)
Admin assignsCurrently manual — admin sets ID, PIN, and scope in config
FutureAuto-generate from mem.2nth.ai when partner role is approved

6. CURRENT PARTNERS

PartnerTypeIDScopeTokens
SC Engineering (incl. SkiSpot)Premium Buildmurraydronescan,scengineering10M
B2BS.AIPremier Developercraig-b2bfull
Proximity GreenTechnologymarkproximity-green
VibeCraftersDesign Agencyemmavibecrafters
Ctrl FutureAI Strategykathctrl-future
Republic LifestyleManufacturingrepublicrepublic-lifestyle
Gananda ConnectFinancial Advisorybarryfull
EatFitSAMedicalericaeatfitsa5M
Jonty Jankovich-BesanConsultingjontyjankovich
Rohrs & AssociatesCash & Paymentsbarryrrohrs2M
DurProWorkforcejacquidurpro
DroneScanWarehouse IoTjasperdronescan,scanman,luthuli

7. ADMIN CAPABILITIES

Member Management (mem.2nth.ai)

ActionHow
View all membersAccount → Admin panel — list with name, email, tier, tokens
Change tierInline dropdown — tokens auto-update to tier allocation
Change roleInline dropdown — user / partner / admin
Auto-detect adminsEmails from 2nth.ai, 2nth.io, b2bs.co.za, imbila.ai → auto admin

Partner Hub Access (developers.2nth.ai)

ActionHow
See who has accessCheckbox panel on each group showing all users
Grant accessCheck a user's checkbox → scope updated via API
Revoke accessUncheck → scope updated, toast confirms
Downgrade full-accessUncheck a full-access user → confirmation prompt → converted to specific scopes
View AsDropdown to see the hub exactly as any user sees it
User management/admin/users.html — full table with PINs, scopes, sign-in links

8. PRIVACY & COMPLIANCE

RequirementStatus
Passwordless auth✓ All properties use OTP or magic link
HttpOnly + Secure cookies✓ All properties
Zero tracking✓ No analytics, no third-party scripts
Consent management✓ 6 toggles on mem.2nth.ai (registration, service, updates, marketing, data sharing, analytics)
Data export✓ Per-category JSON/CSV + full ZIP on mem.2nth.ai
Account deletion✓ Email confirmation → 30-day cooling → permanent removal
Terms versioning✓ v1.0 April 2026, timestamped consent records
POPIA Section 22 breach registerPlanned Q2 2026
Data retention purgePlanned Q3 2026
Full compliance framework: See the member management skill review for the complete POPIA/GDPR implementation plan including schema, API endpoints, and phased rollout.

9. ROADMAP

PhaseWhenWhat
Phase 1NowSeparate auth per property, manual partner onboarding, KV storage
Phase 2May 2026mem.2nth.ai reads token balance from 2nth.ai D1 via API
Phase 3May 2026Full SSO — all properties authenticate via 2nth.ai OAuth
Phase 4Q3 2026Self-service partner onboarding, auto-generate hub credentials from mem
Phase 5Q3 20262nth.me token bridge — human skills tokens convert to 2nth.ai project tokens

Last updated: 5 April 2026. This document is maintained on mem.2nth.ai and reflects the current state of the platform.