OpenPTE openpte.com

Can AI replace OpenPTE?

The mechanics of a PTE trainer are not hard: record audio, transcribe it, time the task, score against a rubric, keep a history. An agent can build that in a weekend using Whisper for transcription and an LLM for rubric feedback, and you will genuinely practice more because the loop is yours. What you cannot build is the part people actually pay for: a question bank that tracks what is currently showing up in the real exam, and a scoring model calibrated against Pearson's automated marker so the number you see means something. Your DIY grader will be directionally useful and numerically fictional. Good enough for drilling fluency and essay structure, not good enough to decide whether you are ready to book the test.

Verdict: Half-bot · AI gets you partway; the hard part stays hardBuild time: a weekend
Half-bot

01What it costs

$17.99/moPremium 30-day pass, one-time time-limited access pass
$215.88per year at that price

Checked Aug 18, 2026 · source: openpte.com.

02Could AI build it for you?

The core job: A local web app that runs timed PTE-style tasks, records your speaking or captures your typing, transcribes it, and returns rubric feedback plus a trend chart across attempts.

What a working version needs:

  • Node 20 and a modern browser with mic permission
  • An OpenAI-compatible API key in .env for transcription and rubric scoring, or a local whisper.cpp build
  • Your own question set: prompts, images, and audio you supply as JSON
  • Time to write the rubric prompts per task type, which is most of the actual work

Build it to drill, not to predict; treat your own scores as encouragement rather than evidence.

03What you'd give up

  • Scores calibrated to the real automated marker, so your numbers are vibes, not predictions
  • A question bank that is maintained and rotated as the exam changes
  • Full mock tests with official section timing, weighting and score report layout
  • Model answers, templates and community discussion around each item
  • Mobile apps, cross-device sync, and anyone to blame when the grader is wrong

Because a test taker is not buying software, they are buying a number they can trust before they pay the exam fee. A prep platform's value is the item bank that mirrors what is currently in circulation and a grader tuned so a 79 on the practice test means roughly a 79 on the day. Both of those are accumulated data work, not code. A self-built trainer is great for volume practice and terrible for readiness signals, which is exactly the wrong half to have if you only get one shot at the visa cutoff.

05The build prompt

Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.

prompt.txt
Build a local PTE Academic practice trainer. Empty folder, no accounts, no telemetry, no cloud database.

Stack, non negotiable: Next.js 15 with the App Router, TypeScript, Tailwind, and SQLite via better-sqlite3. Everything runs with `npm run dev` on localhost. Secrets in .env.local only, read `OPENAI_API_KEY` and `OPENAI_BASE_URL`.

Data: a `questions/` folder of JSON files, one per task type, each item having id, type, prompt text, optional imagePath, optional audioPath, timeLimitSeconds, and preparationSeconds. Ship 3 dummy items per type so the app runs before the user adds real content. Do not scrape or invent exam content.

Task types to support: Read Aloud, Repeat Sentence, Describe Image, Retell Lecture (speaking, recorded), plus Summarize Written Text, Write Essay (typed), and Reading Fill in the Blanks (drag or select).

Practice flow: pick a task type, get a random unattempted item, show preparation countdown, then the recording or typing window with a hard timer that auto-submits. Use MediaRecorder for audio, store the webm blob under `data/recordings/`.

Scoring: for speaking, send audio to the Whisper transcription endpoint, then compute words per minute, filled pause count, and for Read Aloud a word level diff against the reference text. For writing, compute word count and run a rubric prompt. In both cases call the chat model with a task specific rubric that returns strict JSON: content, form, fluency, pronunciation or grammar, each 0 to 5, plus two sentences of feedback and three concrete fixes. Store the raw JSON.

Label every score in the UI as "unofficial, uncalibrated" and never render a 10 to 90 style score. This is deliberate.

History: an attempts table plus a dashboard with a per task type trend line, a list of past attempts with playback of the stored audio, and a CSV export.

Out of scope: full mock tests, official score mapping, user accounts, payments, mobile apps, sync, and any bundled question bank.

Deliver a README covering setup, how to add your own items to `questions/`, and a blunt paragraph on why these scores are not predictions.
Sponsor slot · openFeatured alternative to OpenPTE. A labeled card for one relevant tool.
Book this spot →

App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.