← Documentation · Classroom v1 · Blueprint v2 Documentation · Home v1
Game Track · Home v1 · 20 Sep 2026 · Proposal for Neo & Lan

Its own home, off Neo's estate

Neo's note of 20 September: the program is shared with the Academy team, so it should not run on his personal domain (neotodak.com) or his personal machines (the office fleet, the NAS, the Bandung box). This page proposes a home that Todak Academy and Todak Studios own, names what moves, and prices it. Everything in the student's path lands on Academy or Studios accounts. Neo's fleet may lend a hand in the dry run and nowhere else.

Update, 20 Sep (later the same day). Neo decided the base stays course.neotodak.com. No domain move, no redirects. Everything else on this page, the accounts, the database, the server and the build farm being Todak-owned, still stands as proposed.

Short version
  1. DomainDecided 20 Sep: course.neotodak.com stays as the base. Site, documentation, slides and the showcase live there, as today. The classroom and the collector use paths or subdomains under it.
  2. OwnershipOne rule: every account in the chain belongs to a Todak entity, with Lan and Neo as owners and Kai as IT admin. No personal accounts, no personal tokens, no Siti, no neo-brain.
  3. HostingStatic site and showcase on the Todak Cloudflare account (free). Code in a new todak-academy GitHub organisation (free). Classroom system and course database in a Supabase project inside the Todak organisation, next to the Academy portal's. Collector and publisher desk on the Academy's own server in the Kay rack.
  4. MachinesThe Mac mini becomes an Academy asset, placed at the Academy, reached through a Cloudflare Tunnel on the Todak account, not Neo's private network. No Academy workload on EdgeXpert, tr-home, the NAS or bandung-01.
  5. AI servicesThe two seats do most of the work. Bulk images, 3D and sound go to rented GPU by the hour during class weeks and pay-per-use services through the kit, on Academy accounts with a per-student budget. An Academy GPU box is bought only if a second cohort proves the demand.
  6. CostAlmost nothing new: the hosting is free, the database is the same line as before, GPU rental is a few hundred ringgit per cohort. The one-off is the Mac mini, already approved.
01

Why this matters

02

The new home, piece by piece

What each piece moves to, who owns it, and what it costs. "Exists" means the account or box is already Todak's.

