
Products
The platform layer,in four products.
Four products on Qode Core infrastructure — each on a different stratum of the same architecture, all four inside your perimeter rather than beside it.
The four
Four products,three strata.
These pages publish position and architecture, not a feature matrix. The capability specification for each product is issued in a technical briefing.
Why there is no feature matrix
These four pages publish position and architecture rather than a feature matrix. The capability specification for each product is issued in a technical briefing, against the environment you are scoping — because a feature list written for everyone answers the question for no one. No capability should be inferred from a product’s category or from its name.

One architecture
Inside your perimeter,not beside it.
All four run on Qode Core infrastructure, inside your perimeter, under one jurisdiction.
Where they sit
Three strata,and one that watches.
Intellake, Oryn and Kyro each occupy a band of the same architecture. Insight 360 observes all three.
Read the detail
Qode Core builds the infrastructure beneath enterprise AI, and four products on top of it. Each one occupies a different stratum of the same architecture, and all four run inside your perimeter rather than beside it.
Intellake, Oryn and Kyro each occupy a band of the same architecture. Insight 360 occupies none of them — it observes all three, which is why it is drawn across the full height.

Also on the platform · QODE Cortex
One governed foundationfor AI, GenAI and IoT.
Qode Core’s intelligence platform, built on Lorgan’s Enigma and Ellie and hosted in-country.
- Batch, real-time and IoT ingestion
- Behavioural modelling
- ML & analytics
- Generative & agentic AI
Read the detail
QODE Cortex — Intelligence platform — on Lorgan Enigma & Ellie.
QODE Cortex is Qode Core's intelligence platform, built on Lorgan's Enigma and Ellie and hosted in-country. Data ingestion, behavioural modelling, machine learning and generative and agentic AI share one foundation, so a tenant reaches production without assembling a separate toolchain for each.

How it deploys
Wherever the restof your stack runs.
All four are the same shape operationally: Qode Core infrastructure, inside your perimeter, one jurisdiction.
In-tenant
Deployed inside your perimeter rather than consumed from someone else’s. The product runs where your data already is.
Jurisdiction
DetailOn Qode Core infrastructure in the United Arab Emirates, under a single legal regime.
Deployment models
DetailAvailable across colocation, dedicated infrastructure and managed services. The responsibility boundary moves; the product does not.
Air-gapped
DetailWhere the workload requires it, the environment has no route to the public internet at all.
Sizing and configuration
Sizing, dependencies and supported configurations are established per product in the technical briefing. They depend on model, throughput and data classification, so there is no single correct answer to publish here.

Products
Ask uswhat it does.
A briefing is an hour with an engineer, the specification for the one product you care about, and a straight answer on whether it fits. It is not a demo of all four.








