Deployment
Siper runs in two ways: the managed service we operate in Istanbul, or an installation on your own servers. The product is identical in both.
Siper can run in two ways: the managed service we operate in Istanbul, or an installation on your organization’s own servers. This page explains the difference between the two. It does not contain installation steps; an on-premise installation is planned and carried out together with us.
The important part: the product is identical in both. The gateway, masking, and panel are installed as a single whole. An on-premise installation is not a reduced version.
| Managed service | On-premise installation | |
|---|---|---|
| Where it runs | On our infrastructure in Istanbul | On your organization’s servers |
| Who operates it | We do | Your own team |
| Where raw data is processed | In Turkey, on our infrastructure | In your environment |
| Panel, audit trail, categories | Same | Same |
| API contract and masking behavior | Same | Same |
What is the same in both
Masking behavior, the 26 categories, the placeholder format, and the
fail-closed rule do not change. The panel, the audit trail, virtual key
management, and usage charts are the same. The API contract is the same: your
application does not need to know which model it runs against, only the
base_url differs.
This means moving to an on-premise installation, or the other way around to the managed service, does not require changes in your application code.
External model traffic
In both models the Gateway reaches out to the language model provider you select: the request goes to the provider after it has been masked. So an on-premise installation by itself does not mean “nothing leaves”; what leaves is masked text.
If you want a fully closed setup, you choose a model running on your own servers as the provider. Solutions such as vLLM and Ollama expose an OpenAI-compatible interface, so the Gateway connects to them the same way. In that case the request never leaves your network. For provider selection, see Models and providers.
Which one to choose
For most organizations the managed service in Istanbul is the most practical path: installation and operations stay with us, raw data is still processed in Turkey, and only masked text goes to the external model.
The on-premise installation exists for organizations that cannot let data leave their own infrastructure at all. Scope, operational responsibility, and version updates are agreed in the contract; to get started, contact us.
For data retention, the audit trail, and access rules, see Security.