Delta Hydro Engineers (Pty) Ltd The Flood Specialists

Solutions / Custom Software

Custom software for water engineering

QGIS plugins, operational dashboards, data pipelines, bespoke applications, and modelling-platform automation. Built around the specific workflow you want to remove friction from — not around a generic product we are trying to sell everyone.

Why in-house expertise matters

Water-engineering software is unusual: the people who know what the tool should do speak hydrology, not software architecture; the people who can build the tool rarely understand the domain. We do both. That means the scoping conversation is short, the build avoids rebuilding things that already exist in QGIS, HEC-RAS, or SCADA, and the handover is to a team that can actually maintain what we shipped.

What we build

Plugins

  • QGIS Plugin Development

    Custom QGIS plugins for hydrological workflows, catchment delineation, floodplain export, and modelling-platform bridges. Delivered as scoped engagements with handover documentation.

Dashboards

  • Dashboard Development

    Operational dashboards for municipalities, water utilities, and mining water managers. Real-time stormwater performance, TSF water balance, reservoir status — built around the data you already collect.

Integrations & automation

  • Data Pipelines & Integration

    Ingest, transform, and serve hydrological, meteorological, and telemetry data. Pipelines that feed models, dashboards, and decisions — engineered for the messiness of real-world water data.

  • Modelling Platform Customisation

    Extensions, scripting, and automation on top of commercial hydraulic modelling platforms. Let your modellers spend time on analysis, not on button-clicking.

Bespoke applications

  • Bespoke Water Engineering Applications

    Custom desktop and web applications for water engineering calculations, design workflows, and compliance reporting. Built around a specific pain point — not a generic platform.

How we work

1. Discovery

We sit with the team that will use the tool and watch the current workflow. The shape of the software follows the shape of the work, not a template. If a scoped-project fits better than a phased engagement — or vice versa — we will say so before we write a proposal.

2. Scope & design note

Inputs, outputs, failure modes, and interop constraints in a short design note. No waterfall document. Your team reviews and pushes back before any code is written.

3. Build in short loops

The intended user tries the tool on their own data as each piece lands. Feedback in days, not at the end. Scope changes surface early, and get costed honestly.

4. Handover

Source code, a short handover document, a demo with the team. An agreed bug-fix window. Ongoing support or extension work scoped separately — never bundled in to keep you tied to us.

Representative engagements

Anonymised to respect client confidentiality. Each one started as a conversation about a workflow that was painful, not about software someone wanted to build.

Who we build for

Tell us what you would build if you had the right tool. We'll tell you whether we can build it, whether something off the shelf would be cheaper, and what a scoped proposal looks like.

Request a scoped proposal