Your systems were never designed to talk to each other.
Dataflow Dojo is an integration platform that makes them. It translates between them, tracks every record that passes through, and tells you the moment one goes missing — without replacing anything you already run.
Already speaks to
What it looks like
A complete integration platform for your whole system estate — one pipeline at a time
Systems that send
Housing management
Raises the record
Contractor portal
Sends updated photos
Spreadsheet or file drop
Overnight, from a client SFTP
Materials supplier
Sends an invoice
In
Communications
Email · Push notifications · Teams · Slack · SMS
Every step recorded, every record kept
Reference data
codes · priorities · service levels
Logging and auditing
every run · every change · every retry
Out
Systems that receive
Field service
Gets what it needs to act on
Finance
Gets what it costs
Reporting
Gets the numbers behind it
The customer
Gets an arrival time and a tracking link, via Glympse
Every step has its own connection and its own credentials, so a pipeline is not limited to a pair of systems. Nothing is replaced and nothing moves: each system carries on as it is, and the work of making them agree happens in between.
How it works
Every integration is built from the same five steps
Not every interface needs all five, and they do not always run in this order. You choose which steps an interface uses, how they are sequenced, and what should happen if one of them fails — which is why the second interface costs less than the first.
Collect
Step 1 of 5
We take the data exactly as the other system sends it, and keep that original untouched.
Each step carries its own connection and its own credentials, so a single interface is not limited to two systems — it can take work from one and deliver it to several, in the order you set.
Connections
A library that scales with your IT environment
Each system we support has a ready-made connection, so most of the work is already done before a project starts. Adding one does not disturb the systems already running.
Exactly Right Now
Repairs management
Theia360
Virtual tours and digital twins
Microsoft Dynamics 365
Dataverse / Power Platform
Power Platform
Low-code apps and automation
NEC Housing
Housing management
MRI Orchard
Housing management
Open Housing
Housing management
Civica Cx
Housing management
Capita
Housing management
Aareon
Housing management
Plentific
Repairs marketplace
Totalmobile
Field service
Advanced DRS
Dynamic scheduling
MoreIQ
Scheduling
Accuserv
Repairs management
Microsoft SharePoint
Document management
Business Central
Finance and ERP
Xero
Accounting
Twilio
Messaging
Keyfax
Repairs diagnostics
Glympse
Arrival tracking and ETAs
Plus interfaces built to an organisation's own specification.
And the ways it connects
Dataflow Dojo can consume from and export to many different types of connection.
Web services
File transfer
Databases
Cloud storage
Documents
Messaging
Error handling
You can see exactly where it went wrong
Every item keeps a copy of itself at each step. When something does not arrive, the answer is on one screen.
Record 4821
Failed at Sent
Arrived
Understood
Translated
Sent
Answered
Resolved
WHAT WENT WRONG
The receiving system did not recognise the priority code.
Fix the translation, send it again, say why.
One bad item
Does not have to stop the other nine hundred. You decide, per interface.
Every item
Carries its own error, and how many times it has been tried.
Every run
Says what went wrong in enough detail to act on it, without going to the logs.
Honest status
A run that half-worked reports as half-worked. Nothing is quietly marked successful.
So what?
There are plenty of integration platforms. What is good about this one?
Most of them will get data from one system into another. That part is not the hard bit, and it is not where the cost lives. An interface is not finished the day it first works — someone has to live with it for years afterwards, and that is what the rest of this is for.
Fix it and send it again
When something fails, correct the cause and put the item back through — no re-keying, no asking the other side to resend. Whoever did it has to say why, and that note stays with the record.
Runs on your timetable
Overnight, every fifteen minutes, on demand, or the moment another system calls in. Whichever it was, the history says so.
Tells the right people
Alerts go by email, text, Teams or into your own systems — and not only when things break. You choose what is worth knowing about.
Safe to hand over
Passwords and keys are encrypted and held apart from the configuration, so the people who build an interface never need to see the credentials behind it.
Nothing changes quietly
Every change to how an interface works is recorded — what it was, what it became, who did it and when. So is every item anyone reprocesses.
Runs where you need it to
Hosted by us, or deployed into your own environment when your security policies or data rules require it. The platform is the same either way — where it sits is a decision you get to make, not one made for you.
Looks after its own history
Finished work moves into long-term storage on a schedule and stays searchable, so the system does not slow down as the years add up.
Reporting for whoever asks
What ran, what failed, what is waiting to be looked at — on screen for the team who support it, and as reports shaped to whoever needs them. The people who ask for numbers are rarely the people watching the screen.
Watch it happen
Progress appears on screen as it goes, so an overnight run is something you can look in on rather than find out about in the morning.
Always someone's name against it
Every record shows who set it up and who last touched it — so "when did this change and who changed it" is a question with an answer.
In their words
What the people who run it say
Housing is a small sector. The quickest way to find out whether we are any good is to ask someone who already works with us.
“Dataflow Dojo gave us the visibility and control we needed. Repairs are faster, data is cleaner and our teams can focus on residents, not workarounds.”
Ben Marsden
CIO, Cardo Group
Every dojo has a master
The Integration Master
The Dataflow Dojo is where you learn your craft from others who have mastered it. Our Integration Master leads the dojo, and he has seen all the integration complexities before.
A code that means one thing to the system that sent it, and something else entirely to the one receiving it.
Dates arriving as text, in a format nobody ever agreed.
A field that takes a number one day and a name the next.
Systems so old they never validated anything — they just passed the problem on.
He has seen the ones that work, too. Running on technologies most people stopped learning years ago, kept going by a handful of veterans who know exactly why that field has to be eleven characters and what breaks if it is twelve.
That experience is what the product is built out of. You should never be the one guessing. Whether you are connecting a system for the first time or working out what happened to the one that failed at three in the morning, he is there to show you the way through.
Cut through complex integration like a master in the dojo.
Bring us the interface nobody wants to build again
Show us the one that keeps going wrong. We will follow one of your records all the way through, and show you what your team would see on the day it fails.