Fleet, ELD & telematics
Hours-of-service logging, FMCSA submission, CAN diagnostics, dashcam pipelines and transport management. Compliance is unforgiving here, and we know exactly where it bites.
Product engineering studio · Working worldwide from Kolkata
From the screen to the sensor.
Almetric builds software products end to end — web platforms, mobile apps, and the cloud behind them. And when a product reaches into the physical world, we build that part too: the firmware, the radio link, the device. Fifty-plus products across eleven industries, from hospital systems to fleets of trucks.
Founder-led. You'll talk to the engineer who would run the build, and hear back within one working day.
- Web & product
- Mobile apps
- Cloud & data
- Firmware
- Devices & sensors
- 50+
- products and platforms shipped
- 12
- years of principal engineering experience
- 11
- industries, from healthcare to logistics to media
The whole stack, under one roof
Most projects need the top two or three layers, and that is fine — that is the bulk of our work. The point is that the stack does not run out when a project needs to go further down it.
Web & productReact · TypeScript · Node
Most of what we build lives entirely in software: customer portals, operator consoles, admin systems, booking platforms, dashboards and marketing sites that actually rank.
MobileReact Native · iOS · Android
Offline-first apps that keep working with no signal and reconcile cleanly when they get one. Multi-environment builds, store submission, and the battery profiling that keeps a driver's phone alive all shift.
Cloud & dataGCP · PostgreSQL · streaming
Ingestion and storage sized for telemetry volumes, with the query performance to answer real questions across millions of rows — plus the access control an audited industry demands.
ConnectivityBLE · LTE · MQTT
Getting data off the device reliably: background BLE that survives an iOS restart, cellular modems that reconnect on their own, and message pipelines that don't drop a reading when a truck goes through a tunnel.
Hardware & firmwareESP32 · STM32 · J1939
Firmware for devices that live in trucks, clinics and kitchens — where power budgets, reboots and bad connectivity are the normal case, not the edge case.
Where we go deep
Generalists in technology, specialists in these industries. That's where accumulated domain knowledge saves you months of learning on your budget.
IoT & connected devices
From a bench prototype to a fleet of devices in the field, with provisioning, updates and telemetry designed in from the start rather than bolted on before launch.
Healthcare & vertical SaaS
Hospital systems, patient apps and kiosks, plus software built for one industry's real workflow — restaurants, clinics, sports clubs, home services.
Recent builds
Platforms in production, carrying real operations. Named on request.
Fleet compliance & TMS
An electronic logging and transport management platform for North American carriers: telematics hardware, driver app, dispatch console and the cloud between them.
Hospital system, app & kiosk
A healthcare suite across three surfaces — patient application, clinician and admin system, and an on-site self-service kiosk — from one clinical data model.
Restaurant operating system
Branded ordering apps per venue, point-of-sale integration, and automation across the order lifecycle so staff stop relaying information between screens.
Founder-led, not account-managed
Almetric is deliberately small. Rahul Tibrewal, who founded it, has twelve years in the work and is the principal engineer on every build — the person you scope with is the person writing the hard parts.
That changes what a project feels like. Decisions get made in the same conversation they're raised in. Nothing is translated through a layer of account management, and nothing gets quietly reassigned to whoever is free. When a firmware bug turns out to be a cloud bug, the same person follows it across the boundary.
It also means we take on a limited number of builds at a time, and we'll say so plainly if yours isn't a fit.
How engagements usually run
A short paid discovery to pin down scope, architecture and risk. Then either a fixed-scope build with milestone delivery, or a monthly retainer if the roadmap is still moving.
You keep the code, the infrastructure accounts and the documentation throughout. Handover isn't an event at the end — it's the default state.