Neomir
Architecture

Optimized for Data Security

Part of the Neomir philosophy is to live transparency. That's why we publicly share our architecture.

Priorities

We carefully designed our architecture to optimize for the following priorities (in order of importance):

Data Security

The top priority: Your data must be protected. That's why our architecture prevents any customer data exposure by design: By making sure your data never leaves your own infrastructure.

Maintainability

We must be able to publish security updates and new features quickly and efficiently. That's why we host the application ourselves - and take care of maintenance for you.

Ease of Use

Using Neomir should be a breeze. Log in, connect your data sources and start monitoring your data quality. That's why we intentionally keep the application lightweight and easy to use.

Data Flows

Let's dive into the details and look at the data flows. We differentiate between raw data and metadata:

Raw Data
For raw data, Neomir follows a strict "Information Barrier": Neomir infrastructure never sees, processes or stores your systems raw data.
Raw Data
Metadata
For Neomir to work, we must save some metadata. All metadata is encrypted at rest with AES-256 and in transit via TLS.
Metadata

Pleasant Side Effects

This architecture has multiple unintended, but positive side effects that make Neomir an even better product:

Enabler for Free Trials

Ever wondered why we're the only ones offering a free trial? It's because we're the only ones with an architecture that doesn't require you to install anything on your infrastructure.

Erasing Headaches

Many DQ solutions require you to somehow move your data to them - even if they're on-prem. That often causes a lot of work and headaches. With Neomir, you can skip that.

More Speed, Less Pain

Processing your data close to where it already lives (=source systems in your infrastructure) also makes things much faster - and you don't have to fight with firewall issues.