Company
Partners and technology ecosystem
ZouhThings combines local delivery capability with established international technology platforms. This page sets out who those partners are and, just as importantly, what each relationship does and does not cover.
Approach
Why we work through partnerships
Building every layer of a system from scratch is slower, more expensive and harder to support than integrating platforms that already work.
Our customers need systems that run for years, not demonstrations. That argues for proven platform software underneath, and for local engineering on top of it — people in the same time zone who know the deployment and can be reached.
So ZouhThings works as an integrator. Partners provide platform technology; we design the solution, integrate it with the systems an organisation already runs, deploy it, and support it. Neither half works without the other.
We describe these relationships in plain terms. Where a partnership does not grant something, this page does not imply that it does.
Proven platforms, local delivery
Platform software that is already in production elsewhere, deployed and supported by engineers here.
No lock-in by default
We favour platforms with documented integration routes, so a customer is not trapped by our choice of supplier.
Accurate attribution
A partner's technology is described as theirs. We do not present a partner platform as a ZouhThings product.
Only what is agreed
We state what a partnership covers. We do not claim exclusivity, resale rights or territory that has not been granted in writing.
Partners
Strategic partners
The organisations ZouhThings works with directly.
These are technology partnerships. Unless a specific right is stated on a partner's entry, nothing here grants ZouhThings exclusivity, distribution or resale rights, ownership of a partner's technology, or authority to represent a partner in any territory. Partner descriptions are published once the partner has approved the wording.

MingoThings
Strategic technology partnerActivePartner organisationInformation to be supplied
MingoThings
An approved description has not been supplied for this partner yet.
Website link to be confirmed

Mersal Telecom
Solution ecosystem partnerActivePartner organisationInformation to be supplied
Mersal Telecom
An approved description has not been supplied for this partner yet.
Website link to be confirmed
Platforms
Technology platforms
Platform providers whose software ZouhThings builds on, integrates and supports.

thethings.io
Technology platformActivePlatform providerthethings.io provides the IoT platform ZouhThings uses for device connectivity, device management and monitoring. The platform is developed and owned by its provider; ZouhThings builds and integrates solutions on it.
Draft wording — not yet approved by the partner.
Relevant solutions
Relevant platforms
- thethings.io
Website link to be confirmed
For customers
What this means for a customer
The practical effect of an integrator model, rather than the theory of it.
Shorter path to something working
A platform that already exists removes the longest and least predictable part of a project — building the foundation.
A single party accountable for delivery
ZouhThings is responsible for the delivered solution, including the integration work between the platform and existing systems.
Support in the same time zone and language
Operational questions are answered locally, in Arabic or English, by people who worked on the deployment.
Access to platform development
Improvements the platform provider makes reach deployments we support, without a rebuild on our side.
Honest scope
Where a platform does not do something, we say so during design rather than discovering it during deployment.
Integration
How platforms are integrated
A platform only creates value once it reaches the systems where work is planned and recorded.
Most of the engineering on a ZouhThings project sits between a partner platform and the systems an organisation already runs — maintenance, scheduling, asset registers, reporting and identity.
That work is ours, not the platform provider's, and it is described in more detail on the Systems Integration page.
System and data integration
Moving data between a platform and existing enterprise or operational systems, with agreed formats and error handling.
Identity and access
Aligning platform access with the identity model an organisation already operates, where one is in place.
Device and field integration
Selecting, provisioning and connecting field hardware so it reports consistently.
Operational handover
Documentation, training and a defined support route, so the system can be run by the customer's own teams.
Partnering with us
Become a partner
We are interested in platform providers, systems integrators and specialist suppliers whose technology complements what we deliver, particularly where local deployment and support are the missing piece.
Tell us what your technology does and which problems it solves. If there is a fit we will say so, and if there is not we will say that instead.
Getting in touch is a conversation, not an agreement. Any partnership is set out in a separate written agreement, and nothing on this website creates one.
Next step
Talk to us about a project
If you are evaluating a platform or a system, we can walk through what the work would involve.