Software for operations teams
We build tools that take repetitive, error-prone operational work and turn it into something that runs reliably — extraction from portals that resist automation, fleet and maintenance records, financial workbooks, Windows diagnostics and repair, and the workflows in between.
Every project below is an independently verifiable public repository. Where something is unfinished, the page says so.
Tools that handle financial, tax or card data are built so that data stays on the operator’s own machine. Several projects request no network access at all.
Anyone can claim a system is broken. Our diagnostic work is designed around captured evidence, explicit confidence levels, and a rollback path for every change.
Repair tooling is built to refuse unsafe operations outright — not to warn and proceed, but to hard-block them.
Architecture, limitations and source are published with each project so the claims can be checked rather than taken on trust.
Projects
Four projects that show the range of what we build: a full fleet operations platform, a released e-invoicing exporter, a safety-gated Windows diagnostic toolkit, and a card scanner that structurally cannot leak data.
A fleet operations platform covering vehicle records, maintenance scheduling, work orders, fuel monitoring and the reporting built on top of them.
Illustration — not a screenshot of the application.
A Chrome extension that exports every invoice and line item from Egypt’s national e-invoicing portal into a formatted Excel workbook, using the portal’s own API rather than page-by-page scraping.
Illustration — not a screenshot of the application.
A local-only Windows 11 diagnostic, vulnerability-assessment and repair toolkit built on one rule: every finding needs evidence, and every repair needs a rollback path.
An Android application that records issued payment cards from the camera and exports them to Excel, designed so that it is structurally incapable of leaking card data.
Illustration — not a screenshot of the application.
The catalogue is organised by the operational problem being solved, not by technology fashion.
Software marketing usually hides the difference between a prototype and a shipped product. We label it instead, on every single project.
Source is public and a versioned download has been published.
Source is public and work is ongoing, but there is no packaged download yet.
Working source exists with a documented list of what is still unfinished.
Exploratory or internal work rather than a user-facing product.
The stack we actually use across the projects in this portfolio.
We take on the operational problem, not just the ticket.
Describe the process that is costing you time. We will tell you plainly whether software fixes it, how we would approach it, and what we would need from you.