zorentia.

Zorentia for Years 9–12

Want your secondary school students to learn how apps are built?Let them build their own.

Zorentia guides students from a software problem and real feedback to an evidence-backed product plan or runtime-verified full-stack application. Teachers retain a limited cohort view while each student's private project stays separate.

Book a school demo (opens in a new tab)See how it works

The classroom experience

Different student projects. One view of the class.

Every student can pursue a different idea while following the same project process. Teachers see membership, recent activity and each student's furthest milestone across six coarse stages—not the contents of private projects.

  1. 01Idea
  2. 02Evidence
  3. 03MVP
  4. 04System
  5. 05Build
  6. 06Test
  7. 07Launch
  8. 08Evaluate
ILLUSTRATIVE TEACHER VIEWCOHORT ACTIVITY

Classroom principle

01

Different ideas, one shared process

Every student moves from a product problem and real feedback to an evidence-backed plan or runtime-verified application.

02

One view across the cohort

Teachers see membership, recent activity, coarse milestones and credit usage without opening private student work.

03

Technical depth that fits the class

Choose a planning or application-build pathway to suit the year level, subject and technical depth of the class.

See where attention may be needed.

  1. 01Who has joined or not started
  2. 02Who is active or has become inactive
  3. 03Each student's furthest recorded milestone
  4. 04Recent activity across the cohort
  5. 05Credit usage and remaining allowance
Administrative signals, not student work or grades.

The organisation view shows participation, six coarse milestones and credit usage. It does not automatically expose raw prompts, private ideas, generated code, project artifacts, research observations or quality scores.

Learning with AI

AI supports the build. Students still make the decisions.

AI is changing how software gets built. Zorentia gives students a structured place to use it through a real project: they define the problem, collect evidence, approve scope and architecture, inspect generated outputs, interpret verification results and test the application with real people.

Their big idea stays ambitious. Their first release stays achievable.
  1. 01
    Identify a problem worth solvingEvidence: Product one-pager
  2. 02
    Use feedback to shape the productEvidence: Feedback analysis and feature decision
  3. 03
    Set the first useful releaseEvidence: Downloadable MVP plan and roadmap
  4. 04
    Design how each feature worksEvidence: Approved architecture blueprint
  5. 05
    Verify the application actually runsEvidence: Database, test, health and route checks
  6. 06
    Test the result with real peopleEvidence: Participant observations and synthesis

Choose the technical depth

Two pathways for different classroom goals.

Not every cohort needs to complete the full application-build and launch pathway. Choose the planning or build outcome that fits the year level, subject and assessment plan.

Recommended year level9–10

Product planning

Plan and prove an app idea.

Pathway scope

A structured introduction to software-product thinking, evidence and technical planning without requiring a complete application build.

Students complete
  • Product one-pager and editable pitch deck
  • Public-by-link landing page and feedback
  • Evidence-backed feature decisions
  • Downloadable MVP plan and technical roadmap
Student outcomeA researched software concept with real product artifacts students can explain and defend.
Recommended year level11–12

Application development

Design, build, test and launch an application.

Pathway scope

A deeper pathway from product decisions into per-feature architecture, generated implementation, technical verification, user testing and release.

Students complete
  • Architecture and verified MySQL schema
  • Generated backend, frontend and full-stack package
  • Automated tests and runtime verification
  • Three-participant user testing and guided deployment
Student outcomeA runtime-verified full-stack application package, test evidence, user-research findings and the reasoning behind the build.

School fit and responsibilities

Two things to confirm before your class begins.

First, check that the pathway suits your subject. Then confirm what stays with your school, what Zorentia provides and how students receive access.

01 / Curriculum fit

Does it fit our subject?

These are potential classroom contexts, not claims of formal curriculum endorsement or completed syllabus mapping. Your school confirms fit against its current syllabus and assessment plan.

Australian Curriculum v9.0Digital Technologies · Years 9–10
New South WalesSoftware Engineering · Years 11–12
VictoriaVCE Applied Computing: Software Development
QueenslandDigital Solutions
02 / Responsibility split

Who is responsible for what?

The school retains academic responsibility. Zorentia provides the student workflow, generated outputs and a limited administrative cohort view. Private student work is not automatically exposed to school administrators.

Your school retains

  • Teaching and assessment
  • Student authentication
  • Syllabus interpretation
  • Academic judgement

Zorentia provides

  • Student project workflows
  • Generated planning and build outputs
  • Six-stage activity and milestone visibility
  • Cohort credit-usage visibility

Students receive

  • Institution-provisioned cohort access
  • A private project workspace by default
  • A shared step-by-step project process
  • No individual purchase or payment details

Getting started

