Agoge Request a pilot

Agoge CourseOps · in pilot with faculty

Your whole course, in one app on your own laptop

A course is a folder of files. Edit it with an assistant, check it, preview it the way D2L will show it, and send it to Brightspace. The graders live in the same place.

Ask to see it running

The CourseOps course screen: work on content, check my course, send to D2L, and eleven more things you can do, from creating a quiz to grading student work.

What you can do

Every step of the term, in one workspace

01Content

  • Work on contentYour course files and an assistant that edits them
  • Build course materialsDatasets, workbooks, starter projects and decks
  • Write a caseA situation, exhibits, and a separate teaching note
  • Test with a readerStudents and colleagues say where they got lost
  • Check my courseAccessibility, old dates, contradictions, facts
  • PreviewSee it the way D2L will show it

02Assignments

  • Create a quizQuestions built from your own materials
  • Build with a guideStep-by-step help for bigger jobs
  • How long this takesStudent workload, counted from your files

03Running the class

  • Grade student workKept separate from the course, never exported
  • Write an announcementIn your voice, every date checked
  • The term, week by weekWhere the work falls, and which week is heavy
  • Send to D2LDownload the import package

A look inside

Real screens from the pilot sandbox

A week-five lesson on joining tables open in CourseOps, with the course files on the left and review and edit-with-AI controls at the top.
Work on content. A lesson is a plain file in your course folder, marked for review until you sign it off.
The create-a-quiz form: question types, how many questions, a difficulty mix and a free-text brief.
Create a quiz. Pick the question types and the difficulty mix, and say what you want in plain words.
The course health panel with checks for accessibility, outdated dates, consistency, and facts and accuracy.
Course health. Catch last term's dates, broken accessibility and contradictions before students do.

How it works

Everything stays on your machine until you publish

The CourseOps iteration loop Four stages inside a dashed boundary labelled your machine: draft, generate, review, publish. A revise arrow runs from review back to draft. Only the Brightspace package crosses the boundary, plus one optional call to the AI assistant you signed in to. YOUR MACHINE The course is a folder of files. Nothing here leaves it. 01 Draft outline, syllabus 02 Generate assignment, rubric, key 03 Review grade a test submission 04 Publish locked D2L package revise, as many times as it takes To the LMS optional: your own AI assistant, on your own account
Everything but the last arrow happens on your machine. The course material leaves only when you publish it, and the one dotted line is the assistant you chose, billed to your own account.
Bring your own AI

It uses the ChatGPT Edu or Plus seat your school already pays for, or your own API key. We sell no AI account.

Much of it needs no AI

Seven of the eight generators make something real with no assistant set up: datasets, decks, workbooks, Power BI and Tableau files.

A folder you already back up

Courses live in your Documents folder, usually synced by OneDrive already. Move machines by copying it.

Room to grow

The same app at three sizes

  1. 1 Local app One instructor, on their own machine Courses shared by zip export and import No IT involvement
  2. 2 Department server A college or department Co-instructors and teaching assistants on shared courses A server and backups
  3. 3 CampusPlanned The whole institution Single sign-on and direct publishing into Brightspace A real deployment

Where it is today: CourseOps is in pilot with faculty, not generally available. The local app is real. It installs from a public container image and updates itself. The campus tier is still design work.