The anonymization server inside your own network
The anonym.plus engine, installed as a server in your own network. From 10 client connections upwards, open-ended, scaled by the hardware you give it — and set up with you.
One server in your network, every client pointed at it
Nothing about the detection changes. What changes is where it runs: on hardware you own, inside the boundary your auditor already draws.
Your server
The engine runs on hardware in your network, and the text does not leave your network to be processed. After the one-time activation, the server runs without an internet connection.
Your clients
For your own operation: the web app, the desktop app, the Microsoft Office and LibreOffice add-ins, the Chrome extension, the Nextcloud apps, the REST API and the MCP server — all pointed at your server.
Your numbers
Your administrator sets how many client connections the licence carries: from 10 upwards, with no ceiling. How much the server handles depends on the hardware you run it on.
The data stays in your house
Hospital groups, banks, insurers and public authorities write the same clause into their tenders: the data may not leave the building. A cloud service cannot answer it. A server in your own network answers it by the way it is built.
No text sent out for processing
The processing happens on your hardware, under your operation. No document is sent to us, or to anyone else, to be anonymized.
An answer for the tender
Where the procurement says the data must stay on your premises, this is a configuration that can answer that clause — the anonym.plus engine, inside your perimeter.
Reversible when it has to be
5 protection methods, one of them reversible, so the authorised reader gets the plaintext back. Pseudonymized data remains personal data under the GDPR.
The engine inside your product
If you build software for hospitals, law firms or public bodies, your customers ask you the question they ask us: where does the text go? Enterprise lets you answer it inside their own network.
REST and MCP
Your application calls the server over the REST API; AI assistants and agents use the MCP server. The engine sits in your customer’s network, next to your product.
Your customers’ environments
A server per customer site or one for a whole estate, sized to the hardware there, with the number of client connections set in each licence.
Under your name
White-label is a custom build on anonym.plus Enterprise, delivered by anonymize.solutions as a service rather than a switch in the product. What the service covers.
Hosted, on one machine, or on your own server
| anonym.legal | anonym.plus | anonym.plus Enterprise | |
|---|---|---|---|
| Where the text is processed | Our servers at Hetzner, Falkenstein, Germany | On the machine it is installed on | On your server, inside your network |
| Licence | Monthly, billed in tokens | Bought once, for a set number of machines by tier | Issued by hand, by number of client connections |
| Scale | Per account | The machines the licence covers | From 10 client connections, open-ended, as far as your hardware goes |
| Ways in | Web, desktop, add-ins, Chrome, Nextcloud, REST, MCP | The desktop client; with an Enterprise licence, a local API on that machine | Web, desktop, add-ins, Chrome, Nextcloud, REST, MCP — pointed at your server |
| How you get it | Self-service at anonym.legal | Self-service at anonym.plus | Through us, set up with you |
From 10 client connections, open-ended. There is no price list and no checkout: we make an offer by scope, and the licence is issued by hand. Setting up the server, connecting your clients and building it into your own software is implementation and scaling.
Tell us the size of your network
How many clients, and where the server may stand. Those two answers shape the offer.