B.E. Mechatronics, Robotics & Automation · Agni College of Technology
First exposure to kinematics and physical automation. The spark that ignited my interest in bridging hardware and software.
I'm Vignesh S, founder and chief engineer at Navi3D. We ship production web applications, AI and edge-AI systems, embedded firmware, and physical parts off our own 3D printers and laser cutters. One team, from the first line of code to the finished part in your hand — for clients in Mumbai, across India, and around the world.
Every job added a layer. Two ventures came of it.
First exposure to kinematics and physical automation. The spark that ignited my interest in bridging hardware and software.
First C compiler. First sensor. First time code moved metal — and the only thing I wanted to do after that.
Multi-region apps across the US and India on AWS. Migrated Spring Cloud to Spring Boot microservices — cut AWS spend in half. Learned how the back-end of a real product feels.
Deep dive into machine learning, computer vision, and the maths under PID. Started building robots on the side because pure software stopped being enough.
Built Fynd's Robotics Division from zero. Smart Trolley with YOLO + Raspberry Pi 5 + ARUCO localization. Picked MJF 3D printing over injection molding to ship in days instead of months — that's the day Navi3D started forming in my head.
Robotic arm on a daisy-chained CAN bus at 1 Mbps. ROS 2 + MoveIt 2 with sub-5 ms control loops. Wrote my own ros2_control hardware interface. Closer to the silicon than ever.
Started Artyla in parallel — a venture that runs alongside Navi3D, built on the same engineering DNA. artyla.in →
Home for everything I've learned — 3D printing for early-stage founders, Drone Studio for makers, and large-scale manufacturing on the way. navi3d.in →
I don't just write code. I design the frame, route the PCB, and boot the firmware.
Built a dedicated web-based application allowing users to visually assemble custom drones and dynamically boot or flash the flight controller firmware directly from their browser window.
Launch Drone StudioEngineered an ultra-lightweight micro drone frame. Designed with precise structural ribs to balance rigidity and weight for aggressive flight dynamics, eliminating the need for off-the-shelf chassis.
Custom-designed compact motor driver board tailored specifically for coreless motors on micro drones. Optimized for high-frequency PWM switching and a minimal thermal/weight footprint.
Unfinished Project: Focused on hardware/software bridging. Stopped development at the successful completion of the CAN bus driver layer, establishing communication with ROS over a daisy-chained network.
Developed my own custom G-code generation and slicing software targeted at the Creality CR-10. Built purely out of curiosity to understand the underlying mathematics of converting 3D meshes into machine toolpaths.
Engineered a unified web application and single operational dashboard powering both the Artyla and Navi3D platforms, leveraging SvelteKit for a reactive frontend and Rust for high-performance backend logic.
Today Navi3D designs its own parts, manufactures them, and writes its own software and firmware — all in-house. Here's the road from that to finished products with every part made in India.
Where Navi3D stands right now. We draw the CAD, print the parts and write every line of software ourselves — drone frames, client parts, Drone Studio, flight firmware, and the infrastructure it all runs on.
Our own GPU nodes are being commissioned now — on-premise inference and training for edge-AI workloads, with nothing rented and nothing leaving the building.
We already route the boards. Next we bring fabrication and assembly onto our own floor — power rails, motor drivers and flight-grade traces etched and tested here, not sourced.
Beyond prototyping. Industrial SLS for production-grade nylon parts, CNC for metal, and injection molding for volume — so a design can go from one-off to ten thousand without changing vendors.
The endgame: a drone, a robot, a consumer device — brain, board, body and firmware all designed, manufactured and assembled by us. Finished products out the door, end-to-end in India.
One honest caveat: our PCBs are designed and routed here, but currently fabricated by a trusted manufacturing partner in India. Bringing that line onto our own floor is milestone 03.
Designed, engineered and manufactured in Navi Mumbai. Come build the next one with us.
Artyla and Navi3D are hosted on servers we own in Mumbai, sitting behind Cloudflare. We rent out what we don't use.
Both Artyla and Navi3D run on hardware we own and administer ourselves — not rented capacity in someone else’s region.
Every request passes through Cloudflare first. Firewall, DDoS protection and DNS are governed there before anything reaches our floor.
Our nodes currently sit in Mumbai only, which keeps latency low for Indian users. More regions when demand asks for them.
India-hosted compute for side projects, staging environments and small production workloads. Nodes are deployed in Mumbai only for now. Get in touch and we'll size it with you.
How we work with teams in India and overseas — engagement, IP, stack and time zones.
Yes. We work with founders and teams in the United States, the United Kingdom, the UAE, Europe, Australia and Singapore, as well as across India. Most collaboration is async over email, Slack or your preferred tool, with scheduled calls in your time zone. Payments can be handled in USD.
We are based in Vashi, Navi Mumbai, India, and work with clients in Mumbai, Pune, Bengaluru and across India, plus overseas. Software and AI work is delivered remotely; hardware and 3D-printed parts ship where you need them.
Fixed-scope projects, monthly retainers, or a single prototype — whatever fits. We scope the work, quote it, and give you a clear milestone plan before anything starts, so there are no surprises.
You do. On delivery and final payment, all source code and IP transfer to you. We are happy to sign an NDA before you share anything confidential.
SvelteKit, Rust, Node and MongoDB on the software side; Python, YOLO, Coral Edge TPU and Jetson for AI and computer vision; and C/C++, RTOS and ROS 2 for firmware and robotics.
That is the whole point of Navi3D. The same engineers take a product from web platform to AI layer to firmware to a physical housing — no handoffs between vendors, and a much shorter path to something shipped.
Upload your CAD, or just tell me the problem in plain words. I'll reply within 24 hours.