We were the people buying this, and it never existed

Why this exists

We spent our careers inside enterprise IT in Norway, working in architecture, delivery, consulting and sourcing for some of the largest companies in the country.

Integration was the bottleneck in almost every programme we touched. Migrations slipped because the re-mapping took longer than the migration itself. Projects sat waiting while two systems disagreed about what counted as a customer. Capable engineers spent most of the year keeping connections alive that they had already built once.

The method has barely changed in twenty years. Someone writes down which field means what, and someone else keeps that document alive for the rest of the system’s life. The products sold into this space mostly make the writing faster. None of them remove the need for it.

masterVantage is our attempt at removing the document altogether. The engine works out what the data means, and carries on working it out as the systems underneath it change.

Where we are

Early. The product is in paid production use today with an enterprise customer, and the technology is patent-pending in the United States. The team is small enough that the person you talk to is the person who builds the thing.

That also means we are not the safe procurement choice and we are not going to pretend we are. If your process requires a supplier with a long reference list, we will not get through it yet. If you want a specific problem solved by the people who wrote the code, that part we can do.

We are aware of what we are asking. A small company wants to sit in the middle of your data flows. So we build in a way that limits how much you have to trust us: the engine runs on your infrastructure and keeps running whether or not we exist, and we will put source code escrow into the contract so you can take over the code if something happens to us. Ask for it and you will get it.