Water resources & flood management

Water resources and flood management in one working platform.

CatchmentOS connects data, model configuration, hydrologic and hydraulic analysis, water operations, scenarios and decision support in a single workflow, so the work of getting to an answer holds together from start to finish.

Technical prototype and customer-validation stage

The problem

The analysis is connected. The tools are not.

Water-resources work moves constantly between terrain and network data, GIS, hydrologic and hydraulic models, operational records and reporting. Each of those tools is good at its own job. The cost sits in the space between them.

  • Context is rebuilt every time

    The same watershed gets reassembled for each study, each model and each review, because no single place holds the whole picture.

  • Scenarios drift apart

    Variants accumulate across folders and file names. Knowing which inputs produced which result becomes an exercise in recollection.

  • Results travel without their history

    A figure reaches a decision-maker separated from the assumptions behind it, which makes questions later in a project expensive to answer.

The difficulty is fragmentation across the workflow, not the quality of any individual tool. CatchmentOS is being built to close that gap with a traceable, scenario-driven working environment.

The platform

One continuous workflow, from data to decision.

Four stages of the same project, held in one context rather than four disconnected environments.

  1. 01

    Connect data

    Bring geospatial, environmental, observational and modeling data together in a single project context, with its origin and meaning carried alongside it.

  2. 02

    Build & configure

    Describe the watershed or system, organize modeling inputs and prepare scenarios in one working environment instead of several disconnected ones.

  3. 03

    Model & simulate

    Run hydrologic, hydraulic and water-management analysis against that shared project, without translating between separate tools at every step.

  4. 04

    Compare & decide

    Set scenarios side by side, inspect what changed and why, and carry results into engineering, planning, operations and decision support.

Who it's for

Built around how water-resources teams actually work.

CatchmentOS is being designed for workflows across engineering, public-sector, operational and research settings.

  • Engineering consultants

    Teams running studies and designs across many basins and clients, where set-up time and reviewable assumptions decide project economics.

  • Flood & stormwater programs

    Programs assessing flood behavior, mitigation options and drainage performance, and needing scenarios that stay comparable over time.

  • Water agencies & utilities

    Organizations balancing supply, demand and allocation, where analysis has to connect to planning decisions and public accountability.

  • Reservoir & basin operators

    Operational teams evaluating release and storage strategies against changing conditions, on schedules measured in hours rather than months.

  • Researchers & technical teams

    Groups developing and testing methods who want reproducible configurations and a shared basis for comparison.

Why CatchmentOS

Fewer handoffs. Clearer provenance.

One catchment, four questions. The whole network as one systemEvery input behind a result, traced upstreamThe terrain and divide the model sits onA second run laid over the first
  • Connected workflows

    Data, configuration, analysis and results stay part of one project rather than four separate efforts stitched together at the end.

  • Traceable by default

    Inputs, assumptions and scenarios stay attached to the results they produced, so a figure can be explained months after it was made.

  • Integrated modeling context

    Hydrologic, hydraulic and water-management questions are asked against a shared description of the system instead of parallel ones.

  • Comparison built in

    Scenarios are organized for side-by-side reading, which is the form the work usually needs to take when a decision is being made.

Current stage

Technical prototype and customer validation.

  • Technical prototype
  • Customer validation

CatchmentOS is at technical prototype and customer-validation stage. Core technical capabilities are under active development while we continue learning from water-resources professionals across engineering, public-sector, operational and research settings.

The current focus is strengthening the platform through realistic watershed-scale testing, infrastructure development, and continued feedback from practitioners.

We describe the platform as it is today. CatchmentOS is not presented as a certified or approved replacement for established commercial or government modeling software, and is not claimed to be in operational deployment.

Next milestone

Scaling the development environment.

The next milestone is a secure cloud-hosted environment able to support realistic watershed-scale model testing, large geospatial datasets, and product demonstrations for the professionals we are working with.

Team

Built by people who do this work.

CatchmentOS is developed by a small team working across hydrology, hydraulics and software engineering.

  • Portrait of Aydin Bakhtar

    Aydin Bakhtar

    Co-founder & CTO

    Hydroinformatics and full-stack engineering. Builds the data and modeling side of the platform, working from a background in computational hydrology.

    • Hydroinformatics
    • Computational hydrology
    • Hydrometeorology
    • Software engineering
  • Portrait of Afshin Shayeghi

    Afshin Shayeghi

    Co-founder & CEO

    Hydrologist, and the team's main point of contact with practitioners. Leads customer discovery and partnerships, and carries what comes out of those conversations back into the work.

    • Hydrology
    • Water-resources modeling
    • Customer discovery
    • Partnerships
  • Portrait of Javad Teymoori

    Javad Teymoori

    Founding Engineer, Hydraulics

    Hydrologist by training, working across hydrodynamics and hydraulic modeling with a focus on coastal flood analysis.

    • Hydrodynamics
    • Hydraulic modeling
    • Coastal flood
    • Hydrology

Contact

Let's talk about better water-modeling workflows.

For technical discussions, partnership conversations, customer-discovery interviews or general information, we would be glad to hear from you.

We are actively speaking with engineering consultants, agencies, operators and research groups about how this work is done today.