The technology industry loves its gold rushes. Every few years, something new captures everyone’s imagination, and suddenly every vendor is scrambling to slap the latest buzzword on their products. After three decades in this business, we’ve learnt to take a different approach.
When mobile apps became mandatory for every enterprise product, we didn’t just shrink our interface to fit a phone screen. We thought hard about why someone would actually need to access their corporate archive on a mobile device, and what security that would require.
Since 2006, EMA has protected archived documents with chained digital signatures. Each signature carries a time stamp and links to the one before, so tampering shows. We never needed a fancy name for it. A bridge isn’t called a “Cross-Water Transportation Enablement Platform”, and we call our chained digital signatures what they are.
When everyone rushed to the cloud, we held back with ARTEC Trusted Cloud as our hosting solution, gathering experience to get it right with EMA Cloud. Today EMA Cloud runs in the region each customer chooses, in data centres certified to ISO 27001 and attested to BSI C5. Each customer gets a fully isolated archive with true zero-knowledge encryption. With EMA Cloud, neither we as the service provider nor the data-centre operators can see your archived data, unless you open a support session yourself. This is how we define enterprise-grade security. Thoughtful architecture, complete implementation, no compromises.
This is how we’ve always operated. Let others rush to market with half-baked implementations. We think it through and then build something that actually solves the problem. Now with AI, I’m watching the same thing play out again. The same rush to implement, the same vendor lock-in dressed up in new clothes, the same fundamental mistakes.
The rush to AI integration
Today, software vendors across our industry are making the same mistake. They’re selecting an AI provider, embedding it directly into their products, and forcing their customers to accept whatever terms, pricing and limitations come with that choice. Your sensitive data flows through their chosen model, processed by their selected provider, under conditions you had no say in determining.
This should sound familiar because we’ve been here before. It’s the same vendor lock-in strategy that has frustrated enterprise customers for decades, just wearing a new costume. The technology changes, but the fundamental problem remains unchanged.
Consider what happens when your vendor’s chosen AI provider triples their prices. With an archive containing years of your business data, the stakes are much higher.
What recourse do you have when new regulations make their data processing methods non-compliant in your jurisdiction? What happens when the AI model they selected becomes obsolete, or when you need capabilities that their provider simply doesn’t offer? What if you’ve invested in developing your own specialised AI models tailored to your industry’s unique requirements?
The answer, unfortunately, is that you’re trapped. You must either accept the limitations or undertake the costly and disruptive process of switching to an entirely different archiving solution. This is precisely the scenario we’ve spent three decades helping our customers avoid.
A different approach
I believe there’s a better way. Instead of dictating which AI tools you must use, EMA gives you open, permission-aware APIs, so you connect the AI you choose and keep control.
Our two APIs let the AI tools you choose search and read your archive. You decide which providers to use, what data they may read, where that processing happens, and how results come back into your work. In your own AI tool, you control the system prompts, the model’s temperature and token use, and what it is allowed to access.
This isn’t just about technical flexibility. It’s about respecting the fundamental principle that your data is yours, and the tools you use to process it should be your choice as well.
How it actually works
The APIs work with the Model Context Protocol (MCP). An MCP server can connect an assistant to EMA, acting as the signed-in user and seeing only what that user may see.
Your AI tool calls EMA, not the other way round. Through the User API it can search, read text and, if you allow it, download originals or write attributes. Each is a separate scope you grant. Need to search documents? That’s the search scope. Want to analyse attributes? The attribute scopes are there. Extracting specific documents for processing? The download scope handles that securely.
These aren’t proprietary connections that lock you into specific providers. They’re standard REST calls that work with any service that can send web requests. We don’t require specific AI providers or models.
Want an on-premises model for sensitive data? Run it in your network and connect it to EMA. Different departments can register different apps, each with its own scopes.
The regulatory maze
Governments worldwide are racing to out-regulate each other on AI. The European Union’s AI Act turns software vendors who embed AI into “AI system providers” with massive compliance obligations. The United States is tackling this with executive orders and agency-specific guidelines. Japan is currently betting on industry self-regulation and that it will all turn out okay. China is regulating the underlying algorithms themselves. And the rest of the world is taking notes, following one approach or another.
With hard-coded AI, you’re tied to your vendor’s compliance strategy. When they become an AI system provider in the EU, you might be one too. When new US guidelines drop, you live with whatever interpretation your vendor chooses.
We draw a clear line here. ARTEC remains an archiving provider. We give you the tools. How and whether you use them is your call.
This matters especially for international operations. Through our federated search feature, you can already build global enterprise archives that respect national boundaries and regulations. The same applies to AI. Need one approach for Europe, another for the US, something different for Asia? When regulations shift, which they inevitably will, simply adapt your AI strategy at the national level and keep moving.
The ARTEC philosophy
Let me be clear about one thing. ARTEC IT Solutions will not become an AI company. We are and remain specialists in archiving, because that’s what we can do and what we do well. You can rely on that. But we also see how AI is changing and simplifying work with archived data. That’s why we’re creating the technical foundations so you can use AI, but on your terms. You retain full control over your data, your processes, your compliance. We provide the tool, you decide how to use it. That’s our understanding of partnership.
Every customer who chooses EMA has had the same promise from us for decades. Your data stays yours, and so do your decisions.
Looking ahead
AI is coming to enterprises, that’s beyond question. The crucial question is how we shape this transformation.
The convenient path for us would have been to decide this for you by selecting an AI solution and building it permanently into EMA. Many of our competitors are currently taking this route, and in the short term it might even appear attractive. A tick in the “Supports AI” box, nice screenshots for the marketing department, job done.
But we know our customers. You’ve built individual processes over years, developed special requirements, established your own compliance standards. Forcing you into a pre-made AI solution would be disrespectful, and short-sighted. Because what’s state-of-the-art today can be outdated tomorrow.
Open APIs are deliberately a different approach. It respects your expertise, your requirements and your future. You decide which AI technology fits your company. You retain control over your data. You remain capable of acting when markets, technologies or regulations change. Whether it’s ChatGPT, Claude, Gemini or whatever comes tomorrow, it can connect through the same APIs. And if you’ve developed your own models, we’re happy to help you connect them.
If thirty years have taught us anything, it’s that you make the best technology decisions yourself. Our job is to give you the necessary tools to do so. No more, but no less either. With EMA’s open APIs, you’re not betting on our AI strategy. Instead, you’re implementing your own. That’s the ARTEC difference. That’s how we’ve built lasting partnerships for three decades. And that’s how we’ll continue serving our customers for decades to come.
Update, September 2026
With AOS 7.20 (September 2026), EMA gained the two APIs this post describes. The System API is for integrations that work with administrator rights, such as migrations, compliance processes or regular reporting. The User API works on behalf of a signed-in user via OAuth 2.0 and sees only what that user may see. A .NET SDK is available for both. The User API comes with every edition of EMA, and the System API with every edition from Business Professional up. They let the AI models of your choice work with EMA, without vendor lock-in. The System API and the User API are the foundation for this approach. With the User API, an AI assistant can search and read only what the signed-in user may see.