mWater vs WISKI

Short answer: These products overlap, but they are designed around different primary jobs. The right choice depends less on a feature checklist than on the data model, users, workflows, and operating environment you need to support.

mWater is a broad monitoring and management platform built around surveys, mapped sites and assets, recurring field observations, indicators, dashboards, and operational workflows. WISKI is KISTERS' specialist environmental data-management system, built around hydrological and environmental monitoring networks, parameters, and time series.

At a glance

Requirement	mWater	WISKI
Primary strength	Field-to-dashboard programmes for WASH, facilities, assets, services, and inspections	Hydrological and environmental time-series management
Typical data	Surveys, sites, assets, photos, issues, indicators, and administrative areas	Sensor, logger, SCADA, model, laboratory, and monitoring-station data
Field collection	Native offline mobile surveys and mapped asset/site workflows	Available through WISKI modules and extensions
Hydrometric processing	General calculations, integrations, and visualizations	Purpose-built validation, analysis, forecasting, and hydrological workflows
Access model	Core platform is free with unlimited users; optional paid services	Commercial implementation; scope and price are agreed with KISTERS

Choose mWater when

Your programme must collect structured observations from enumerators, district staff, utilities, or community teams, often offline.
You need a shared registry of water points, facilities, customers, or physical assets and want to monitor each one repeatedly over time.
You want surveys, maps, dashboards, indicators, approvals, issues, and workflows in one platform without per-user fees for the core service.
Your national or multi-organization programme needs fine-grained sharing while keeping data ownership with the organizations that manage it.

Choose WISKI when

Your central requirement is authoritative hydrological or environmental time-series management.
You operate dense networks of gauges, sensors, data loggers, SCADA feeds, models, or laboratory systems.
Your specialists require established validation workflows, auditability, rating and flow analysis, forecasting, or regulatory reporting.
You want a commercially implemented, mission-critical environmental data platform with specialist vendor support.

Can they work together?

Yes. A common architecture is to keep high-frequency hydrometric observations and specialist quality control in WISKI while using mWater for field inventories, service monitoring, inspections, programme indicators, and broader operational dashboards. Data can be exchanged through APIs, scheduled exports, or integration pipelines. Decide which system is authoritative for each dataset before building the connection.

Decision guide

If the sentence describing your project begins with “manage a national hydrometric network,” WISKI is likely the closer fit. If it begins with “collect, map, monitor, and act on WASH or service-delivery data,” mWater is likely the closer fit. For programmes spanning both, integration is often better than forcing either product to replace the other's specialist role.

Sources and verification

See the official WISKI overview and the mWater platform overview. Product packaging and commercial terms can change; confirm current requirements with each vendor.