Your environment
Container-first and cloud-native, available for deployment in your cloud, on-premise, or in a sovereign environment where residency requires it.
lalla.ai is the AI platform beneath everything Innopas ships: graph-grounded retrieval, agents, evidence, evaluation, guardrails, and Lalla Chat as the surface people actually touch. A new product brings a domain graph and an interface. It does not bring its own AI stack.
The Innopas model
Innopas is an AI technology company. We build our own AI platform, our own products, and the research that makes them hard to copy. lalla.ai is the middle link, and it is the one that compounds.
DeepTech Research & Intelligence Hub. Representation, forecasting, attribution and explainability, proven against a baseline before anything ships upward.
Models, retrieval, agents, evaluation, guardrails and Lalla Chat. Built once. Shared by everything above it, and versioned so a product team cannot quietly fork it.
A domain graph and the screens people live in. EUNIQ for energy and utility networks, TopSyllabus for education. Nothing below layer three is rebuilt.
The test of a platform is the second product. Anything can be called a platform while one product runs on it. TopSyllabus and EUNIQ share no customers, no regulator and no vocabulary. They run on the same layer two.
The stack, live
Five planes, wired as they actually run. Research feeds the platform from underneath; the six capabilities cross-wire to each other; two domain graphs sit on top of them; and the products are the thinnest thing in the diagram.
Around all of it, four solutions hold their own orbits: DeepTech, Data Spine, AI Engine and Cloud Mesh. They are the ways a client enters, and each one draws on the same core. Drag to turn it.
Five layers, bottom to top: DTRIHub research; the lalla.ai platform core with six capabilities; the utility knowledge graph and concept graph; the EUNIQ and TopSyllabus products; and the surfaces: Lalla Chat, dashboards and APIs, field and operations. Four solutions orbit the core: DeepTech, Data Spine, AI Engine and Cloud Mesh.
Topology, not telemetry. The wiring is how the platform is composed; the pulses are illustrative.
Inside the platform
Six capabilities, versioned and shared. A product team consumes them; it does not reimplement them. Each one exists because something specific goes wrong without it.
Retrieval that walks a typed domain graph rather than searching a pile of documents. The answer is assembled from the structure, so it can name the node it came from.
Why Flat retrieval cannot tell you which transformer, or which prerequisite.
Agents that query the graph, run a model, call a service and compose a result. Each step is recorded, so what happened can be reconstructed later rather than inferred.
Why An unexplained action is one nobody in a regulated business will authorise.
Every output carries its supporting evidence and a confidence value, produced at the same time as the answer rather than reconstructed afterwards.
Why This is what a regulator, an auditor or a parent is actually asking for.
Test sets, baselines and regression runs for every capability. A change ships when it beats the previous version on the record, not when it demos well.
Why Without this, a model upgrade is a gamble taken in production.
Access control down to the graph node, redaction, refusal behaviour and audit logging. A student and an operator see only their own scope, enforced below the product rather than inside it.
Why Permissions implemented per product are permissions implemented inconsistently.
Model-neutral by design, and deployable in your cloud, on-premise or in a sovereign environment. Some customers cannot send data anywhere else.
Why A platform locked to one vendor or one region is a platform with a shelf life.
Lalla Chat
Lalla Chat is the same component in both products. What changes is the graph it is grounded in and the scope it is allowed to see. Ground the answer in a graph, name the node, show the evidence, state the confidence. Only the vocabulary belongs to the industry.
Use the surface switch above to move the page between the two. Nothing about the platform changes.
Running on layer two
One core, many domains. Every product sits on the same platform and adds only the knowledge of its own field, which is why the second product cost a fraction of the first, and why a competitor has to rebuild the foundation rather than copy the interface.
Electricity, gas and water network intelligence. Loss, assets, forecasting and field work, with Cockpit, Command and Field for utility teams.
euniq.ai ↗ EducationAI exam practice with evidence behind every score. Concept mastery, evaluated answers, and dashboards for students, parents and schools.
topsyllabus.ai ↗ The companyThe AI technology company behind both: the products, the platform underneath them, and the research programme that keeps the platform ahead.
innopas.com ↗Runtime & governance
Both of our domains are governed ones. The platform is designed so that a security review is a conversation about architecture rather than a negotiation about exceptions.
Container-first and cloud-native, available for deployment in your cloud, on-premise, or in a sovereign environment where residency requires it.
Access control to the graph node, tenant isolation and retention rules implemented in the platform, so every product inherits the same behaviour.
What was retrieved, which agent ran, which model answered and what confidence it carried, all recorded with the answer rather than reconstructed after it.
APIs into retrieval, agents and evaluation, so the platform sits inside your stack rather than replacing it. License it, or have us build your domain on it.
DTRIHub
DTRIHub, our DeepTech Research & Intelligence Hub, is a standing team rather than a project allocation. It works with university research groups and our PhD advisors on representation, forecasting, attribution and explainability. A method is proved against a baseline in research before it is allowed into the platform.
Questions
lalla.ai is the AI platform Innopas builds on: layer two of a four-layer stack that runs research, platform, domain and product. It provides graph-grounded retrieval, agents, evidence and confidence, an evaluation harness, guardrails and model portability. A new product brings a domain graph and an interface; it does not bring its own AI stack.
No. It is model-neutral by design and routes across model families. Retrieval walks a typed domain graph rather than searching a pile of documents, scope is applied before anything is read, and every answer carries the evidence and confidence it was produced with.
Lalla Chat is the conversational surface of the platform, and it is the same component in every product. What changes between products is the graph it is grounded in and the scope it is allowed to see, not the component itself.
EUNIQ, an intelligence platform for electricity, gas and water networks, and TopSyllabus, an exam practice platform for K-12 education. The two share no customers, no regulator and no vocabulary, and both run on the same layer two.
It is container-first and cloud-native, and is available for deployment in your cloud, on-premise, or in a sovereign environment where data residency requires it. Access control is enforced to the graph node, below the product rather than inside it.
Yes. The platform exposes open APIs into retrieval, agents and evaluation, so it can sit inside an existing stack. Innopas can also build a domain on it. The starting point is a thirty-minute call with the engineers who would do the work.
Start here
Thirty minutes with the engineers who would do the work. No deck, no discovery invoice. A straight read on feasibility, sequence and what a first build would take, including when the answer is that you should not build it.
30 min · video call · Who joins · engineering, not sales · Cost · none