EduGaa
Education
An AI study platform, taken from an unregistered domain to a live product
EduGaa turns whatever a learner already has, a PDF, a deck, a photo of a whiteboard, into notes, flashcards, and practice built around how that person studies. We delivered the whole thing: the domain, the infrastructure, the backend, the interface, the AI pipeline behind it, and the security and policy work needed to put it in front of the public.
edugaa.comEnd to end
Domain purchase through to running it in production
5
Upload formats accepted: PDF, slides, images, links, text
6
Study activities generated from a single upload
3
Plans live: free, pro, and institutional
The challenge
The idea was clear and nothing else was. There was no domain, no hosting, no accounts, no schema, no interface, and no answer to the hard part: how you take a file a learner uploads, in whatever shape it arrives, and reliably turn it into study material that is actually correct. The founding side of the project was subject-matter deep and deliberately not technical, which meant we were not being asked to fill gaps in an engineering team. We were being asked to be the engineering team, and to make the technology decisions that a founder should not have to make alone.
What we did
We ran it as one engagement rather than a chain of vendors, because the seams between vendors are where projects of this shape usually fail. That meant buying the domain and standing up DNS and mail on day one, choosing an architecture that a small team could still afford to run at zero users and would not have to abandon at ten thousand, and building the ingestion and generation pipeline as the first real piece of software rather than the last. Each study format, notes, flashcards, multiple choice, fill-in-the-blanks, true or false, and the mixed set, was treated as its own generation problem with its own checks, so a weak result in one format could be fixed without disturbing the others. The learner-facing product was built on top of that, then the account, plan, and billing layer, then the tutor. Security and the published policies were part of the build rather than a pre-launch scramble.
The result
EduGaa is live at edugaa.com, open to the public, and running on infrastructure we set up and continue to support. A learner uploads a PDF, slides, an image, a link, or pasted text, chooses the activities and the difficulty, and works through a four-star mastery loop that banks points and tracks streaks. Free, Pro, and institutional plans are in place, the AI tutor answers alongside the material, and the privacy, terms, cookie, and AI policies are published. The client owns the domain, the repositories, the cloud accounts, and the code.
Every piece of it, stage by stage.
- 01
Domain and foundations
Registering edugaa.com, configuring DNS, setting up business email and the shared accounts the project would need, and separating development, staging, and production before there was anything to deploy into them. Unglamorous, and the reason nothing later had to be unpicked.
- 02
Discovery and scoping
Turning the idea into a build order: what a first release had to contain to be worth using, what could wait, and which of the study formats had to work before any of them were worth shipping. The output was a costed roadmap, not a proposal.
- 03
Architecture and infrastructure
Cloud hosting, the database, file storage for uploads, background processing for the generation work, and the deployment pipeline. Chosen to cost almost nothing while the product was small, and to hold when it was not.
- 04
Backend and data model
The API, the schema behind modules, activities, attempts, points, and streaks, and the accounts and authentication under all of it. The mastery system is the spine of the product, so it was modelled properly rather than bolted on once the screens existed.
- 05
AI generation pipeline
The part that makes EduGaa what it is: reading an upload in any of five formats, extracting the substance from it, and generating each study activity to the difficulty, length, and question count the learner asked for. Built with per-format validation, so bad output is caught before a learner sees it rather than after.
- 06
Front end and product design
The upload flow, the activity screens, the progress dashboard with its charts and streaks, and the four-star mastery loop, built to stay legible on a phone, because a good share of studying happens on one.
- 07
Tutor, plans, and billing
The EduGaa tutor answering against the learner's own material, and the Free, Pro, and institutional tiers with the subscription billing, entitlements, and upgrade paths behind them.
- 08
Security and policy
Authentication hardening, transport and storage security, sensible platform headers, and the published privacy, terms, cookie, and AI policies. Learner-uploaded material and AI generation both carry obligations, and they were handled during the build rather than the week before launch.
- 09
Launch, handover, and run
Going live, then staying: monitoring, patching, and incremental feature work, with the domain, repositories, and cloud accounts in the client's own name from the first day.
Scope of the engagement
- Domain and DNS
- Cloud infrastructure
- Backend and database
- Front end
- AI generation pipeline
- AI tutor
- Billing and plans
- Security and policy
- Launch and run
Wherever you’re starting from, let’s figure out the next step.
Tell us what you’re building. We’ll tell you honestly whether we’re the right team for it.