In the oil industry, casing pipes represent significant value and pass through multiple parties, from the manufacturer and logistics providers to the drilling site. At every handover, the same question arises: was the pipe damaged, and if so, who was responsible?
MarQR Tracking set out to make this entire journey traceable, from manufacturing to final installation in the well. A previous development company had delivered a partially completed React Native application, but the assessment revealed that several business-critical features were still missing.
LogiNet first analysed the existing codebase using AI-assisted code analysis alongside its own technical review. Together with the client, we decided to fully refactor the solution. The web application was largely rebuilt, while the mobile application was rewritten from scratch. The platform is powered by a Django backend, QR code identification, push notifications, and role-based access management supporting five different user roles.
The solution is built around two unique concepts. During every asset handover, both parties independently record the condition of the pipe. If their assessments differ, the pipe is immediately flagged for investigation. The agreed condition is then stored in an immutable database built on Merkle tree technology (immudb), making it impossible to alter records afterwards and ensuring responsibility cannot be changed retrospectively.
MarQR received a fully auditable asset tracking platform that follows the complete lifecycle of every casing pipe, from manufacturing to installation. The immutable audit log and shared condition reporting create transparency between manufacturers, logistics providers, and on-site teams, while disputed cases remain permanently visible instead of disappearing from the process.
Project Information
Client:
MarQR Tracking
industry:
Oil & Gas
Technologies:
Django, React Native, immudb, QR Codes
Ready to Build Something Real?
No sales pitch. No buzzwords. Just an honest conversation about your challenges and how we might help.
What is the difference between Jev and an LLM?
An LLM generates general text. Jev classifies or decides based on a context, a question and an answer format, and replies in the requested structure.
What does System One model mean?
What question types does Jev support?
What does the confidence level show?
What tasks is Jev good for?
How much faster and cheaper is Jev?
Can Jev be used in real time?
How many times does the while loop in Probably run?
Is there an open-source alternative to Jev?
Ready to Build Something Real?
No sales pitch. No buzzwords. Just an honest conversation about your challenges and how we might help.






