Software for connected devices: From prototype to product.
Your device works on the bench. We build the companion app, cloud backend and admin panel that make it a product, plus the firmware when you need it.
- Device
- Phone or gateway
- Cloud
- Admin panel
( Shipped with )
( Also works with )
( The gap )
A working prototype is about a third of a connected product.
The rest only shows up once real people carry the device around. These are the four places it usually breaks.
Connections drop.
Phones kill background Bluetooth. Without reconnect logic, users think the device is broken.
Data goes missing.
A device that is offline for an hour needs somewhere to keep its readings and a clean way to sync them.
Nobody can see the fleet.
Once 500 units are in the field, someone needs a panel showing which are online, which are failing and why.
The cloud bill surprises you.
Message volume is predictable. It should be calculated before launch, not discovered after.
( What we build )
From device to fleet, in one picture
- 01Yours
Device
Your hardware and firmware
- Your boards and firmware
- Our firmware engineers, when you need them
- Message format we agree together
Runs on Your boards
- 02We build
App
Built by us
- Pairing
- Automatic reconnect
- Offline sync
Runs on iOS and Android
- 03We build
Cloud
Built by us
- Secure onboarding
- Ingestion and storage
- Alerts
Runs on AWS, Firebase or your own
- 04We build
Admin
Built by us
- Fleet view
- Users and roles
- Reports
Runs on Web dashboard
One team for the app, the cloud and the fleet.
( Where you are )
Where is your hardware today?
Still prototyping
Software does not have to wait. We agree the data format with you and build against a simulated device, so the app and cloud are ready when the boards are.
See how a build goes02Heading to production
We size the backend for your launch numbers, set up device onboarding and get the app through store review.
How we size a launch03Already shipping
We fix dropped connections, add fleet monitoring and take over a codebase someone else left behind.
Fixing dropped connections( How it works )
How a build goes
Six steps. At the end of each one you receive something you can open, check and keep.
We define what the device sends, how often and over which protocol, with your firmware team or ours.
You receive
A one page message specification both teams sign off.
Message specification · v1Exampletopic: devices/{device_id}/telemetry · every 60 s · QoS 1
device_id string, set at onboarding ts unix time, milliseconds temp_c number, 0.1 steps battery number, 0 to 100 fw string, firmware version We work out users, messages per second, storage and monthly cloud cost.
You receive
A sizing sheet with the arithmetic shown.
How we do the arithmeticSizing sheetExampleDevices at launch 500 Messages per device 1 per minute Messages per second 500 ÷ 60 ≈ 8.3 Messages per month 500 × 1,440 × 30 = 21.6 million Storage per message about 200 bytes Storage per month about 4.3 GB Secure device onboarding, ingestion, storage and alert rules.
You receive
A working pipeline you can send test data through.
Pairing, automatic reconnect, offline sync and the screens your users see.
You receive
Test builds on your phone every week.
Fleet view, alerts, users and roles.
You receive
A staging link you can log into.
Admin panel · FleetExample482
Online
12
Offline
6
Alerts
- unit 0142Online · 2 min ago
- unit 0377Low battery · 18%
- unit 0419Offline · 3 h
Pipelines, monitoring and documentation.
You receive
Repositories, cloud accounts and keys in your name.
( Case study )
FuelSec: catching fuel fraud at the dispenser.
- Problem
- Drivers, families and fleet owners paying for fuel see only the pump's own reading, with no way to check the tank received it. Stations had no record to prove honest fills or find repeated problems.
- What we built
- An ESP32 device at the nozzle that measures every fill with its own flow meter and the dispenser's pulse signal at once, compared live every second. A Flutter app connects to it over the device's own WiFi, captures photo evidence and works without mobile signal. A FastAPI backend raises fraud alerts, and a Next.js admin panel gives stations a live view of every nozzle.
- ESP32
- Flutter
- FastAPI
- Firebase
- Next.js
- Result
- Running now as a pilot. Every fill is checked litre by litre, any gap above 0.05 litres is flagged, tampering is reported instantly, and firmware updates reach every device over the air.
The client is not named here. Their identity is kept confidential under our agreement.
Read the full case study( The hard parts )
The hard parts, and how we handle them
Companion apps
Automatic reconnect that survives the phone's battery saver.
Phones close background Bluetooth to save battery. We use the tools iOS and Android give connected devices, and the device keeps every reading until the app is back.
Read the articleCloud and alerts
Measuring latency end to end.
Every message is timestamped at each hop, from the device to the alert. We watch the 95th and 99th percentiles, where the late alerts users notice show up.
Read the articleBackend sizing
Sizing for the launch you hope for.
A launch planned for 50 users met 11,670. What decides whether a backend survives that, and what to check before the day arrives.
Read the article( Working with your team )
We fit beside your hardware team.
- We work from your firmware team's specification.
- White label delivery under your brand, if you are a design house.
- An NDA before any files change hands.
- A weekly demo on a staging link.
( How to start )
A small first step, then the full build
- 1
Technical call
30 minutes, free
You show us the device and the plan.
- 2
Proof of concept
Fixed price, one to two weeks
One device talking to the cloud and showing up on a screen.
- 3
Full build
Fixed price
A written scope and a fixed price within 48 hours of the call.
- 4
Partnership
Monthly, if you want it
We stay on to monitor the fleet, fix problems early and keep the cloud bill in check.
- Fixed scope
- 100% code ownership
- Written roadmap in 48 hours
( After launch )
Launch is where the partnership starts.
We like to stay on as your technical partner once the devices are in the field. Every month we watch how the system is used, fix problems before your customers find them, and keep the running costs honest.
Ask about a monthly partnershipPrefer a single build? That works too. You receive the full handover, the code, the cloud accounts and the documentation, and you can come back for more whenever you need it.
Fleet and system monitoring
Devices, app, cloud and panel watched every day, with alerts that reach us before they reach your users.
Problems fixed early
Rising error rates, slow messages and failing units are spotted in the data and dealt with while they are still small.
A cloud bill that earns its keep
We review usage every month and switch off any service that costs you money without adding value.
Updates that keep it working
Firmware updates over the air, app releases for new iOS and Android versions, and security patches.
A short monthly report
What we checked, what we changed, what it cost and what we suggest next.
The same team builds web platforms and dashboards. A few that are live.
( Blog )
What we have learned, written plainly
View more articlesYour device did not break. The phone closed the app.
Most dropped Bluetooth connections come from the phone, not the firmware. Here is what iOS and Android do, and how to design around it.
- Mobile apps
- Systems integration
- Cloud deployment
Measure latency where your users feel it.
A dashboard can say 200 milliseconds while some alerts arrive a minute late. Here is how to see every hop, and every slow message.
- Cloud deployment
- Systems integration
- Web development
How to judge a software agency before you sign anything.
Every proposal says experienced, fast and affordable. Here is how to tell which one means it.
- Web development
- UI and UX design
- Mobile apps
( Questions )
Questions we get asked most
Yes. CoreFinity Tech agrees the data format with your team and builds the app and cloud against a simulated device, so the software is ready when the boards are.
Yes, when you need it. Most projects pair CoreFinity Tech's app, cloud and admin work with the client's own firmware team, and CoreFinity Tech's firmware engineers step in on ESP32, STM32, Nordic nRF and RAKwireless boards when there is no team in place.
CoreFinity Tech has shipped ESP32 devices with Flutter apps and Python backends, and its firmware engineers also work with STM32, Nordic nRF and RAKwireless modules. Projects connect over WiFi, BLE, MQTT or LoRa.
Yes. CoreFinity Tech reviews the existing code, fixes dropped connections and missing monitoring first, then carries on building from where the previous team stopped.
The client owns everything CoreFinity Tech builds. Repositories, cloud accounts and keys are set up in the client's name, and nothing stays locked to CoreFinity Tech.
Each device gets its own X.509 certificate and connects to AWS IoT Core over mutual TLS, with a policy that only lets it use its own topics. Firmware updates are signed and verified on the device before they install, keys are kept in secure storage, and data is encrypted in transit and at rest. A lost or compromised device is cut off by revoking its certificate, with no effect on the rest of the fleet.
Yes. CoreFinity Tech delivers white label work under the design house's brand, signs an NDA before any files change hands, and builds from the hardware team's own specification.
Yes. CoreFinity Tech prefers to stay on as a monthly technical partner, covering monitoring, early fixes, updates and a monthly review of cloud costs. Single builds are welcome too, with the full code, accounts and documentation handed over at the end.
CoreFinity Tech is based in Islamabad, Pakistan, and works remotely with hardware teams worldwide. Messages get a reply within one business day, and calls are booked at a time that suits the client's working day.
Show us your device.
Send a spec sheet or book 30 minutes with an engineer. You get a written plan within 48 hours.