PieceTodayProposed homeOwnerCost
Domaincourse.neotodak.com, classroom.neotodak.comUnchanged: course.neotodak.com stays as the base (Neo, 20 Sep). Showcase at a path under it; classroom and collector as subdomains of neotodak.com.Neo's domain, by his decision.RM0
Site, documentation, showcaseNetlify on Neo's account, repo under Neo's GitHubStays on the current deploy (push = deploy). Recommended still: move the repository into the todak-academy organisation and let the deploy pull from there, so the site's code is company-owned even though the address is Neo's.Address: Neo. Code: todak-academy organisation (proposed).RM0
CodeRepos under Neo's personal GitHubNew GitHub organisation todak-academy: the site, the Game Kit, the classroom system, and one private repository per student game per cohort. Fine-grained tokens for the kit's hands; no personal tokens.Owners Lan + Neo, admin KaiRM0 on the free plan
Classroom system and course databaseSupabase project on a separate personal accountA new Supabase project creator-classroom inside the Todak organisation, the same organisation that already holds the Academy portal's database. Students, progress, prompt logs, review reports, signed paperwork, the project brains.Todak organisationFree tier, then ~RM120/mo
Collector, publisher desk, build queue, store-review watchPlanned on Neo's fleet (EdgeXpert watchers, Kay .213)The Academy's own server in the Kay rack (.213, already keys-only, already the Academy's): small services that receive prompt events, queue publishing manifests and build jobs, and watch the stores. Alerts by e-mail and a WhatsApp group through a plain business API, not Siti.Todak Academy, Kayrule-managedRM0 (exists)
Build farmMac mini at the Kenwingston office on Neo's private networkThe same Mac mini, bought as an Academy asset, placed in the Academy's IT room on wired power and network, reached through a Cloudflare Tunnel on the Todak account (free) with Cloudflare Access in front. Holds the Studios signing keys in a dedicated keychain, because Studios is the publisher. If it must sit at Kenwingston for practical reasons, it still joins nothing of Neo's: its own tunnel, its own accounts.Todak Academy (asset), Todak Studios (keys)One-off, approved
Files: builds, assets, exportsNeo's NASCloudflare R2 bucket on the Todak account, private, signed links for the showcase and the review reports. The Mac mini's 1 TB is the working cache.Todak~RM0–20/mo
Images, 3D, sound in bulkbandung-01 and tr-home (Neo's), EdgeXpert's 3D pipelineThree layers. The seats first (Astra draws, Claude writes). Then rented GPU by the hour on an Academy account during the weeks that need it, running the same open image and 3D tools the fleet runs today. Then pay-per-use services through the kit's asset service, on Academy keys, with the RM50 per-student budget. An Academy GPU workstation only after cohort 1 shows the load.Todak AcademyGPU rental ~RM300–700 per cohort (estimate)
SecretsNeo's credential vaultA team password manager for the Academy (or the Supabase vault of the classroom project), holding the tunnel token, store keys' locations, service tokens. Lan, Neo, Kai.Todak AcademyRM0–40/mo
The kit's AI hands (build, publish, review)Neo's Claude and Codex loginsAn academy-cc service identity on the Mac mini and the Kay server, signed into Academy-owned seats in the Team and Business workspaces from Classroom v1. Its work is logged like a student's.Todak AcademyTwo seats, already in the seat budget
MonitoringNeo's fleet monitors and Siti alertsCloudflare health checks plus an uptime checker on the Kay server. Alerts to a shared inbox and the WhatsApp group.Todak AcademyRM0
Store accountsTodak Studios' Apple, Google Play, itch.io, SteamUnchanged. These are company accounts and Studios is the publisher of record.Todak StudiosRM0

Why Cloudflare and not Netlify. Todak already has the Cloudflare account that holds todak.com and todakstudios.com, so the site, the tunnel to the Mac mini, the file bucket and the access control all sit under one company login with no new vendor. Netlify would need a new team on a company card for the same result.

03

How the pieces reach each other

Student PC or laptopWorkbench pushes code to the todak-academy GitHub organisation. Prompt events go to the collector over HTTPS.
→
Kay .213 · Academy serverCollector, publisher desk, build queue, store watch, uptime. Public address, keys-only SSH, Cloudflare in front.
→
Mac mini · build farmPulls jobs from the queue over its Cloudflare Tunnel, builds every platform, uploads to the stores and to R2, posts the link back.
04

Who can do what

Person or identityRoleHas
Lan (Todak)OwnerEvery account and the domain. Approves at the review gate.
Neo (Todak Studios)OwnerEvery account. Holds the Studios store accounts and signing keys. Bypass at the review gate.
Kai (Academy IT)AdminGitHub organisation, Cloudflare project, Supabase project, the Kay server, the Mac mini. Runs the lab image and the installer.
LecturersStaffClassroom system: their classes, prompt journeys, review reports. No server access.
StudentsMemberTheir own repositories in the organisation, their own seats, their own journey.
academy-cc (the kit's hands)ServiceFine-grained tokens: push to student repositories, read the queue, upload to stores and R2. Nothing else.
05

What moves, in what order

About one week of work once the accounts exist. Nothing on the current pages changes until the new home is live and checked.

  1. Accounts (Lan or Kai, one afternoon): the todak-academy GitHub organisation; the creator-classroom Supabase project in the Todak organisation; the Cloudflare Pages project, tunnel and R2 bucket on the Todak account; the todakcreator.com registration if wanted; the Academy password manager.
  2. Site and docs: nothing to move. Transfer the repository into the organisation and point the existing deploy at it.
  3. Classroom: export the current classroom database, import into creator-classroom, transfer the repository, keep it at classroom.neotodak.com, re-test login and grading.
  4. Kay .213: deploy the collector, the publisher desk, the build queue and the store watch as services; wire alerts.
  5. Mac mini: set up as the Academy asset with the tunnel and the Studios keychain, connect to the queue.
  6. Clean-up: remove the Academy's crons and watchers from Neo's fleet; Neo's fleet keeps nothing of the program.
06

What it changes in the bill

LineClassroom v1 saidHome v1 says
Site, docs, showcase hostingRM0 (Neo's Netlify)RM0 (Todak Cloudflare)
Course databaseRM0 → ~RM120/moSame, in the Todak organisation
FilesRM0 (Neo's NAS)~RM0–20/mo (R2)
Bulk images, 3D, soundRM0 (Neo's GPU boxes)~RM300–700 per cohort, rented by the hour (estimate)
Academy GPU workstationNot neededDeferred; ~RM9k–15k if a second cohort needs it
Secrets, monitoring, tunnelRM0 (Neo's)RM0–40/mo
Mac mini, seats, asset budget, legalUnchanged from Classroom v1

Net effect: a few hundred ringgit per cohort for GPU time, in exchange for a program that the Academy owns end to end.

07

Decisions for Neo & Lan

  1. 1Base address stays course.neotodak.com. Decided 20 Sep
  2. 2Hosting on the Todak Cloudflare account (Pages, Tunnel, R2, Access) and a new todak-academy GitHub organisation. Recommended
  3. 3Classroom system and course database as a new project in the Todak Supabase organisation. Recommended
  4. 4Collector and desk services on the Academy's Kay .213 server, or a new small box on the Todak Hetzner account if Kayrule prefers.
  5. 5Mac mini as an Academy asset at the Academy's IT room, reached by Cloudflare Tunnel. Kenwingston only as a fallback location, and even then on its own tunnel.
  6. 6Bulk generation on rented GPU hours and pay-per-use services for cohort 1; an Academy GPU box deferred. Recommended
  7. 7Who opens the accounts and runs the move: Kai, with Lan as owner. Neo stays owner on everything.
08

Changelog