Skip to main content
Platform Architecture

Three Workspaces. One Intelligence Layer.

Skillonize is built on a layered architecture where shared infrastructure powers multiple products. Every workspace inherits platform capabilities — auth, AI, analytics, community — and extends them with product-specific modules.

Proprietary Technology

AHCOS™

Adaptive Human Capability Operating System

The Intelligence Behind Human Growth.

AHCOS™ is Skillonize’s proprietary intelligence layer that continuously understands, measures, and develops human capability across learning, teaching, leadership, and entrepreneurship through adaptive AI, real-world evidence, and lifelong capability growth.

Three Workspaces

Each workspace serves a distinct user and purpose. All share the same intelligence engines and platform core.

Beta

Skillonize Learn

Online learning for students, professionals, and lifelong learners.

  • Courses & Learning Paths
  • Capability Profiling
  • Progress & Certificates
  • AI Coach (Learn)
  • Growth Profile
Open workspace
Coming Soon

Skillonize Educators

Professional tools for teachers, trainers, and curriculum designers.

  • Course Creation Studio
  • AI Lesson Planner
  • Assessment Builder
  • AI Studio
  • Educator Analytics
Coming Soon

Skillonize Startup

End-to-end support for founders building their first venture.

  • Business Model Canvas
  • Customer Discovery
  • Startup Roadmap
  • Investor Preparation
  • Launch Planning

Intelligence Engines

Shared AI and data services that power every workspace. Your context follows you across Learn, Educators, and Startup.

Capability Engine

Maps every activity to the 12 AHCOS capability domains and builds a holistic growth profile per user.

AI Coach Engine

Context-aware coaching powered by the capability profile — personalised to the workspace you are in and the goals you have set.

Analytics Engine

Cross-workspace usage analytics, learning outcome measurement, and predictive intervention signals.

Community Engine

Cohort management, discussion forums, social learning signals, and Early Access program tooling.

Technical Details

Architecture Layers

4 layers — Presentation, Core, Engines, Infrastructure

Presentation

Next.js 15 App Router with Server Components. Each workspace is a route group sharing the platform shell.

App Router (RSC)Route Groups per workspaceShared layouts & navigationServer-side rendering

Platform Core

Shared business logic, hooks, and utilities consumed by all workspaces. Lives in shared monorepo packages.

Auth & session managementOrganisation contextFeature flag systemShared UI components

Intelligence Engines

Capability profiling, AI coaching, analytics, and community — shared across all three workspaces.

Capability EngineAI Coach EngineAnalytics EngineCommunity Engine

Infrastructure

Supabase for auth, database, and storage. Express API server for shared backend logic.

Supabase Auth (JWT)PostgreSQL via SupabaseObject storageExpress API server

Platform Core — Shared Capabilities

8 capabilities shared across all workspaces

Auth & Identity

Supabase Auth — JWT, refresh rotation, SSO-ready

Multi-Tenant Orgs

Role-based access with PostgreSQL Row Level Security

AI Services

Provider-agnostic AI layer — OpenAI, Anthropic, extensible

Learning Engine

Shared curriculum, progress tracking, and assessment

Resource Library

Centralised media, assets, and content management

Payments

Subscription billing and monetisation infrastructure

Analytics

Cross-product usage analytics and growth insights

Community

Discussions, cohorts, and social learning features

Architecture Decisions

6 key decisions with rationale

Next.js App Router

Server Components reduce client bundle size. Nested layouts enable workspace-level shells without re-rendering the platform nav.

pnpm Workspaces Monorepo

Shared packages (db, api-spec, api-client-react) are imported by all workspace apps. Single lockfile ensures dependency consistency.

Supabase as Backend-as-a-Service

Row-level security enforces multi-tenancy at the database layer. Supabase Auth handles JWTs without a custom auth server.

TypeScript Strict Mode

Strict null checks and noImplicitAny catch runtime errors at compile time — critical for a platform with shared APIs and three workspaces.

Tailwind CSS v4 Design Tokens

CSS custom properties as design tokens ensure visual consistency across workspaces without a separate design system library.

Contract-First OpenAPI

OpenAPI spec drives Orval codegen — generating React Query hooks and Zod validators shared by all workspace frontends.

Project Structure

Monorepo layout — artifacts, libs, and API server

artifacts/
└── platform/                     # Next.js App (this app)
    └── src/
        ├── app/                  # App Router routes
        │   ├── learn/            # Skillonize Learn workspace
        │   ├── educators/        # Skillonize Educators workspace
        │   ├── startup/          # Skillonize Startup workspace
        │   ├── early-access/     # Early Access Program (5 routes)
        │   └── platform/         # Architecture overview
        ├── components/
        │   ├── ui/               # Primitive UI components
        │   └── platform/         # Platform shell (nav, footer, logo)
        ├── config/               # Platform & workspace configs
        └── modules/              # Feature modules per workspace

lib/
├── db/                           # Drizzle ORM schema + migrations
├── api-spec/                     # OpenAPI specification (source of truth)
├── api-client-react/             # Generated React Query hooks (Orval)
└── api-zod/                      # Generated Zod validators (Orval)

artifacts/
└── api-server/                   # Express API server (shared backend)