Datastreams
    Co-creation

    Turn domain expertise into
    an operable data service.

    Your domain expertise becomes a running data service, built with Dutch-designed Datastreams. Agree the rules once and let the runtime apply them consistently across your information network.

    Bring an operationSee the reference use case

    Pure Dutch design. Your choice of infrastructure. No mandatory Big Tech services in the core runtime.

    A domain expert and runtime specialist map, test and approve a mobility operation before reusing it across organisations.
    Business benefitTurn expert knowledge into a reusable servicePartners agree, test and approve one operating model, then reuse it without rebuilding the same logic for every organisation.

    The partnership model

    Domain authority and runtime responsibility stay clear.

    Co-creation is not a generic innovation workshop. It starts with a real operation and ends with explicit ownership of knowledge, configuration, service and change.

    The partner brings the domain

    Business rules, regulatory realities, users, exceptions and access to a representative operation.

    Datastreams brings the runtime

    Stream contracts, execution, state, policy, adapters, evidence and the managed operating model.

    Together we create a repeatable service

    A verified configuration and interface that can move from one implementation to a reusable domain pattern.

    Dutch research, practical collaboration

    Built on research. Developed with people who know the domain.

    Datastreams has been developed since 2014, building on Dutch research into context-aware information services. Today, co-creation connects that foundation to shared meaning, clear responsibilities and real business operations.

    TU/e, Eindhoven University of Technology

    Research roots · TU/e

    Context has been central from the start.

    The CAPA programme at Eindhoven University of Technology (2011–2015) explored context awareness in predictive analytics. That research helped lay the foundation for Datastreams development from 2014.

    Read the CAPA extract (PDF)
    HAN University of Applied Sciences

    HAN & DEMAND

    Shared meaning across organisations.

    Our intensive collaboration with HAN and the DEMAND network addresses information systems in ecosystems, partnerships and transitions, with data governance and semantics at the centre.

    Explore HAN and DEMAND
    ZonMw

    Care innovation · ZonMw

    From research into everyday care.

    ZonMw funding supports Apotheek Orion’s Benzomoe & Valrisico pilot. Datastreams and DataInbox contribute controlled data services within the pharmacy workflow.

    View the ZonMw programme
    Stijn Hoppenbrouwers

    HAN · DEMAND

    Stijn Hoppenbrouwers

    Lector Data & Knowledge Engineering

    Business benefitGive AI explicit business meaningStijn and his team at HAN and within DEMAND contribute to the further exploration of data semantics. Datastreams’ foundation in TU/e research provides a strong basis for this work: helping AI operate with explicit business meaning, shared concepts and context.
    Rolf de Jong

    APPSS innovation team

    Rolf de Jong

    Former CTO of AFAS · business software and modelling

    Business benefitBusiness software shaped by your way of workingRolf brings enterprise software and model-driven development expertise to the APPSS collaboration. This connects the Datastreams runtime to applications built around a company’s business model, rules and everyday work.

    Research partnerships and project funding support development; Datastreams remains responsible for product validation and operational claims.

    How co-creation works

    From one real operation to a reusable service.

    Each stage produces something that can be inspected and accepted before the partnership takes on more scope.

    1. 01

      Map

      Describe one recurring operation from source and context to permitted outcome and evidence.

    2. 02

      Prove

      Run it with representative data and verify rules, exceptions, responsibilities and resource behaviour.

    3. 03

      Productise

      Separate organisation-specific choices from the reusable domain configuration, adapters and interface.

    4. 04

      Operate

      Agree deployment, support, updates, change control and commercial responsibilities before scaling.

    Before productisation

    Prove the operation before making market claims.

    A configuration becomes a product only after the team has verified the data contract, exception handling, authority boundaries, runtime behaviour and support model with representative conditions.

    • A named business outcome and evidence owner
    • Representative events, volumes and failure conditions
    • Verified adapters and substitution boundaries
    • Explicit data, IP and commercial responsibilities
    • A deployment, update and incident-service agreement

    Bring the operation your sector still solves the hard way.

    We will separate domain knowledge, runtime capability and partnership assumptions, then define the smallest proof that can validate all three.

    Start the mapping