Gurukey — Psychometric platform

Gurukey sells psychometric assessments. A person buys a test, takes it, and receives a scored report with charts. That sentence hides most of the work, because there is no such thing as "a test" here: aptitude, emotional intelligence, MBA readiness, business quotient, personality and a children's assessment each score differently, so each needs its own question bank, its own parameters and its own result model. A separate branded line, Swabodh, has its own form, review flow, referrals and email lifecycle on top.

That produced an administrative surface of roughly twenty-five tabs — one per operational thing the owner actually does — over thirty-four database migrations and seventeen server-side functions. Pricing is read from the server, never accepted from the browser, because a price the client can send is a price the client can choose.

Two pieces of this project are worth telling honestly, because both were problems found rather than features shipped.

The first was a payment-integrity fault caught in a pre-production audit. Fulfilment was running on the browser callback alone, which works right up until somebody pays and closes the tab — at which point their money is taken and their access never arrives, silently. The fix was to move fulfilment to a server-to-server webhook from the payment provider, so the grant happens whether or not the customer's browser is still there. The same review turned up two adjacent faults in that flow: access was being granted after the paid flag was written rather than before, and an idempotency guard was skipping the re-grant on retry.

The second was a database access-control lesson that is now written into the repository so it cannot be forgotten. Revoking a function from the public role does not lock it down on this platform, because execute permission is granted to the anonymous role directly by a separate mechanism. A protective guard written against a guessed function signature had never run at all — a guard on the wrong signature fails silently and looks exactly like protection. The rule adopted afterwards is the useful part: verify against the live database, not by re-reading the code that was supposed to have changed it.

Guest test-taking was built as a first-class path, including resuming an assessment interrupted halfway, which required a parallel identity and payment route rather than a shortcut through the existing one.