About Lornets
Built for the point where software becomes important.
Lornets is a London-based production assurance and engineering consultancy for organisations whose software has become commercially or operationally important.
Customers may depend on it. Revenue may run through it. It may process sensitive information, face investor or enterprise scrutiny, support critical operations, or sit inside a workflow the organisation cannot afford to misunderstand.
Rapid and AI-assisted development is one way software reaches that point quickly. It is not what determines the technical conclusion.
Lornets also works where a consequential AI use case needs to move into real operations. The same principle applies: start with the operating outcome and establish what the organisation needs to be able to depend on.
The problem Lornets specialises in
Proving that software works is a different problem from knowing that an organisation can safely depend on it. The first is a demonstration. The second is an engineering position that has to hold under fundraising scrutiny, serious production use, enterprise procurement, sensitive data handling, operational dependence and growth in usage.
That is the point Lornets is built for: the software matters, and the technical questions being asked of it have changed.
- Can it fail safely?
- Can another engineering team understand and operate it?
- Is access to sensitive information properly controlled?
- Can failures be detected, diagnosed and recovered from?
- Can it support greater usage without unnecessary architectural complexity?
- Can management explain and defend the technical decisions behind it?
How Lornets approaches the problem
Keep · Refactor · Replace
Assess first. Keep what works. Refactor where justified. Replace only where necessary.
Lornets does not start from an assumption that a client needs a rewrite, a migration, more infrastructure or more AI. We start by understanding the system, its responsibilities and its actual failure modes, then recommend the smallest change that makes the software defensible at the level of responsibility it now carries.
Production assurance work examines architecture, security, reliability, scalability, data, delivery and observability through the Production Assurance Framework, with contextual overlays where relevant.
Lornets combines senior engineering judgement with a repeatable evidence-based methodology. Conclusions are tied to observable technical evidence, explicit operating context and recognised engineering frameworks.
The judgement behind the practice
Dr Anas Almharat, Founder and Technical Director
Lornets is founder-led. Dr Anas Almharat has more than 15 years of experience across engineering, software, AI and consulting, including taking AI systems from prototype into highly regulated production environments, leading multidisciplinary technical teams and working on systems supporting critical operations serving millions of customers. He holds a PhD specialising in artificial intelligence and reasoning under uncertainty.
That experience spans banking and financial services, defence, aerospace, health, energy and technology, across large organisations, startups, scaling companies and consulting environments. It is the reason the Lornets framework concentrates on what happens after the prototype: architecture, access to sensitive information, reliability, recovery, observability and engineering ownership.
These sectors describe career experience. They are not a list of Lornets clients.
Technical philosophy
Working across early products, scaling companies and highly controlled production environments makes one thing clear: more technology is not automatically better engineering. What changes between those environments is consequence, and consequence is what should determine how much engineering a system deserves.
Lornets applies that proportionality deliberately. Understand the system first. Keep what remains appropriate. Strengthen what needs attention. Replace only where the evidence justifies it. Engagements are run from London, United Kingdom, remotely across the United Kingdom, Ireland, the Netherlands, the Nordics and the United Arab Emirates, with on-site work in London where it is useful.