Who's building
One person, both sides of the software-to-silicon line. I'm Karthik, a solo builder in Bangalore. I run Hivelinks Technologies, design and install smart homes, and spend my off hours flashing firmware onto things that have no business being connected. Firmware, hardware, backend, dashboard: one pair of hands across the whole stack.
400+ Companies run from one seat
100+ Deployments shipped
5+ yrs Longest system running
24/7 Field uptime monitored Available for projects Builder · Maker ● ESP32 FIRMWARE● LoRa LINKS● MQTT● HOME ASSISTANT● Zigbee2MQTT● Node.js● React● PostgreSQL● Docker● SELF-HOSTING● Modbus / RS-485● TIME-SERIES TELEMETRY● PCB DESIGN● ESP32 FIRMWARE● LoRa LINKS● MQTT● HOME ASSISTANT● Zigbee2MQTT● Node.js● React● PostgreSQL● Docker● SELF-HOSTING● Modbus / RS-485● TIME-SERIES TELEMETRY● PCB DESIGN
Four trades. One pair of hands. Why build with me. 01 Demo first You see it working before you commit. No slide decks standing in for software.
02 Fits your operation Built around your process, not a template you bend yourself to fit.
03 Owned end-to-end One person from firmware to dashboard. Nothing lost in handoffs between vendors.
04 Built to last Systems still running five years on. I build things I can keep alive.
Selected work
Things I have shipped. Case studies
Two problems, solved. CASE 01 Running a large compliance book through one operator
Problem A growing compliance practice was tracking hundreds of filings across spreadsheets, email and memory. One missed deadline meant a penalty.
Process Mapped every recurring obligation, then built the workflow around the operator's real routine instead of an idealised one.
Solution One system that knows what is due, who owns it, and what is slipping, with reminders that fire before deadlines, not after.
Result [PLACEHOLDER: measured outcome, e.g. filings handled per operator, missed-deadline rate] CASE 02 Putting offline equipment online, affordably
Problem Field equipment gave no signal until it failed. Every fault was a surprise and a site visit.
Process Added sensing to existing machines rather than replacing them, and sent telemetry over whatever network the site already had.
Solution A live dashboard showing every unit health, with alerts that reach the team before the customer notices.
Result [PLACEHOLDER: measured outcome, e.g. units monitored, downtime reduced, site visits avoided] The whole stack. Software & Product React Node.js PostgreSQL REST & Realtime APIs Dashboards Auth & Roles Firmware & Hardware ESP32 Arduino / ESP-IDF LoRa Modbus / RS-485 Sensors PCB Design IoT & Data MQTT Time-series Telemetry Device Provisioning Alerting Edge-to-Cloud Systems & Self-hosting Docker Linux Home Assistant Zigbee2MQTT NAS Local-first After hours
The part I would do for free. Off the clock I am still building. Different stakes, same itch: make one thing talk to another and do something useful.
ESP32 & Firmware I flash microcontrollers for fun and write the firmware that makes them behave. A board, a sensor, a radio, and an evening quietly disappears.
Electronics & Hardware Breadboards, solder, the occasional custom PCB. I like understanding a system down to the trace, not just the API on top of it.
Home Assistant & Self-hosting I run my own stack. Local-first automations, dashboards I built myself, data that stays in the house. Owning it beats renting someone cloud.
How I got here. [PH] [PLACEHOLDER: where it started, the first thing built and why]
[PH] [PLACEHOLDER: first system shipped to a real user]
[PH] [PLACEHOLDER: Hivelinks founded, the scope widened]
[PH] [PLACEHOLDER: now, what is on the bench today]
Got a problem worth soldering? An operational headache, a device that should be online, or a home that should be smarter. Tell me about it.
Let's talk →