“It is engineered. It is not vibe coded.”The sentence this whole program exists so that you can say about your own work, to a client, in an interview, or to yourself at 2am when something breaks and you know exactly where to look.
So ours carries a link instead of a claim. Here is exactly what each one says, at full size.
Issued not for attendance but for evidence. Aarav designed, built and deployed a working tool of their own, published every commit of its source in the open, sat and passed the written examination, and then submitted the running product for review. A named engineer read the code before this credential existed.
Swipe the plate sideways
It names the product, the repository and the human who read it, because those are the only things that make it hard to fake. The evidence block is the design. Remove it and this becomes any certificate from any course platform.
This is not a course certificate and it cannot be bought, audited or completed. It is awarded only on the four core credentials, two electives of the holder's choosing, and a capstone product that is theirs alone. Every one of them required its own deployed product, its own public repository and its own line‑by‑line human review. Seven products of Aarav's own design are running in public, and a practising engineer has read every one of them.
Swipe the plate sideways
The professional certificate inverts the plate deliberately, so the two are never mistaken for each other at a glance. Its value is argued with density, not decoration: every constituent credential enumerated by name and date, and a tally that a course certificate cannot produce.
You submit a live URL and a public repository. What happens next is published in advance, in this order, so nothing about the decision is a mystery.
You complete two peer reviews before your own submission enters the human queue. It surfaces the obvious problems early, and reading someone else's code is the entire subject of course 06.
Five criteria, scored 0 to 4, against a rubric published before you pay. Pass and the certificate is issued with the reviewer's name on it. Fall short and you get written feedback and one free resubmission.
AI may draft a first pass against the rubric for the reviewer to edit. It never sends a review unread. If that ever changes, the promise on the certificate is dead and so is the reason to want one.
If one certified project turns out to be bought or copied, every certificate we have issued is worth nothing. So these are not policies, they are the design.
Every student gets a different constraint on the same project. No two submissions are the same, so nothing can be bought or copied wholesale.
Three tradeoffs, in your own words, and why you chose what you chose. Using AI to build is expected and fine. Not being able to explain your own product is not.
Not a fork. Commit history that is not one dump. Every submission is compared against every previous submission.
A two minute walkthrough recorded by you. It is the one place where the cost of faking it exceeds the cost of doing the work.
There is no subscription, no course access fee and nothing locked behind a paywall to learn. Money changes hands once, and only if you want the work verified.
Second resubmission ₹299. That protects review time without punishing a genuine second attempt.
Start a course free decide about the certificate laterFull refund any time before your first review begins. Once an engineer has started reading your code, that time has been spent and the fee is not refundable. The full terms are on the refund page.
Begin with course 04 free, no accountThe founding batch is thirty seats, and the scarcity is honest. One reviewer has about ten hours a week, which is roughly thirty reviews. That is the schedule, not a marketing device. There is no countdown on this page and there never will be. When the seats are taken the price goes up for the next batch, because capacity is what is actually scarce.
There are no student counts on this page, no testimonials and no logos, because we have not earned any of them. Here is the actual state of things, and it will be updated as it changes.
No. Course 01 assumes nothing, and the whole premise of the program is that AI has moved the wall. What it has not moved is knowing what to build, in what order, and why the output is wrong when it is wrong.
If you already write software, start at 04 and skip everything you already know.
No. Prompting is one course out of nine. The other eight are product sense, data models, deployment, agents, reading code you did not write, security and cost, and getting your first user. That list is the difference between a coder and a product engineer.
No. We are not accredited by anyone and we will never imply that we are. What it carries instead is a live product, open source code and a named engineer who read it.
Whether that is worth more to a particular employer than an unaccredited certificate from a bigger name is a judgement you should make yourself, with the plate in front of you.
No. The fee buys a review, not a result. If the work does not meet the published rubric you get written feedback and a free resubmission, not a certificate.
Yes, and you are expected to. That is the whole point. What you are not allowed to do is fail to explain your own product, which is why DECISIONS.md is mandatory and why the capstone is recorded.
The verify page says so honestly and keeps the repository link. A certificate is a record of what was true on the day it was issued, and it does not pretend otherwise.
Yes, in full, any time before a human starts reading your code. After that the time has been spent and it is not refundable. The complete terms are on the refund page and they say the same thing.
No account, no email, no card. It runs on a phone. Decide about the certificate much later, when you have built something and have a reason to want one.