System architecture
A practical map of device, firmware, connectivity, cloud, application, security, data, and operational responsibilities.
Device to cloud
Connected products fail at the handoffs between electronics, firmware, cloud, applications, and field operations. I have built and operated across every layer.
Best fit
What you leave with
A practical map of device, firmware, connectivity, cloud, application, security, data, and operational responsibilities.
Critical experiments, component and platform decisions, integration milestones, field validation, and manufacturing-readiness risks.
Implementation or leadership across the layers that need intervention, with one decision trail instead of vendor blame.
How the work runs
Review the physical product, firmware, data path, cloud, application, deployment model, and field evidence together.
Test the assumptions that threaten feasibility, reliability, cost, security, or manufacturability before scaling effort.
Bring device, firmware, cloud, and user workflow together in testable increments rather than postponing integration.
Plan diagnostics, updates, support, operations, and handoff for the conditions the product will face outside the lab.
Relevant proof
Connected health at scale
CompletedFounder & CEO, Pulse Active Stations Network · 2016 to 2024
Built a connected network of IoT-enabled health kiosks that delivered more than 600,000 health checks and joined Y Combinator's Winter 2019 batch.
Y Combinator company profileSystems in the field
CompletedFounder, Vajra InfraTech · 2006 to 2024
Built embedded, tracking, monitoring, and workflow systems for logistics, infrastructure, government, and industrial operations.
Professional history and product overviewInstitution building
ActiveCEO, T-Works Foundation (Govt. of Telangana) · Apr 2024 to present
Leading India's largest prototyping centre and manufacturing knowledge partner: a 78,000 sq. ft. open facility built to help people turn ideas into physical products.
T-Works official websiteBefore we talk
Both. The engagement can be a focused architecture review, hands-on ownership of critical layers, or technical leadership across a broader team.
Yes. The goal is to make interfaces, decisions, evidence, and ownership explicit so specialist partners can converge on one product.
The strongest fit is between early feasibility and a repeatable pilot, or when a deployed system has integration and field-reliability problems.
Yes. Remote work covers architecture, software, reviews, and operating cadence; any required physical access or travel is agreed during scoping.
Next step
I will tell you whether I can help, what needs clarifying, and the most responsible first step.