Loading course details…
Fetching the latest program information for you.
Loading course details…
Fetching the latest program information for you.
Most startup tech stacks are not designed. They accumulate: a microservice split too early, a cloud bill nobody owns, a database that cannot answer next year’s questions, logs that would not survive a CERT-In request. Sixty days to replace accidents with decisions — written down, costed in rupees and built for India.
₹9,999 · one-time · 1-year access
For the person who will be blamed when the system, the bill or the audit fails.
Every architecture call made in a hurry, none written down, and a nagging sense that some of them cannot be undone.
Explicit NFR budgets, a Type 1 / Type 2 decision habit and a repository of ADRs that explains every hard-to-reverse choice.
Over-provisioned databases, forgotten environments and egress nobody modelled — paid in dollars, planned in hope.
A rupee cost model per environment, a waste review with owners, and a scaling path through replicas, caching and capacity plans.
A 300-question security questionnaire, no SOC 2, and a customer asking how you meet RBI outsourcing expectations.
A threat model, encryption map, VAPT scope, certification roadmap and one control map across DPDP, CERT-In, RBI and SEBI.
Unsure whether the team is building the right thing, whether a vendor is a risk, or what an investor’s tech DD will find.
Build-vs-buy TCO in rupees, vendor risk scoring, a board-ready technology budget and a due-diligence data room.
Twelve modules of five lessons each, from architecture and cloud through delivery, data and security to teams, AI and compliance engineering.
Built for founders who need decision-ready tools, not passive reading.
One per lesson, saving your work — architecture readiness scorer, monolith-vs-microservices engine, cloud cost waste analyzer, Kubernetes reality check, VAPT scope planner, build-vs-buy calculator, DPDP readiness check, DORA benchmarker.
The DPDP Act 2023 with the Rules 2025 phase-in, CERT-In’s 2022 Directions, RBI’s 2023 IT governance and outsourcing directions and SEBI’s CSCRF — translated into logs, retention jobs, consent records and controls, with a pointer to the official source.
Worked ₹ examples throughout: the cost of a wrong Type 1 decision, cloud waste, cache hit-ratio savings, the interest on technical debt, build-vs-buy TCO and LLM token spend.
ADRs, NFR budget worksheets, runbooks, incident reports, security questionnaires answers, vendor and due-diligence checklists — markdown you can commit today.
Every lesson says what a five-person seed team should do and what can wait until Series B — no Kubernetes before you need it, no microservices before product-market fit.
Architecture questions arrive in bursts. Come back before a re-platform, a SOC 2 audit, an enterprise deal or a funding round’s technical due diligence.
Real lessons from the course. Each one opens with the decision at stake and ends with something you have built.
Architecture is the set of decisions that are hard to reverse. Your programming language can be changed in a sprint. Your button colours can be changed in an hour. But the decision to split your product into twelve microservices before you have product–market fit, or to store all your user data in a US region in a way that violates the DPDP Act 2023 — these are decisions that take quarters to unwind.
Most startup expenses are decided deliberately: you hire a person, you sign a tool contract, you approve a spend. The cloud bill is different and more dangerous, because it grows on its own, continuously, without anyone deciding anything.
Container orchestration is the automation of exactly these jobs. You declare the desired state and the orchestrator continuously works to make reality match that declaration. Kubernetes is genuinely powerful, genuinely capable, and — this is the part the tutorials underplay — genuinely complex and expensive to operate well.
A phone number verified by OTP proves possession of a SIM at a moment in time. It does not prove identity, and it does not grant permission to anything. Engineers say “auth” and mean four different things — identification, authentication, authorisation and session management — and collapsing them is the root of most identity bugs.
In most startups, “tech debt” describes almost anything an engineer dislikes, so it persuades nobody. Ward Cunningham, who coined the metaphor, used debt to explain why shipping imperfect code can be a good decision. The problem is not borrowing. The problem is the interest — the extra effort every future change costs — which compounds if the loan is never repaid.
Ask an engineer whether to build or buy and you will usually get a build answer within a minute, along with an estimate that is wrong by a factor of three. Ask a finance lead and you will get a buy answer, based on a licence quote and nothing else. Both are reasoning from the number that is easiest to see.
The DPDP Act 2023 received Presidential assent on 11 August 2023. For two years the honest answer to “what exactly must we build?” was “we do not know yet, the Rules are not out.” That excuse expired: the DPDP Rules 2025 were notified on 13/14 November 2025, and they commence in phases.
DORA’s most valuable contribution is not any single threshold; it is a structural claim that contradicts most engineering folklore: throughput and stability move together. That disarms the most common internal argument in an Indian startup — “we can ship fast or ship safely, pick one.”
Eight capabilities the course is built to leave you with.
Why it matters: NFR budgets, a stage-appropriate service design, contract-first APIs and ADRs that explain every hard-to-reverse decision.
Why it matters: Provider and Indian-region choice with residency constraints, infrastructure as code, and a waste review with owners.
Why it matters: A maturity-scored pipeline, lean containers, the right deployment strategy per change, and observability with SLOs.
Why it matters: A defensible database choice, schemas that model money, tenancy and personal data correctly, and a costed scaling path.
Why it matters: Threat model, auth design, encryption map, VAPT scope and a SOC 2 / ISO 27001 roadmap enterprise buyers can review.
Why it matters: Capacity and spike plans, a priced debt register, a hiring plan for the Indian market and an org design for the next stage.
Why it matters: A roadmap, build-vs-buy TCO, vendor risk scores, a due-diligence data room and a board-ready technology budget.
Why it matters: LLM gateways and RAG with evaluation, AI governance, and one control map across DPDP, CERT-In, RBI and SEBI.
Indicative market rates for the work this course teaches you to do in-house. Ranges vary by city, firm and scope — treat them as a comparison, not a quote.
What founders pay for this, piece by piece
Price is inclusive. No GST is charged.
The course is written against the rules in force in 2026: the Digital Personal Data Protection Act 2023 and the DPDP Rules 2025 (notified in November 2025 and phasing in over 18 months), the CERT-In Directions of April 2022, the RBI Master Directions on IT governance (2023), IT outsourcing (2023) and payment system operator cyber resilience (2024), and SEBI's Cybersecurity and Cyber Resilience Framework (2024).
These outcomes are educational and directional, not legal advice. Cloud and AI prices, benchmarks and cost ranges are indicative. Regulatory timelines move — verify the current position on the official source (MeitY, CERT-In, RBI, SEBI) or with qualified counsel before acting.
Sixty days from an accumulated stack to an architecture, cloud, security programme and compliance map you can defend.
1 year access · 60 lessons · 60 interactive tools · 3-day refund