Asked and answered.

KodeStep is a code practice platform built for schools. Teachers create classes and assign coding challenges; students solve them in a browser-based editor with practice runs against visible tests; every submission is graded against the full test suite on an isolated server; and teachers review results, leave feedback, and export a gradebook.

HTML, CSS, JavaScript, TypeScript, Python and Java. HTML, CSS and JavaScript practice runs happen instantly in the browser; TypeScript, Python and Java practice runs go to the server. Every graded submission, in every language, runs on the server. React, Next.js and C++ are not supported at launch.

No. KodeStep runs in the browser: editor, practice runs and live preview included. It is designed for school Chromebooks and works on phones down to 360px wide, with a special-character toolbar on small screens.

Not yet. LTI 1.3 with Schoology, including grade passback, is planned but not available today. KodeStep works standalone: students join with a code, a class link, an email invite or a CSV roster import, and teachers can export a gradebook CSV.

Yes. Teachers can author challenges with their own tests, starter code, design references, working assets and example solutions, private to their school. Test My Challenge runs the example solution in both the browser and the grading server, and a publish checklist has to pass before students can see the challenge.

Yes. The curated library has 149 challenges across six languages, and 30 starter packs group them into sequences, including a Java AP CSA exam-prep pack. Importing a pack gives your school its own copies plus draft assignments; you set the due dates.

Practice runs check code against the visible tests, so students can iterate before submitting. When a student submits, the full test suite runs on a separate, isolated server: visible tests, tests hidden until submit, and secret tests that show students only a pass or fail. A full pass marks the work passed automatically; teachers can review, leave feedback and request a revision.

With signals for the teacher, not accusations. Paste detection records large pastes and shows them as context, not proof. Hidden and secret tests make hard-coded answers easy to catch. Every submission is timestamped by the server, and resubmission rules are set per assignment.

No. AI never grades, scores, passes or fails a student. KodeStep has an optional AI review summary that drafts strengths and suggestions for a teacher on visual HTML and CSS challenges, only when the teacher asks. It is switched off today and stays off until our AI provider confirms zero data retention in writing; after that, each school decides whether to turn it on, and staff can exclude individual students.

It is designed for them. The editor was chosen for low-end devices and loads only when needed, HTML, CSS and JavaScript practice runs need no network round trip, and auto-save retries on its own when the connection drops, with a status that never claims work is saved when it isn't.

It is built to a WCAG 2.1 AA target: semantic HTML, full keyboard access including a clear way out of the code editor, screen-reader support, and automated accessibility checks in the test suite.

A seat is an active student in your school. Teachers, assistant teachers and school admins never use a seat, and students who have left don't count.

Each school gets a per-seat quote based on its student count, so we don't publish a price list. Email us your approximate number of students and we'll send a quote.

Yes. Pilot schools run the full platform with real classes and pay nothing. A signed Data Privacy Agreement comes first, before any student joins.

By invoice. We send a formal quote, and an accepted quote becomes an invoice. There is no self-serve checkout.

Your school goes read-only: teachers and students can still view and export their work. That window lasts 30 days by default. The school's data then leaves the platform, and is removed from the live database after a further grace period, also 30 days by default. Both windows are set per school. Copies inside encrypted backups already taken sit outside that deletion and expire on their own, the last within 1 year.

KodeStep is designed with FERPA in mind: data is used only for the school's educational purposes, collection is kept to a minimum, and deletion follows a documented schedule. We don't claim a certification. Our privacy policy and standard data agreement will be published before launch.

Through the school-consent model that is standard in education technology: the school consents as the parent's agent, under the school's signed data agreement. KodeStep collects only what the educational service needs.

No. Student data is never sold, never used for advertising, and never used for anything beyond the educational service. There are no ads and no third-party analytics or tracking inside the app.

No. Student work is used only to run the service. The optional AI review is off today; when a school turns it on, code comments are removed, no name, email or account ID is sent, and it runs only after zero data retention is confirmed in writing.

Practice runs for HTML, CSS and JavaScript run in the student's browser, inside an isolated sandbox: an opaque-origin frame on its own subdomain that cannot read any cookies. Graded submissions run on a separate, firewalled server with no access to student records, the database or platform credentials, in a fresh sandbox with networking disabled.

Yes. Students can download their own completed work while they can still sign in, teachers can export a class gradebook as CSV, and school admins can export the school's data. A student who loses access to a school-issued email account can't export on their own, so it's worth downloading before leaving.