Built by someone who works inside Business Central
Midstream Integrations started with real problems: Business Central doing almost what a business needed, and data stuck where other systems couldn't reach it.
Why Midstream
Hi, I'm Avery Enders. I write AL extensions for Business Central SaaS and the Python services that connect it to Linux servers. I started building these tools to remove manual work I saw every day: exports, re-keying, and gaps between systems that should have been talking to each other.
The name says what we do. "Midstream" is the space between your systems, where data has to move reliably and securely. That's the part we build.
We publish our tools as open source because you should be able to see what software does before it touches your financial data, and because you shouldn't be locked in to the person who wrote it.
How we work
Plain language
You'll always know what we're building, why, and what it costs, without needing to read code.
Sandbox first
Nothing touches your live company until you've tested it and signed off.
Security by default
Least-privilege access, secrets kept out of code, and everything logged so you can see what happened.
You own it
Source code and documentation are handed over at the end of every project.
Let's talk about your Business Central setup
A free 30-minute call, no obligation.