Author: Harish Ashok

Harish Ashok

Short Bio

Harish Ashok is a 17-year-old hardware builder from Chennai, India, who has been building robots since he was eight — starting with breaking open toys to see how they worked. He is the founder of Zenith and is currently on a gap year to work on it full-time. Over the years, he has built a disaster relief rover, a GPS tracking beacon, a long-range communication system without cellular infrastructure, and an ethical hacking USB tool, among other projects. During the lockdown, when hardware parts were out of reach, he pivoted to software and ran a web hosting service for local businesses on a Kubernetes cluster of Raspberry Pis — at age 13. Zenith began as a voice-first hardware assistant for the workbench, born from his own frustration with the friction of hardware development. After shipping three prototypes, he identified a deeper bottleneck: the journey from prototype to production. He is now building a micro manufacturing unit to help indie builders and small teams go from prototype to product without needing factory connections or massive capital. He has received grants from Emergent Ventures and the Bagel Fund, and was a fellow at the Localhost hackerhouse in Bangalore.

Extended Bio

Harish Ashok is building the infrastructure for hardware that he wishes had existed when he started. At 17, he has already lived through the full arc of a builder's journey — from childhood tinkering to teenage product development to the hard realization that building one thing is very different from building many things.He started early. At eight, he was breaking open toys to understand their mechanisms, repurposing components into janky RC cars and bottle boats. This is how hardware builders are made — not through courses or curricula, but through the irresistible urge to take things apart and put them back together differently.The lockdown of 2020 presented an unexpected challenge: he could not get hardware parts. Most young builders would have simply stopped. Harish pivoted to software, running a web hosting service for local businesses on a Kubernetes cluster of Raspberry Pis. He was 13. He admits it was overkill, but it was fun — and it taught him that the boundary between hardware and software is artificial. The skills he learned in distributed systems and deployment would later inform how he thinks about hardware infrastructure.When the lockdown ended, he returned to hardware with accumulated momentum. He built a disaster relief rover, a GPS tracking beacon, a long-range communication system that did not rely on cellular networks, and an ethical hacking USB tool. Each project taught him something about what works, what breaks, and what is missing in the hardware ecosystem.The founding insight for Zenith came from a mundane moment of frustration. He was working on a motor late at night, hands covered in grease, and realized he could not touch his laptop without messing it up. Software engineers have Cursor and Copilot — AI tools that integrate into their workflow. Hardware builders have nothing. They are constantly switching between laptops and circuits, uploading code, checking pinouts, googling errors. The process is fragmented, slow, and lonely.He built what he wished he had: a voice-first hardware assistant that sits on a workbench. It could generate circuit diagrams, write and upload code, debug through voice conversations, and document projects automatically. The vision was to make building hardware as frictionless as writing software. He shipped three prototypes and learned a great deal.But deeper engagement with the problem revealed a larger bottleneck. Getting from a working prototype to actual production is brutally hard for indie builders and small teams. Manufacturing infrastructure is designed for scale — for orders of thousands or millions. There is no accessible infrastructure for small-batch production.That is why he is pivoting. He is now building a micro manufacturing unit that allows individuals and small teams to go from prototype to product without factory connections or massive capital. The goal is the same as the voice assistant: reduce friction, remove barriers, make it possible for more people to build real things.He has been supported by grants from Emergent Ventures and the Bagel Fund, and was a fellow at the Localhost hackerhouse in Bangalore — a community that understood his vision when he was still figuring it out himself.He writes for the young builder who feels alone in their garage, the indie hardware founder struggling to cross the prototype-to-production chasm, the investor who wants to understand what hardware needs to thrive, and anyone who believes that the tools we build shape what we can imagine.

Primary Beats

• Hardware Prototyping & Robotics: Building from scratch with accessible components; robotics for real-world applications (disaster relief, communication, navigation); iterative design and learning from failure; the craft of turning an idea into a physical object.
• The Indie Hardware Builder Experience: The unique challenges of building hardware outside institutional settings; the gap between software and hardware tooling; finding community and resources as a young maker in India; the emotional reality of long, lonely builds.
• Micro Manufacturing & Small-Batch Production: Building infrastructure for prototype-to-product transitions; accessible manufacturing for individuals and small teams; rethinking production for the age of the indie builder; reducing capital barriers to hardware creation.
• Voice-Controlled & AI-Assisted Hardware Tools: Voice-first interfaces for the workbench; integrating AI into hardware workflow (circuit generation, code upload, debugging); making hardware development as fluid as software development.