Best Place To BuildSrinath Ravichandran, Co-Founder & CEO, AgniKul Cosmos| "Is Rocket Science Really That Hard?"| Ep.20
CHAPTERS
Why “rocket science” is hard: perfection, not mystery
Srinath reframes rocket science as engineering that’s largely understood today, but brutally unforgiving because every subsystem must work perfectly, every time. He compares launches to exams where anything less than a perfect score is a failure, and briefly references AgniKul’s own scrubbed attempt to illustrate the point.
- •Rocket science isn’t hard because concepts are unknown; it’s hard because there’s no tolerance for error
- •Modern compute and communication have reduced many historical barriers
- •Reliability and integration—getting “everything right”—is the core difficulty
- •Even a non-explosive failure (like a scrub) is still a mission failure
AgniKul’s mission: rockets built for today’s small-satellite era
AgniKul positions itself as a dedicated transportation provider for small satellites, built around the new realities of LEO and large constellations. Srinath explains how satellites have become smaller, closer to Earth, and far more numerous—while traditional launch systems still reflect older GEO-era assumptions.
- •AgniKul targets ~300–350 kg payloads depending on orbit and launch conditions
- •Shift from GEO (~36,000 km) to LEO (~360–500 km) changed satellite design and economics
- •Satellite mass shrank from multi-ton to tens/hundreds of kg; constellations grew to thousands
- •Launch systems haven’t evolved at the same pace as satellite electronics
LEO vs GEO basics: latency, speed, and why constellations exist
The conversation dives into orbit fundamentals, including why GEO feels “stationary” while LEO satellites move rapidly and offer short ground passes. This sets up why operators deploy many satellites for continuous coverage, like Starlink-style networks.
- •GEO is synchronized with Earth’s rotation; LEO is much closer but moves fast
- •ISS/LEO orbital period is ~90 minutes (~15–16 orbits/day)
- •LEO passes can be just a few minutes per satellite, driving multi-satellite relay networks
- •LEO is ‘close’ in distance terms, but operationally distinct due to high relative speed
Rideshare launches and collision avoidance in orbit
Srinath explains rideshare economics on large rockets and addresses the practical concern of releasing many payloads into similar orbits. He outlines how separation maneuvers and ongoing station-keeping reduce collision risk, noting satellites will drift into riskier trajectories if left unmanaged.
- •Rideshare makes large rockets economically viable by distributing costs across payloads
- •Satellites are deployed with maneuvers and spacing to avoid immediate conflicts
- •Perturbations (e.g., gravitational effects) can change orbits over time
- •Station-keeping is continuous, subtle course correction to prevent collision paths
From government programs to startup space: SpaceX’s ecosystem shockwave
The discussion shifts to industry structure and how SpaceX changed perceptions of launch as a business. Srinath highlights commoditization via pricing metrics (like $/kg), faster development cycles, and the narrative shift that drew in more entrants and new applications.
- •SpaceX popularized transparent, comparable metrics (notably dollars per kg)
- •Narrative shift: space became a scalable commercial service, not just a government program
- •Shorter cycles (months/years vs decade-long programs) attracted talent and capital
- •“Space-grade” pricing and procurement habits were challenged by a startup mindset
What rockets actually do: speed, orbit, and the ‘first 10 km’ problem
Srinath breaks down orbit insertion as achieving ~7 km/s horizontal velocity so the payload ‘falls around Earth.’ He emphasizes that the toughest part of launch is fighting dense atmosphere early on, then describes key milestones that audiences celebrate during launches.
- •Reaching orbit is about speed and trajectory, not simply altitude
- •The earliest atmospheric segment is hardest; space itself is comparatively clean physics
- •Max-Q is a major vulnerability point due to high dynamic pressure
- •Typical “applause moments”: liftoff, Max-Q, stage events, payload deployment (plus landing for reusable systems)
India’s policy inflection: post-COVID opening and IN-SPACe
Srinath outlines how India historically involved private industry mainly as ISRO vendors, limiting commercial scaling. He describes the 2020 policy shift, creation of IN-SPACe, and how private launches, launchpads, and independent satellite missions became feasible—an unexpected but transformative change for startups like AgniKul.
- •Pre-2020: private players largely sold to ISRO for government missions
- •2020 Atmanirbhar announcements signaled major opening of the sector
- •IN-SPACe created to authorize and enable private space missions
- •Policy clarity unlocked broader commercial participation and investor confidence
Why ISRO succeeded: passion, constraint-driven innovation, and governance
The host asks what made ISRO unusually successful among public institutions. Srinath attributes it to mission-driven talent, operating under tight budgets that forced innovation, and governance that reduced bureaucratic friction through direct top-level oversight.
- •Space attracts intrinsically motivated talent more than many sectors
- •Chronic budget constraints pushed creative, cost-effective engineering
- •Operational decisions benefited from clearer governance under the PM’s portfolio
- •National pride plays a role, though differently than in defense
Engineering for small-rocket economics: the ‘cost-per-thrust’ mindset
Before listing AgniKul’s “firsts,” Srinath explains the core challenge: small rockets struggle economically because most optimizations historically targeted large vehicles. AgniKul’s approach is to find technologies that make performance and cost work at smaller scale, beyond labor-cost advantages of being in India.
- •Small rockets are constrained more by economics than basic engineering feasibility
- •Scaling down large-rocket methods can make unit economics worse
- •AgniKul optimizes for cost with new tech, not just lower local costs
- •ISRO’s low-cost achievements are framed as innovation-driven, not geography-driven
Single-piece 3D-printed rocket engine: design, iteration, and powder removal
Srinath details AgniKul’s 3D-printed engine approach: a one-piece metal engine built through additive manufacturing with extensive iteration. He explains why eliminating joints/welds reduces human assembly burden, and highlights a non-obvious challenge—designing internal channels so trapped powder can be removed through existing ports.
- •One-piece printing removes assembly steps and reduces failure points like joints and welds
- •Additive manufacturing enables internal geometries impossible with subtractive methods
- •Metal printing requires careful material science and post-processing (e.g., heat treatment)
- •A major challenge: ensuring internal powder can escape through functional openings
- •Development involved many iterations (dozens) to converge on manufacturable geometry
Rocket avionics reimagined: ‘OS + apps’ and modular plug-and-play components
AgniKul’s software stack is presented as a platform: a Linux-based real-time operating system with modular applications for engine control, navigation, throttling, telemetry, and more. Srinath describes an electronics-first philosophy where the flight computer is central and hardware behaves like peripherals, enabling upgrades and modular vehicle variants.
- •Linux-based real-time OS runs onboard; functions are modular ‘apps’ rather than monolithic code
- •Flight computer is treated as the core system; engines and subsystems are peripherals
- •Modularity supports versioning, upgrades, and reconfiguration with less integration risk
- •This software-centric architecture supports a plug-and-play rocket build philosophy
Ethernet inside a rocket: lightweight high-speed networking for avionics
Srinath explains why AgniKul uses Ethernet to connect onboard computers and subsystems, emphasizing bandwidth, maturity of the protocol, and reduced wiring mass—critical for small-rocket economics. He frames the rocket as a flying network where communication is simplified by leveraging established standards.
- •Ethernet offers high data rates with minimal wiring mass and well-understood tooling
- •Reduced cable bulk supports payload fraction and cost targets for small launchers
- •Standard protocols can outperform bespoke aerospace wiring for certain architectures
- •The approach strengthens the modular ‘peripherals to a computer’ design philosophy
Mobile launchpad and ‘launch anywhere’: latitude-driven pricing and customer choice
AgniKul’s mobile launchpad—built and qualified at IIT Madras, then moved to Sriharikota—is discussed as both a technical and commercial differentiator. Srinath explains how latitude affects achievable orbits and fuel needs, and how AgniKul plans to present customers with location-cost tradeoffs instead of requiring heavy fixed infrastructure investments.
- •Mobile launchpad enables deployment without building massive permanent facilities
- •Latitude can swing launch economics significantly (order ~40% impact, per Srinath)
- •Earth’s rotation helps equatorial launches for certain inclinations and hurts for others
- •AgniKul aims to give customers a cost table by location/orbit to choose best fit
Building AgniKul: team composition, mentorship, and persistence through scrubs
Srinath describes a young team augmented by retired ISRO expertise to blend fresh thinking with hard-earned lessons. He recounts cold outreach to find testing facilities, Professor Sathya Chakravarthy’s pivotal support, and the emotional/operational burden of repeated countdown aborts and the investigations that follow each scrub.
- •Average team age ~26–27; experience gap filled via retired ISRO veterans
- •Mentorship from Prof. Sathya and leaders like Perumal (GSLV) shaped capability and credibility
- •Early growth came from interns/students evolving into full-time staff as funding arrived
- •Countdowns synchronize teams but amplify anxiety; repeated scrubs create heavy review cycles
- •Persistence—continuing after many rejections—was central to getting started
Founder’s path: ABB checklists, Wall Street shortcuts, film school storytelling, and fatherhood
The closing section traces Srinath’s unconventional route: electrical engineering, ABB field discipline, six years in Wall Street finance, and a detour into film school and pilot training that later influenced decision-making and communication. He shares a “sailing” metaphor about luck and preparedness, and ends with the realities of balancing CEO responsibilities with parenting through support systems and shared hobbies.
- •ABB and pilot training reinforced disciplined checklists and decisive execution
- •Wall Street instilled quantitative shortcuts and first-order thinking under time pressure
- •Film school improved storytelling, audience engagement, and communication with investors/teams
- •Luck matters, but you must ‘put up the sails’ to capture opportunity (policy shift example)
- •Balancing family and startup life depends heavily on support systems and intentional time
