Activation guides — by programme family
Cloud credits: from approval email to first workload
The pattern every cloud programme shares: verify the balance in the console (never trust the email), attach the credit to the right account before anyone creates a second one, set a billing alert on day one, and put a real first workload on it within the week — an idle credit is an expiring credit. The guide walks the console checks, the account-structure traps, and the one sequencing rule that kills applications: some programmes are for new customers only, so the application always precedes the account. Amounts are labelled as reported until a console proves them — that discipline is the course.
AI credits: keys, quotas, and the first real call
API credits die differently: the key is never created, the quota is never raised, or the model route is never wired into anything. This guide takes one AI credit from grant to a working call in your own project — key custody done properly (keys live in a vault, referenced by name, never pasted into chat or code), a cost ceiling set before the first call, and a fallback route so one provider's empty balance never stops the build.
Tool programmes: seats, workspaces, and the second user
Free tiers and startup programmes for tools — email, databases, design, monitoring — pay off only when the team actually moves in. The guide covers claiming the workspace under the right entity, inviting the second user before the trial clock runs out, and the payout-onboarding step that turns a referral programme from a link into income.
First-project tutorials
Ship something on it this week
Each tutorial pairs one programme family with one small, finishable build: a landing page on cloud credits, a working agent call on AI credits, a monitored deploy on tool credits. The artefact is the point — a credit stack you have shipped on is a portfolio; a credit stack you have only collected is a spreadsheet. Tutorials run in the same build-along format as the Academy's courses and reuse the tour's session rhythm: brief, build, demo.
The Expiry-Rescue Clinic
Bring us a dying credit
A standing clinic session, run alongside the tour: bring a credit that is about to lapse, a balance you cannot reach, or an approval you never activated. The clinic works the case in the open — find the balance, prove it in the console, name the blocker (a broken key, a missing account step, a sequencing mistake), and leave with either a working workload or a written account of why the credit is genuinely gone. The network learned this the expensive way: balances have lapsed unspent on our watch, and the clinic exists so yours don't.
The Credits Lab — a monthly working session
One evening a month, the stack gets audited
The monthly session concept: a live audit of the room's credit stacks. New programmes from the latest sweep get filed in the room; expiring balances get rescue plans; one builder demos what last month's credits actually built. The Lab is the community form of the onboarding service — the agent files, the room learns the filing, and next month everyone files one programme smarter. Dates join the tour calendar as sessions are confirmed; nothing is announced before it is real.
Win — win — win
For vendors: we act as DevRel — we learn a tool the way its makers hope someone will, teach it in the open, and put it in builders' hands with a first project attached, so a trial becomes a workload instead of a forgotten tab.
For local companies: we ask what you need from new hires — the roles, the skills, the tools on day one — and train toward exactly that (tell us on the Employer Needs page). A credit spent training toward a real job description is a credit that hired somebody.
Through universities: the channel we are building — the tools and the training reach students where they already are, in the towns the tour serves. No university is named as a partner until it has agreed in writing; until then this is the direction of travel, stated plainly.