LEGO Life of George
Computer vision in a consumer product
For LEGO Life of George we developed real-time image recognition connecting physical objects to a digital game.
iGates builds AI capabilities into real systems that run in production — not demonstrations. We develop AI agents, retrieval and reasoning over enterprise data, document processing, computer vision, and models that run on the device itself, then integrate them with the core systems you already operate.
What separates a working AI system from a convincing demo is not model access. It is the engineering required to make an AI capability secure, stable, observable and predictable in cost — and to make it fit an organisation that already exists.
AI development in a business context is not training models from scratch. It is building a new capability inside an existing product or system: an agent that completes a task, search that understands a question in plain language, a classifier that routes documents, or a model that detects a fault in real time.
Connecting a model and getting an answer is the easy part. Everything that decides whether the project reaches production is harder: where the data comes from, who is allowed to see what, what happens when the model is wrong, what it costs at scale, and how you know six months later that it still works.
That is ordinary software engineering. It is what we have done since 2010.
In each case we take responsibility for the whole system, not only the model layer.
For defence organisations, public bodies and companies under regulatory constraints, the first question is not what the model can do. It is where the data goes.
We run open-weight models on your infrastructure — in your private cloud, in your data centre, or in an environment fully disconnected from the internet. Your data does not leave your environment and does not reach a third-party provider.
This is possible because of depth most software houses do not have. We have worked at the operating-system and hardware level for years — embedded Linux, drivers, and Android Internals — so deploying a model into a closed environment is familiar engineering for us rather than a research project. See Embedded Development.
Where there is no regulatory constraint we also work with the leading providers — OpenAI, Anthropic and Google — selecting per task rather than by habit.
Not every AI capability belongs in the cloud. When a response has to be immediate, when connectivity is unreliable, when bandwidth is expensive, or when the data is too sensitive to leave the device, the model has to run at the edge.
We develop models that run on devices and controllers: local inference, optimisation for memory and power, and integration with dedicated hardware. This connects directly to our work in embedded systems and IoT.
Models: self-hosted open-weight models, plus OpenAI, Anthropic and Google.
Retrieval: pgvector on Postgres, self-hosted vector databases (Qdrant, Weaviate, Milvus), and managed services where no regulatory constraint applies.
Knowledge bases: structured Markdown and Obsidian knowledge bases — human-readable, editable, and fully ownable by the client.
Orchestration: LangChain, LlamaIndex, Semantic Kernel, and custom development where frameworks fall short.
Computer vision: image and object recognition, real-time processing, on-device inference.
Classical ML: forecasting, classification and anomaly detection over sensor and transaction data.
Infrastructure: monitoring, quality measurement, cost control, and CI/CD.
We have developed for AI21 Labs, one of Israel's leading artificial-intelligence companies.
AI capabilities built for a classified environment, including local models running without internet connectivity.
For LEGO Life of George we developed real-time image recognition connecting physical objects to a digital game.
Some of our capabilities were built and tested internally first, including agent systems for software development. We do not sell a capability we have not run ourselves.
Every interaction with a model sits inside an engineering process rather than replacing one.
Computer vision in a consumer product
For LEGO Life of George we developed real-time image recognition connecting physical objects to a digital game.
Not necessarily. For organisations with regulatory or classification constraints we run open-weight models on your own infrastructure, including in environments disconnected from the internet. Where no such constraint applies, external providers are also an option — and the decision is made together during specification.
We do not train foundation models. We build systems on top of them — agents, retrieval layers, processing and monitoring — and where needed we adapt existing models to your task and data.
A demo has to work once. A production system has to work every time, against real data, with permissions, predictable cost, quality monitoring, and a defined response when the model is wrong. Most AI projects stop precisely at that gap.
Operating cost is part of the specification rather than a surprise that arrives later. We measure model usage cost during the feasibility stage and build the system so it can be controlled — selecting models per task, caching results, and running locally where that is cheaper.
Yes, and in practice that is most of the work. We build intermediate layers that connect AI capabilities to existing systems without rewriting them, including legacy systems with no modern interface.
Yes, and we say so upfront — it affects the pricing model. It happens inside a full engineering process: specification and architecture before, code review after, and normal testing and deployment cycles throughout.