From interest to a running class in three steps.

  1. 01You + Zorentia

    Confirm the class

    Choose the year level, subject, cohort size, pathway, project format and delivery dates.

  2. 02Zorentia

    Set up the workspace

    We create the school workspace and teacher access, then your authorised administrator invites eligible students into the managed cohort.

  3. 03Teacher + students

    Run and review

    Students follow the project process while teachers monitor administrative progress signals and remain responsible for teaching and assessment.

Pricing

School plans and pricing.

Choose a shared credit pool for one semester or an agreed school-program term. Eligible students join through institution-provisioned access without purchasing an individual subscription.

School packages compared by intended use, price, shared credits and typical output
PackagePriceShared creditsTypical output
01
Planning ClassroomIdea to technical plan
A$2,000Per semester or term500CreditsApprox. 20 full app plans
02
Build PilotSmall application build
A$4,000Per semester or term1,000CreditsApprox. 5–6 applications
03
Build CohortMid-size application build
A$10,000Per semester or term2,500CreditsApprox. 12–16 applications
04
Full-Class BuildWhole-class application build
A$20,000Per semester or term5,000CreditsApprox. 25–33 applications
Idea to technical plan

Planning Classroom

A$2,000
Shared credits
500
Typical output
Approx. 20 full app plans

Per semester or agreed school-program term

Small application build

Build Pilot

A$4,000
Shared credits
1,000
Typical output
Approx. 5–6 applications

Per semester or agreed school-program term

Mid-size application build

Build Cohort

A$10,000
Shared credits
2,500
Typical output
Approx. 12–16 applications

Per semester or agreed school-program term

Whole-class application build

Full-Class Build

A$20,000
Shared credits
5,000
Typical output
Approx. 25–33 applications

Per semester or agreed school-program term

Before you decide

Frequently asked questions

What year levels is Zorentia designed for?

Zorentia for Schools is designed for Years 9–12 software and digital-project contexts. The Service has a minimum user age of 13.

The depth of the project can be adjusted depending on the year level, subject and cohort.

Do all students need to build a complete application?

No. A planning cohort can finish with a product one-pager, editable pitch deck, public-by-link landing page, feedback analysis and downloadable MVP plan.

A build cohort can continue through architecture, database, backend, frontend, technical verification, user testing and guided deployment.

What does Zorentia verify in the build pathway?

Zorentia executes the generated schema against disposable MySQL, compiles the backend and tests, starts Flask, checks application health and runs the generated pytest suite.

Final assembly boots the full-stack application and requests every generated screen route and frontend asset before creating the downloadable package.

How does student user testing work?

Zorentia generates three research goals and three realistic tasks from the active project. Students moderate sessions with three participants.

They record outcomes, time, paths, blockers, errors, quotations, notes, ratings and frustration before Zorentia synthesises completion rates and common blockers.

Can teachers see student progress?

Teachers and authorised organisation administrators can see membership, access state, recent activity, the furthest recorded milestone, engagement state, credit usage and remaining allowance.

The organisation portal does not automatically expose raw prompts, private project ideas, generated code, private artifacts, research observations or quality grades.

Can students under 18 use Zorentia?

Yes. Zorentia accounts are available from age 13. When a school provisions access, the school is the contracting customer and students do not enter the individual guardian purchase flow.

School use is governed by the current Terms of Use, Young Person Privacy Notice, Institutional Agreement and Institutional Data & Privacy Schedule.

What devices and external accounts do students need?

Students need a computer or laptop to use Build Studio. It is not designed as a phone-based development environment.

Build and launch cohorts may also need school-approved access to GitHub, a local MySQL-compatible environment, AWS, a domain registrar and email.

What should our school know about assessment, privacy and security?

Zorentia produces project artifacts and process evidence that may support student project work, but its progress signals are not grades or competency determinations.

Schools remain responsible for assessment design, authentication, syllabus interpretation and academic judgement.

Schools can review Zorentia's Terms, Privacy Policy, Young Person Privacy Notice, Institutional Agreement, Data & Privacy Schedule and Subprocessor List before purchasing.

A practical next step

See whether Zorentia fits your class.

Review the pathway, teacher view, cohort size, school responsibilities and package options with us before making a decision.

  1. 01Pathway
  2. 02Teacher view
  3. 03Cohort size
  4. 04Responsibilities
  5. 05Package options

Choose a next step

ZORENTIA.
Sydney, Australia
Est. 2025

Zorentia acknowledges the Gadigal People of the Eora Nation, the Traditional Custodians of the land on which we work in Sydney. We pay our respects to Elders past, present, and emerging.

© 2025 Zorentia
Product Studio Pty Ltd

ABN 86 688 343 482

ZORENTIASYDNEY, AUSTRALIAEST. 2025