Local doesn't mean isolated.
SharePoint, SAP, internal databases — the data for your analyses already exists. It just sits in a different system. DMAIC.io connects to it inside your own network.
The boundary is your network, not your browser.
Data stays in the network
The connection runs between your systems and your browser. No intermediate storage outside.
No cloud stopover
No DMAIC.io backend can see your data — there simply isn't one on our side.
Runs on your infrastructure
The application is served from your own network. What runs there is under your control.
Work together, without your data leaving your organisation.
Several people work on the same project at once, and changes appear live for everyone else. Microsoft 365 carries the synchronisation — infrastructure you already run. No DMAIC.io server is needed for it: the shared state lives in your own storage, not with us.
MS SharePoint
The project sits in your document library. Who may open and change it follows the permissions already set there.
MS Excel 365
Maintain measurement series in the tool your team knows, analyse them in DMAIC.io. Both sides see the same state, in real time.
Further integrations
Running something else? Additional connections are straightforward to add, by arrangement.
Where your data already is.
Which systems make sense depends on your landscape. These are the usual ones.
SharePoint
Read measurement series and inspection records from document libraries — right where your teams file them anyway. Access through the permissions that already exist.
SAP
Take key figures and transaction data from the leading system instead of exporting and passing them around. Read-only, within the views you release.
SQL databases
MS SQL, Oracle, PostgreSQL and others. The data source stays where it is — DMAIC.io queries it.
Network drives & exports
Bind CSV and Excel folders on file servers so nobody has to copy files back and forth.
On-premise deployment
Delivered into your network, onto your server, behind your firewall. Fully without internet access if needed.
Three steps, no procurement marathon.
Conversation
Which systems, which data, which analyses. Half an hour is usually enough to see whether it fits.
Review the landscape
Access paths, permissions, feasibility — together with the people who run those systems.
Implementation in your network
Connection and operation on your side. What we build stays verifiable, because the code stays open.
Questions your IT security will ask.
Existing access paths
Data access typically runs through the access infrastructure you already have — SharePoint, for example. No separate user or permission management required.
Open source code
The application can be read and audited. Your IT security doesn't have to take anyone's word for it.
No callback channel
No telemetry, no license server check, no usage statistics leaving the building.
Licensing
The application is licensed under AGPL-3.0. Different models for corporate use on request.
Let's talk about your system landscape.
Tell us which systems are in play and what you want to get out of them. We'll tell you what's feasible — and what isn't.
Write to us → ← Back to the landing page