For ISPs and data service providers
Deep packet inspection for ISPs: filtering, bandwidth and reporting
For an internet service provider, deep packet inspection (DPI) identifies which applications make up subscriber traffic. That one capability supports three jobs: applying the filtering requirements that apply to you at your internet gateways, making bandwidth and capacity decisions on evidence rather than on totals, and reporting to management and the regulator. Interkey Intelligent DPI provides application classification, content filtering to meet national regulatory requirements, policy execution and reporting, on your own infrastructure, with support from Riyadh.
A Saudi product, built by Interkey
For network, NOC and compliance teams at ISPs and data service providers. Reviewed November 2026.
- Filtering:apply the filtering lists that apply to you, with the traffic they refer to identified, including encrypted traffic.
- Bandwidth:see which applications fill your links at peak, so capacity and plan decisions follow real demand.
- Reporting:a network-wide view with drill-down to application and flow, and a reporting layer for regulatory teams.
- For small teams:the classification model is retrained automatically, and integration and support come from a team in Riyadh, in Arabic and English.
Three jobs DPI does for an ISP
| Job | What the ISP needs | What Interkey Intelligent DPI provides |
|---|---|---|
| Filtering | Apply the filtering requirements that apply to you, consistently, at your internet gateways | Application classification, content filtering to meet national regulatory requirements, a URL library, and blocking where your policy and applicable regulation require it |
| Bandwidth and capacity | Know which applications use the bandwidth, where and when, before buying capacity or changing plans | Network- and application-level traffic trends, with drill-down to application and flow |
| Reporting | Describe your traffic and the policies you applied, to management and to the regulator | Live View, real-time policy execution feedback and a reporting layer for regulatory and capacity teams |
In Saudi Arabia, the Communications, Space and Technology Commission (CST) supplies filtering lists to data service providers to apply on their internet gateways. The filtering capability is covered in depth on ISP content filtering for national requirements.
Bandwidth decisions on evidence
Interface counters and flow records tell an ISP how much traffic crossed each link. They do not say which applications that traffic belongs to, and on a network where most traffic is encrypted and many applications share the same common ports, port-based reports cannot reliably place it in the right class. Application classification answers the questions bandwidth decisions depend on:
| Question | What the application view shows |
|---|---|
| Which applications fill our links at peak? | The application mix in the busiest hours, with drill-down to application and flow |
| Is one class growing, or is all traffic growing? | Application-level traffic trends over time |
| Do our plans match how subscribers use the network? | Which application classes your plans and fair-use terms need to account for |
| Did a policy change have the intended effect? | Real-time policy execution feedback |
DPI does not add capacity. It shows where capacity is needed, and in an inline deployment it applies the policies you approve, per application, subscriber group or cell. Which actions those policies take is defined with your team during scoping and set by your policy and applicable regulation.
What a small technical team should check
Many ISPs run their network with a small team, so the effort a platform needs after go-live matters as much as what it can do. Ask every supplier:
- Model upkeep:who keeps classification current as applications change? In Interkey Intelligent DPI, the AI traffic model extracts features from live traffic and is retrained automatically, and Live View results feed back into models and policies.
- Encrypted traffic:is it classified without decryption, and have you seen the results on your own traffic? Interkey Intelligent DPI classifies from handshake structure, packet sizing and timing, and endpoint behaviour.
- Risk at the start:can you begin outside the forwarding path? An out-of-band deployment classifies and reports without sitting in it.
- Integration:who connects the platform to your policy, billing, security and reporting systems? Interkey's team in Riyadh does this as part of the deployment.
- Support:who answers, from where and in which language? Interkey supports the platform from Riyadh, in Arabic and English.
- Sizing and price:is the platform sized for your traffic? Throughput is scoped per deployment, and pricing is quoted per deployment and capacity.
Subscriber data stays under your rules
The platform's output is metadata about applications, traffic volumes and triggered policies. Retention and access are set in the deployment design and the contract, following your data-governance rules. The platform runs on your own infrastructure and can operate entirely in the Kingdom. See DPI data residency, and for what to keep as evidence for the regulator, ISP regulatory compliance.
Start out-of-band, then test in 3 stages
1. Written acceptance criteria.Agree what is tested, on which traffic, how it is measured and what counts as a pass.
2. Out-of-band classification against verified traffic.Measure false positives as carefully as detection: a false positive means a rule acts on traffic it was never meant to touch.
3. Report-only policy, then the inline decision.Filtering and other rules run in report-only mode first; enforcement follows only after classification has proven itself.
See also: How Interkey runs a DPI proof of concept
Questions ISPs ask about deep packet inspection
Why use DPI if we already have flow records?
Does DPI manage bandwidth by itself?
Can it apply the filtering lists we receive?
Do we need an inline deployment?
Does subscriber traffic leave Saudi Arabia?
How is it priced?
Related pages
- ISP content filtering for national requirements
- ISP regulatory compliance
- Network traffic management for telecom operators
- Encrypted traffic classification without decryption
- Deep packet inspection for Saudi telecom networks
- Bandwidth management for ISPs
- DPI in Saudi Arabia
- Quality of experience monitoring
- Service chaining
- Telecom subscriber analytics
- Traffic shaping
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 provider you are, which job comes first (filtering, bandwidth decisions or reporting), roughly how your internet gateways are arranged, 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