Platforms
Platforms we deploy, and products we are building
Two of these are partner platforms we deploy, integrate and support. Two are our own software, still being defined. Every card states which it is and how far along it is.
Introduction
Platforms introduction
What is on this page, and what each status actually means.
We work with platforms from two directions. Some are commercial products from our technology partners, which we deploy, integrate with installed systems and support locally. Others are software we are building ourselves, which is a different kind of commitment and carries a different kind of honesty about timing.
The distinction matters when you are deciding what to rely on. A partner platform has a roadmap and a support model that exist independently of us. A product of ours that is still being defined has neither yet, and saying so is more useful than implying otherwise.
Most of the value in either case comes from integration rather than from the platform itself. A platform that cannot exchange data with the controllers, meters and management software already on site is a second silo, however good it is on its own.
Status labels mean specific things. Available: in commercial use and deployable now. Pilot: running in a limited deployment to learn how it behaves. In development: being built, with no committed release. Coming soon: release expected but not yet made. Concept: scope still being defined, with nothing committed. Every card shows its status as text, not only as a colour.
Partners
Partner platforms
Commercial platforms from our technology partners, deployed and supported by ZouhThings.
- AvailablePartner platform
MingoThings Mobility
Provided by MingoThings
Smart mobility and fleet management platform from our partnership in Spain. ZouhThings deploys, integrates and supports it.
- Fleet and mobility operations, including vehicle condition rather than position alone.
- Deployed and integrated locally by ZouhThings.
- Demonstrated live at TEXPO rather than presented as slides.
- AvailablePartner platform
thethings.io
Provided by thethings.io
IoT platform used for connectivity, device management and monitoring. ZouhThings builds and integrates solutions on it.
- Device connectivity, management and monitoring across deployments.
- The platform layer beneath much of our IoT work.
- Demonstrated live at TEXPO.
Our software
ZouhThings products
Software we are building ourselves.
- In developmentZouhThings product
HalaHub
Provided by ZouhThings
Syria's all-in-one digital services platform, connecting people with trusted providers across transportation, healthcare, home services, shopping, jobs, real estate, payments, and local businesses.
- In developmentZouhThings product
Nama
Provided by ZouhThings
A digital growth platform helping Syrian businesses attract customers, increase sales, and accelerate digital transformation.
The statuses shown for our own products are development statuses, not commercial positions. Neither product has a published scope, launch date, price or support commitment, and nothing on this page should be read as a statement that either is available to buy or deploy. Each status is read from that product's own page, so it cannot be overstated here — and it will change there first when it changes.
In progress
Projects in development
Internal projects that are not yet products.
No internal project is published here yet. Work that has not reached the point of being described as a product does not appear on this page — an empty section means exactly that, rather than work being withheld.
Integration
Platform integration capabilities
What we do with a platform once it is chosen, which is usually where the effort goes.
Connecting to installed systems
Making a platform exchange data with the controllers, meters and management software already on site, through whatever interface those systems actually expose.
Device and protocol integration
Bringing field equipment onto a platform, including older devices that have to be instrumented without being replaced.
Normalising data between sources
Reconciling readings that arrive in different units, intervals and timestamps, so one view can present them together.
Alert design and routing
Deciding what counts as an alert, at what confidence, and who receives it — because an alert with no named owner is not configured.
Identity, access and segmentation
Device identity, role-based access and separation between a monitoring layer and anything that can actuate equipment.
Offline behaviour and resynchronisation
Local buffering when connectivity drops, with observed and received times kept separate so a backlog is not read as a live event.
Next step
See a platform running
We would rather show a platform working with real data flows than describe it. For our own products, a conversation is more useful than a demonstration at this stage.