Everybody has read about agents. Far fewer have one running. Eight hours, a practitioner in the room, your own machine, everything you need to get yours running.
One agentic AI subject, one day, taught by the same people who run our certificate programmes.
One subject for a whole day. Long enough to get past the demo and into the parts that break in real use.
Live from start to finish, with the instructors who teach our certificate programmes. Nothing recorded, nobody junior.
You are building inside the first hour, on your own machine, and you keep building for the rest of the day.
Bring your repository, your backlog or the process you are stuck with. The exercises run on that, not on a sample project.
Code, documents, prompt libraries and checklists leave with you, with the notes to redo them at work.
Each day comes out of a certificate programme, so if you continue, you carry on rather than repeat it.
Four dates are open, each one running once, each with limited seats. Book the one closest to what you need running.
One day building knowledge systems that hold up in production — five blocks, and three codebases you take home.
One day building agents that run on their own — a support agent, tiered memory, and a multi-agent research system you keep.
Every day is led by someone who builds and runs agentic systems for a living.
Every bootcamp day is one part of a certificate programme, taught by the same instructors and built to the same four rules.
Build production-grade AI systems in TypeScript — LLM integration, RAG pipelines, agents, and a capstone you deploy and keep.
Learn More →Design systems that survive production — hybrid retrieval, knowledge graphs, multimodal pipelines, and agents that coordinate.
Learn More →Both engineering tracks as one path — from TypeScript fundamentals through to autonomous systems, with two capstones.
Learn More →21 hours building production multi-agent systems — anatomy, orchestration, guardrails, and a launch review.
Learn More →The full product path — discovery, prioritisation, roadmapping, and scaling a product organisation.
Learn More →Bridge product and engineering on AI features — from the PRD through the metrics to the ethics.
Learn More →21 hours redesigning how a team works — specs, documents, meetings, and a workflow proposal with its impact estimate.
Learn More →Strategy, workforce design, and the economics of an AI-native organisation — for the people who set direction.
Learn More →21 hours governing AI across the development lifecycle — policy, oversight, licensing risk, and a rollout plan.
Learn More →We pick what you walk out holding, then cut everything that does not get you there. Most of a normal agenda dies at that step.
The day runs in blocks. Every block ends with something working, and the next one starts from what the last one produced.
Cost, latency, what fails in production and the guardrail that catches it. Covered while the build is still open, not in the last half hour.
Nothing runs in a sandbox you lose at the door. You build in what you already use, and it still works on Monday.
Eight hours, in short teaching passes followed by long stretches of building. You finish with something that runs and the notes to rebuild it.
Anyone. Most seats go to individuals paying for their own day, and companies book two or three at a time the same way.
For the engineering days, yes, in any language. The product, workflow and leadership days need none.
The work you built during the day, the prompts, checklists and slides, and a certification for the day itself.
Yes. Any day runs privately for one company, with your own systems as the examples, on a date agreed with you.
Tell us the gap. The listed days are the ones we run most often, and the rest are built from the same programmes.
Any bootcamp here can run for your team only — your codebase, your agents, your date.
