Deep packet inspection for Saudi operators, ISPs and regulators
DPI Saudi Arabia: deep packet inspection on your infrastructure, supported from Riyadh
DPI Saudi Arabia buyers usually ask three things: does it work on our traffic, can it stay in the Kingdom, and who supports it here? Interkey Intelligent DPI classifies traffic by application in real time, including encrypted traffic, without decrypting it. It runs on the operator's own infrastructure and can operate entirely in the Kingdom, and Interkey's team in Riyadh handles localisation, integration and support, in Arabic and English.
A Saudi product, built by Interkey
For network, policy, compliance and procurement teams at Saudi operators and ISPs, and for regulators. Reviewed November 2026.
- What it is:Interkey Intelligent DPI, a deep packet inspection platform with an AI traffic model at its core.
- What it does:classifies traffic by application in real time, applies policy per application, subscriber group or cell, and reports in Live View.
- Who it is for:national operators, internet service providers and regulatory bodies in Saudi Arabia.
- Where it works:fixed and mobile networks, on your own infrastructure, and it can operate entirely in the Kingdom.
What deep packet inspection does for each organisation
| Organisation | Governance job | What Interkey Intelligent DPI contributes |
|---|---|---|
| National telecom operators | Unified, reliable content governance across fixed and mobile networks at national scale. | Traffic intake designed for Tbps-scale volumes, policies per application, subscriber group or cell, and Live View with latency measured in seconds. |
| Internet service providers | Precise application classification and content filtering to meet national regulatory requirements. | Classification of encrypted and tunnelled flows without decryption, a URL library, and report-only mode to check each rule before it acts. |
| Regulatory bodies | Applying digital safety rules consistently, with evidence that they are applied. | Classification of application traffic, policy execution feedback, and a reporting layer for regulatory teams. |
Where it runs and what it keeps
A DPI platform sits where subscriber traffic passes, so where it runs is a design decision. Interkey Intelligent DPI runs on the operator's own infrastructure and can operate entirely in the Kingdom, so subscriber traffic does not have to leave Saudi Arabia.
The platform's output is metadata about applications, traffic volumes and triggered policies. Retention and access follow your data-governance rules and the contract. Which laws and regulator requirements apply to your organisation is for your compliance, privacy and legal teams to determine. For the questions to put to any DPI supplier, see DPI data residency.
National filtering requirements
In Saudi Arabia, the Communications, Space and Technology Commission (CST) provides internet filtering services in the Kingdom and supplies filtering lists to data service providers, who apply them on their internet gateways.
Interkey Intelligent DPI supports that work with application classification, content filtering to meet national regulatory requirements, a URL library with support for third-party interconnection defined in the integration plan, policy execution and reporting. Each rule can run in report-only mode first. See ISP content filtering for national requirements.
Fixed and mobile networks at national scale
- Traffic intake.Designed for Tbps-scale volumes across fixed and mobile networks.
- Reliability.Full-mesh interconnection between the control plane and the user plane, with multi-level disaster recovery.
- Placement.Out-of-band, the platform classifies and reports without touching the forwarding path. Inline, policies can act on traffic. Most operators start out-of-band, and a failover test comes before inline go-live.
- Integration.The connection to your 5G core and your policy and charging architecture is defined during scoping and documented in the integration plan.
See also DPI for mobile operators and Deep packet inspection for ISPs.
Localisation, integration and support from Riyadh
Interkey's team in Riyadh handles localisation to your traffic mix, application set and reporting obligations, integration with your policy, billing, security and reporting systems, and support in Arabic and English. The classification model is retrained automatically, which keeps the load on small teams low.
The decision at each step stays with the operator: what runs, when to move inline, and which rules are approved.
What to bring to a first scoping meeting
- Your network points.Which parts of the network are covered in the first phase, fixed, mobile or both.
- Your obligations.The application classes your regulatory or licence obligations cover, and which reports show that you meet them.
- Your architecture.The policy and charging architecture and enforcement points, and the reporting and security systems that results must reach.
- Your data rules.Retention, access, and whether everything must stay in the Kingdom.
- Your timeline.Whether you start with a proof of concept out-of-band, and when an inline decision is due.
Bringing these answers lets the first meeting settle scope and acceptance criteria, instead of spending it on discovery.
Evaluating a DPI supplier in the Kingdom
1. Agree written acceptance criteria.Which classes are tested, on which traffic, how results are measured and what counts as a pass.
2. Classify out-of-band on verified traffic.Measure false positives as carefully as detection, on your own traffic.
3. Test rules in report-only mode.Enforcement follows only after classification has proven itself.
For the structure of a tender, see DPI RFP requirements.
Questions about DPI in Saudi Arabia
Can Interkey Intelligent DPI run entirely in the Kingdom?
Who supports it, and in which language?
Does it work on encrypted traffic?
Does it work on fixed and mobile networks?
Do we need an inline deployment?
How is it priced?
Proof of concept in three phases
Written acceptance criteria.Agree which rules are tested, on which traffic and subscriber groups, how results are measured and what counts as a pass.
Out-of-band classification against verified traffic.Measure false positives as carefully as detection for every class the rules depend on.
Report-only policy, then the inline decision.Each rule shows what it would have done; enforcement follows only after classification has proven itself.
Discuss DPI for your network
Tell us what kind of organisation you are, which networks are in scope, and your timeline. Our team in Riyadh replies in Arabic or English.
- Our engineers read your request
- We agree the scope of a technical session
- You see the product on a use case you choose