AI course generator for complete, full-length training courses

One request in, a whole course out

Say it plainly, the way you would say it out loud. "I have to learn Rust by Friday" is enough. "Teach me the whole of engineering mathematics, assume nothing" is enough too.

No step asks you to approve a module list before you commit. The runtime you pick is the lever that decides the shape: no module may run longer than 30 minutes, so a longer runtime is split into more modules rather than longer ones, and the deterministic plan for a 30-hour course is 225 modules of 8 minutes.

The chapter titles themselves are decided when the build starts, by a model that reads the whole brief - your own words, every answer you tapped, the track, the level, the runtime, and each file you attached with the line you wrote on it. If that model cannot be reached or answers unusably, the deterministic plan is used instead. Either way the plan lands on the build card in your library, and the event log on that build names which of the two decided it. If particular chapters matter to you, say so in the notes box in your own words.

Three tracks

Every request runs on one of three tracks. Each track has its own default runtime, and you can change it.

• One concept: one idea, taken from first principles to the point where you can use it. Defaults to 10 minutes.
• A whole subject: a subject broken into modules and taught in order, start to finish. Defaults to 60 minutes and scales to 30 hours.
• Your content: a business document, a contract, a deck, a policy, a paper or a spec you hand over, taught back in plain words. Defaults to 15 minutes.

Pitched at your level, in the time you have

Before anything is built, the course fixes what you already know, so nothing you understand gets explained to you again. Beginner assumes nothing. Intermediate assumes the vocabulary and skips the basics. Advanced assumes the formalism, and expert assumes the literature - no recap, no analogies.

Runtime is yours to set, from 30 seconds to 30 hours. Length follows the subject, not a template: a longer runtime is broken into more modules rather than stretching a module to fill time, so a one-hour course and a 30-hour course are built the same way, just at different scale.

What a finished course is designed to contain

The finished course is designed to arrive as one video bundle - every module, downloadable, yours to keep. Each module carries its script, its narration and its worked examples, and a course is built to close on consolidation: recall, and the judgement calls that only make sense once the mechanics are known.

Every finished build gets a watch page of its own. It is private to begin with - you, and the team on your account - and you can open it to people you name by email address, or make it public, in which case anyone holding the link can watch it and only then can it be embedded on another site or posted to a social network.

Pricing is on minutes only: build as many courses as you like, of any length, and only the minutes of finished video count against your monthly allowance. A new account gets 30 free minutes a month, watermarked, no card needed.

Files you hand over

A request can carry reference files, and the Files step is where they go. It is optional - the default answer is no and it costs one tap. The picker offers PNG, JPEG, WebP and GIF images, PDF, plain text and Markdown, and nothing else: there is no DOCX, PPTX or EPUB path, and a file dragged past the picker is refused with the same sentence.

You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it.

Each file has to be under 10 MB, at most 20000 characters are read out of a PDF or a text file, and what you attach is material to work from rather than an instruction that must be obeyed: the pipeline decides whether each one fits the video it is building.

The "Your content" track asks for the document by name, and the name is what travels into the brief: that picker reads nothing and sends no bytes. If the text of the document itself has to reach the build, attach the document at the Files step.

Asking for a change afterwards

A change to a finished video is a NEW BUILD, not an edit inside the file you already have. You type the change in plain words, a confirm strip names the cost before anything is spent - the full runtime of that video in minutes, so a 30-hour course is 1800 minutes again - and the new build appears in your library beside the first one.

Nothing in the product edits inside an existing file, so there is no way to ask for one stretch of a video to change and leave the rest alone. The build you have is kept exactly as it is, with its own event log, and the new one is a build of its own.

Early build: an update request spends real minutes and hands back another sample file, not your rendered course. The video you have now is kept exactly as it is, and we will tell you the day real rendering begins.

What this early build does today

ZUQ is an early build, and the part of it that is live is the part that costs money. A request is saved, minutes really are debited, the build runs and its chapter list is decided - and then it hands back a sample file rather than your rendered video. We will say so on this page the day real rendering begins.