Our platform

ddash is the platform we built doing this work.

ddash connects systems, normalizes the data between them, orchestrates the processes that span them, and carries the governance that makes AI deployable on top. It is built, run and supported by RPR — a platform, not a license we resell.

How it is put together

What it does

Four jobs, in the order they have to happen.

Each depends on the one beneath it. That ordering is the whole design: you cannot govern data you have not normalized, and you cannot normalize data you have not connected.

  1. Connect

    Adapters and event-driven bridges into the systems already running the business — including the ones with no usable API, captured without modifying them.

  2. Normalize

    Deduplication, structure and reconciliation applied continuously, so the data stays usable as the business changes rather than degrading after the first cleanup.

  3. Orchestrate

    Processes that span several systems, with sequencing, state and sensible behavior when step three fails after steps one and two already committed.

  4. Govern

    Policy, lineage and traceable records applied across every layer — which is what makes governed AI deployment possible on top rather than an afterthought beside it.

Architecture

A substrate, not a stage in a pipeline.

Source systems stay exactly as they are. ddash sits above them and beneath everything the business actually uses — with governance running the full height rather than occupying one layer.

The ddash platform in layers. Source systems at the base feed a connect layer, then normalization, then orchestration, then the automations, agents, dashboards and models the business uses. Governance and lineage run through every layer rather than sitting at one stage.

How it is deployed

One dedicated instance per customer.

  • Its own server, its own databases, its own credentials — no shared tenancy
  • Containerized and modular, so capability is added without redeploying the estate
  • Cloud, on-premise or hybrid, depending on where your data is allowed to live
  • Monitored and operated by the engineers who built it
  • Your data stays yours, and leaves with you in a usable form

Straight answers

The four questions we always get.

Why does a services firm have a platform?
Because we kept building the same foundation. After enough engagements that all needed connectors, a normalization layer, orchestration and an audit record, building it once properly was cheaper than rebuilding it badly each time. ddash is the result, and it is why an engagement can start from a working substrate rather than an empty repository.
Is ddash a product I license?
It is the platform RPR deploys and operates as part of an engagement — not a self-serve subscription you administer yourself. Each customer gets their own dedicated instance, and we run it.
What happens to our data?
It stays in your single-tenant environment. No pooled data, no shared tenancy, and it remains yours — including on exit. We will export it in a usable form if the relationship ends.
Does it lock us into a model vendor?
No. Governance, policy and the decision record sit around the model rather than inside any provider, so providers can be changed or combined without losing history.

See it against your own systems.

The useful version of this conversation is not a demo of ddash in the abstract — it is us looking at what you run and telling you what connecting it would actually involve.