Most software platforms are built around clean workflows. The automotive recycling industry is not clean. A single vehicle can move through: quoting towing compliance checks dismantling inventory scrap processing container packing offshore warehousing final sale And most businesses manage this using spreadsheets, whiteboards, WhatsApp messages, and paper forms. That’s the problem we set out to solve with InfraByte. The Real Problem Wasn’t “Inventory” At first glance, automotive recyclers look like inventory businesses. They’re not. They’re operational workflow businesses. The hard part is not storing parts. The hard part is tracking everything that happens between: “Customer wants to sell a vehicle” and “Part sold months later.” That includes: dispatching drivers capturing IDs and signatures PPSR checks documenting compliance tracking dismantling managing containers monitoring offshore stock generating reports The biggest issue we found was fragmented systems. Every department used different tools. Nothing talked to each other. Our Approach We built InfraByte Software as a connected operational platform instead of separate modules. The architecture combines: .NET 8 Blazor Server SignalR Redis SQL Server Hangfire Azure services multi-tenant infrastructure The key idea: A vehicle should remain traceable throughout its entire lifecycle. From: website inquiry quote booking pickup dismantling inventory export sale Everything remains connected. One Unexpected Engineering Challenge One of the hardest technical problems wasn’t UI or APIs. It was state management. Jobs are constantly changing: Drivers update statuses Office staff modify bookings Payments are processed Dismantlers update inventory Containers are packed All in real time. We moved toward a cache-first architecture using: Redis…
Want more insights? Join Grow With Caliber - our career elevating newsletter and get our take on the future of work delivered weekly.
