Skip to content

Data integration for digital agencies

Agency data integration that pays.

Your agents build the app in days. The client's data still takes weeks.

“Send us whatever your IT can export” becomes a promise you can price. For agencies that build data-heavy apps for industrial and B2B clients.

Partner agencies build and run the workflows themselves. The CLI is free on npm.

In production at industrial companies since 2022, from steel to eyewear.

  • voestalpine
  • Mehler Elektrotechnik
  • STRASSER Steine
  • LiSEC
  • Silhouette
  • Lumeso
The problem

Agents made the app code fast. The data path still eats the margin.

  • One-offs

    PIM dumps, ERP exports, Excel files nobody owns. Every client's data is a special case.

  • Overruns

    The estimate assumed clean data. The extra days land in the data path, after the price is fixed.

  • Handover

    Import scripts only one developer understands. Agent-written ones, nobody reviewed.

Why

The hard part of an app was never the code. It's the data.

Agencies should sell ideas, UX and engineering. Not the same data plumbing, rebuilt for every client. Agents made app code faster for everyone. The difference between agencies now is how fast, and how safely, they get a client's data into shape.

How

The client's mess, as a workflow you can show

  1. Built once, reused

    Models, workflows and quality rules are JSON files in your repo. The second catalog starts where the first ended.

  2. Agents stage, leads approve

    Workflows run on a dev runner before they reach the client. The Console canvas edits the same files the agent writes.

  3. A system, not scripts

    Every step is visible with its own result. That is what you hand over, and what another developer can pick up.

Workflow · product-syncdcupl workflow test --file sync.workflow-v3.json --runner dev-runner
Run status: Done
  1. Sync request
    trigger-request
    fired
  2. PIM export
    azure-files
    done
  3. ERP prices
    request
    done
  4. Join and clean
    script
    done
  5. Product data
    dcupl-files
    done
  6. Respond
    response-status
    done
trace · run on dev runner
  1. trigger-request fired
  2. azure-files running
  3. azure-files done
  4. request running
  5. request done
  6. script running
  7. script done
  8. dcupl-files running
  9. dcupl-files done
  10. response-status running
  11. response-status done
What

A client project with dcupl

  1. 1

    Pitch: PoC on the client's real export

    Profile the data before the offer, while surprises are still cheap.

  2. 2

    Build: Developer and agent, one model

    Frontend via SDK, backends via the dcupl REST API.

  3. 3

    Go-live: Runs where the client wants it

    On the client's infrastructure, or hosted.

  4. 4

    Run: New sources, new consumers

    Add an export as a workflow, connect the client's agents via MCP where it is turned on.

dcupldcupl Console · Workflows
Workflow run in the dcupl Console: data integration for digital agencies
What you hand over: a workflow your client's team can open, run and trace in the Console.

digiSTONE: ordering stone worktops as simply as in a web shop

Partner case · Netural × STRASSER Steine

Kitchen studios, furniture stores and joineries order from Central Europe's market leader every day, on a dcupl model decoupled from the source systems.

Read the case

Agencies delivering with dcupl

  • NeturalLinz · B2B platforms, e-commerce

Your client runs the application on a plan of their own. What the plans cover: dcupl pricing →

Latest insights

All insights →
Three rows, each with a change, a staged state and a production state: the CLI with built false and dcupl app build, a workflow variant and promote to base, and a REST API instance with status updating.

NewInsight · Data governance · November 5, 2026

Stage, build, approve: why nothing in dcupl happens by surprise

The CLI stages before it builds. A workflow variant runs on a dev runner before it is promoted. An API instance serves the old data until the update is done. One rule, three places, and why it matters when agents write the changes.

Bring the messiest export you have.