Loading
Loading
A mock exam that loses a student's answers at minute 90, or a course directory nobody can filter, destroys trust immediately. We have shipped a high-concurrency computer-based test platform and a student consultancy portal — this page is built on what that reliability bar actually requires.
Real-time auto-saving, precise timing, and zero data loss during a multi-hour exam — the exact reliability bar a mock IELTS or admission test cannot miss.
Objective sections (reading, listening, multiple choice) scored automatically against a rubric, freeing instructor time for the sections that genuinely need human judgment.
Structured, filterable catalogs of courses, universities, or programs — searchable by country, subject, and cost, not a static PDF list nobody can filter.
Built and load-tested for real simultaneous use — hundreds of students sitting a mock exam at the same scheduled time, not staggered logins.
Proof, not just claims
How we work
Typical timeline: 6–10 weeks for a course/consultancy directory, 3–5 months for a full computer-based testing engine. The date we commit to depends as much on how fast feedback and content come back as on how fast we build — we will be straight with you about that in scoping.
We ask what your business actually does and where the work is going wrong — before talking about software. If what you need is smaller than what you asked for, this is where we say so. No charge, no obligation.
You get the scope in writing, with a fixed price where the requirements are clear, before any work starts. If something is genuinely unknowable up front, we say that too rather than burying it in an estimate that moves later.
Work ships in agreed stages, and at each one you get something working to click through — not a status update. That means you catch a misunderstanding in week two, when it is cheap, instead of at handover.
Code, hosting, domain, and accounts go in your name. We train your team on the real system with your real data. You are never locked in — if you leave, everything is already yours.
Launch is when the real bugs appear. An agreed post-launch fix period is included in every project. After that, maintenance is a separate retainer with published pricing — not a surprise invoice.
Common questions
Yes — real-time auto-saving, precise timing, and zero data loss during multi-hour exams is exactly what we built for Bandly BD's IELTS mock testing platform, load-tested for 500+ concurrent test-takers.
A course or consultancy directory typically starts at 1,00,000 tk. A full computer-based testing engine with automated scoring and high-concurrency reliability is quoted after a scope discussion, given the load-testing and architecture involved.
Objective sections (reading, listening, multiple choice) can be scored automatically against a rubric. Subjective sections (writing, speaking) still need human evaluation — we do not claim to automate judgment that genuinely requires it.
Depends on scope and infrastructure — our Bandly BD build handles 500+ concurrent test-takers at 99.9% uptime. We load-test against your actual expected concurrent count before launch, not after.
Launch includes an agreed period of post-launch fixes. After that we offer maintenance retainers for updates, monitoring, and small changes so the system stays secure and current.
An EdTech platform is one type of web application. These are the closest alternatives.
The wider practice this sits under, including the stack reasoning behind high-concurrency builds.
View serviceFor a course marketing site without exam infrastructure — often the simpler, cheaper first step.
View serviceFor student consultancy lead tracking alongside the course or exam platform itself.
View serviceTell us your expected concurrent user count and exam or course format. We'll tell you honestly what reliability bar that actually requires.
START A CONVERSATION