ThingsBoard delivery for IoT hardware teams
Your device works. We make it customer-ready.
Customer logins, live dashboards, alarms and weekly reports — configured, tested against written checks and handed over in your own ThingsBoard account. One fixed scope, one fixed price.
- ₹14,999 total · USD 500No GST is charged
- Within 15 business days after complete inputs and access
- Your account, your data
- Remote delivery, no lock-in
| Device | Value | Last seen |
|---|---|---|
| Cold room 1CR-101 | −18.4 °C | 18 sec |
| Cold room 2CR-102 | −19.1 °C | 42 sec |
| Chiller 1CR-103 | 7.8 °C | 1 min |
| Cold room 3CR-105 | −17.6 °C | 2 h 57 min |
Built for small sensor and IoT teams in cold-chain, water, energy, agriculture and air-quality monitoring.
- Cold-chain
- Water
- Energy
- Agriculture
- Air quality
The delivery gap
Your hardware is ready. Your customer portal isn't.
A working sensor is only half the demonstration. The customer still needs a secure login, data they can read, alarms they can trust and a report that reconciles.
What you get
One payload in. A customer-ready demo out.
One coherent customer journey, built around the payload your device already sends.
Customer logins & isolation
Named users see only the devices and views assigned to them.
Live dashboard
Current status, trends and fleet context in one operator view.
Offline & threshold alarms
Written open and clear conditions, checked against known data.
Weekly report (PDF/CSV)
A sample report whose device rows reconcile to raw readings.
Written acceptance checks
Done is defined before the build, then checked at handover.
Recorded handover & export
Configuration, evidence, runbook and a recorded walkthrough.
How it works
Four steps. Fixed scope.
The clock starts after the required inputs and access are complete.
- 01Day 0
15-min fit call
Confirm the working payload, deadline and whether the fixed scope fits.
- 02Inputs
Access & inputs
You share one payload and a sandbox account.
- 03Build
Build & test
Within 15 business days after complete inputs and access; 10-business-day target.
- 04Handover
Acceptance & handover
You run the checks; you keep everything.
Next start: 14 Dec 2026 (India) · 4 Jan 2027 (global).
Acceptance, not promises
Done means 10 written checks pass.
The checks are agreed before work starts. A peer reviewer re-runs them before handover, then you run the applicable checks in your own account.
If a Pakvaro-caused check fails, Pakvaro fixes it within 5 business days. If it still fails, Pakvaro refunds the unearned amount. One cure window only.
| Check | Measured evidence | Result |
|---|---|---|
| 01Valid sample payloadData in | NOT RUN | |
| 02Malformed payloadData in | NOT RUN | |
| 03Offline and recoveryAlarms | NOT RUN | |
| 04Threshold and recoveryAlarms | NOT RUN | |
| 05Tenant isolationLogins | NOT RUN | |
| 06Weekly report reconciliationReport | NOT RUN | |
| 07Credential rotationData in | NOT RUN | |
| 08Backup restoreNot applicable | N/A | |
| 09Customer access and exportLogins | NOT RUN | |
| 10Handover artefactsHandover | NOT RUN |
Pricing
One fixed price.
A defined outcome, a written acceptance record and no open-ended build.
- Customer logins & isolation
- One live dashboard
- Offline & threshold alarms
- One sample weekly report
- Written acceptance checks
- Recorded handover & export
PaymentIndia: 100% in advance. Global: 100% in advance, or a funded Upwork milestone.
DeliveryWithin 15 business days after complete inputs and access (10-business-day target)
Fix window5 business days, then refund of the unearned amount
Reference slots: ₹11,999 total; no GST is charged / USD 400 when you agree to a published case study.
For integrators
Overflow capacity, under your brand.
Partner-branded delivery for a fixed slice of work. The partner keeps the client relationship and the client's written authorisation stays explicit.
You keep the client
The relationship and production cutover stay with your team.
Fixed scope, written acceptance
The same checks, evidence and cure terms apply to the subcontract slot.
Starts 4 Jan 2027 (global) / 14 Dec (India)
One paid delivery at a time keeps the handover focused and accountable.
FAQ
Questions teams ask first.
If the scope fits, the 15-minute call confirms it — no pressure.
Is my data safe?
Work happens in your own ThingsBoard tenant, licence or Cloud account using time-limited, least-privilege access where practical. Customer personal data, credentials, keys, production exports and confidential code never enter consumer AI services.
Which platform do you use?
ThingsBoard, in the account and licence you control. Pakvaro is not affiliated with or endorsed by ThingsBoard, and does not provide licence advice.
Who owns the work?
You keep your account, data, keys, billing and the handed-over configuration, evidence and runbook. The signed statement of work records the exact access and deliverables.
What do you need from us?
One working MQTT, HTTP or LoRaWAN payload; field names, units and timezone; a sandbox account; alarm values; the report rule; and one named person for decisions and acceptance.
How long does it take?
Delivery is within 15 business days after complete inputs and access, with a 10-business-day target. The written start date is confirmed after the inputs are complete.
How do I pay?
India: 100% in advance by bank transfer or UPI, with an invoice. Global: 100% in advance, or a funded Upwork milestone. Platform or subscription costs are paid directly by you.
Do you do on-site work?
No. Delivery is remote; your installer commissions devices, connectivity and field hardware.
Vinay Tiwari
Founder, Pakvaro
Indore, India- ESP32 telemetry systems
- ThingsBoard deployments
- MARG-DRISHTI — road-roughness monitoring (ESP32 · IMU · GPS)
Founder-led delivery
Built by the person who hands it over.
I'm Vinay Tiwari. I build ESP32 telemetry systems and ThingsBoard deployments — including MARG-DRISHTI, a road-roughness monitoring system. Pakvaro exists because sensor teams shouldn't have to hire a cloud team to show their customers a working portal.
Next step