SOQ International Academy

IT Architecture

it_architecture screenshot

Live screenshot from the SOQ beauty demo (aiacademy.aiee.dev).

A plain-language map of how SOQ International Academy (soq.edu.sg) fits together — for operators, partners, and business readers. No deep server setup here; that lives under Tech Stack and Hosting.

The four architectures (how the business runs)

Everything on the platform is one of these four. Read left to right: Core is always there; Modules add power; Organizations join SOQ; Resale is when a customer runs their own academy site.

SOQ four architectures — Core, Modules, Organizations, Resale SOQ International Academy — one platform, four architectures 1 — CORE The academy base Courses & learning Checkout & payments Live classes (Zoom) Admin & user roles Email & settings Always on for an activated academy 2 — MODULES Optional add-ons Modules Bundle (59) Theme “ Mobile ” AI SG features (9) Quizzes “ Store ” Orgs… Unlocked by activation Otherwise shows Feature not activated 3 — ORGANIZATIONS Mode A — join SOQ Company / partner orgs Use soq.edu.sg Own staff & learners Package ? Full SOQ SOQ stays superior No separate website to install 4 — RESALE Mode B — own TMS Customer's own domain Gets Core + modules SOQ issues the activation Pick-list of modules Provisioned by SOQ Their Admin — their site (not Super Admin) How they work together SOQ Full site soq.edu.sg = Core + all Activations unlock Modules when needed Orgs join SOQ Mode A on same site Or buy own TMS Mode B — SOQ provisions it
1 Core — base academy 2 Modules — enabled extras 3 Organizations — join soq.edu.sg 4 Resale — customer's own academy site

In one sentence each

ArchitectureBusiness meaningWho cares
Core The academy that always works: find courses, learn, pay, teach, administer. Everyone
Modules Extra capabilities (quizzes pack, store, mobile, AI, Singapore tools — ) turned on with a SOQ activation. Admins “ product ” partners
Organizations Companies or training partners run on SOQ's website with their own people and package — they do not install a separate system. Org owners — SOQ ops
Resale A customer buys their own academy on their domain; SOQ provisions Core + chosen modules based on rollout scope. SOQ sales — Mode B customers

Who uses what (same platform)

Four main audiences. Each opens a different door into the same SOQ system.

Who uses SOQ Students Browse & enrol Learn — quizzes* Certificates Public site + Panel Instructors Create courses Live classes Meetings* Instructor Panel Organizations Manage members Org courses* Package limits Org Panel (Mode A) Admins / Staff Run the academy Manage feature activation Payments — support Admin console * Items marked with an asterisk may need a Modules activation before they appear. Sidebar badges: Core = always available — Modules = Feature not activated until enabled.

Simple system picture (what the IT looks like)

High level only — enough for a business walkthrough. Engineers use Tech Stack and Hosting for versions and sizing.

Simple SOQ system picture People & devices Students “ Instructors ” Organizations “ Admins ” optional Mobile app Secure website soq.edu.sg (or customer domain for Resale) “ HTTPS ” public pages Academy platform (one application) Core + optional Modules “ Public ” Panel — Admin Organizations (Mode A) and Resale (Mode B) reuse this same product shape Records & files Database “ uploads ” media storage Outside partners Email “ payments ” Zoom “ Google ” SG tools*
One application — Core and Modules share the same site * Partners — configured in Admin / Access guide when needed

Modules in business language

PackWhat it gives youGuide
Modules Bundle 59 extras (quizzes, store, forums, meetings, org tools, and more) Module Bundle
Theme Builder Landing pages and themes Themes & Landing
Mobile App Mobile app / API access Mobile API
AI Contents AI-assisted content drafting AI Content
Singapore & regulatory 9 deferred PEI / grants / identity / finance Core features Singapore & Regulatory

Full inventory by audience: Core vs Modules. Activation guide: Feature Activation.

Do we still need anything else on this page?

For an end-user / business guide — this page is complete when it covers the four architectures, who uses the system, a simple system picture, and where modules fit. That is what you have above.

TopicOn this page?Where it lives instead
Core “ Modules ” Organizations — Resale Yes — lead diagram —
Who uses Public / Panel / Admin Yes Also sidebar audiences
Module packs (59 + Theme/Mobile/AI + SG) Yes — summary Detail: Core vs Modules / Module Bundle / SG hub
Simple website ? platform ? data ? partners Yes —
PHP, Redis, cron, CPU sizing No (by design) Tech Stack — Hosting
How to enter SMTP / Zoom / payment keys No (by design) Access guide
Super Admin entitlement app (Mode B keys) Mentioned as Resale flow only Internal entitlement docs — not needed for most operators
Step-by-step install / update No Installation — How to Update

Verdict: Nothing else is required on this page for a non-technical architecture overview. Add a new page only if you want a dedicated “Mode A vs Mode B sales” pitch or a deep Super Admin runbook — those are not end-user guide material.