One protection. Scope to match your company.
Protect company data, your websites and your AI applications with Corpilus. We agree where to connect the protection and prepare a price for the scope you use.
Corpilus protection
Protection for company data, websites and AI applications. We adapt the scope to what you need to protect and how you use the solution.
Individual pricing — based on scope.
The protection works in the channels it is connected to. Before deployment we go through what is covered and what still needs connecting.
Putting the same protection to work
Protection for your company
Connecting the protection to the tools, websites and applications you already use.
Individual, based on scope
Integration over SDK or API
Building the protection into your own application or into the product you deliver.
Individual, based on the integration
Dedicated server or your own infrastructure
Deployment that follows your requirements for the environment and its administration.
Individual, based on the deployment
What stands behind the price
What affects the price?
The number of protected users, the protected websites and applications, the volume of server-side processing, and the integration the deployment needs. Company size only helps us orient ourselves; on its own it does not set the price.
How do we count the scope?
A protected user is a person who uses the protection, not each of their devices. A protected website or application is one system — language versions, aliases and individual API endpoints are not counted as further applications. Traffic volume is the agreed range of server-side processing; internal detectors are not billed as separate checks. A check that runs locally without server processing is not counted into the server volume. Capacity for files and heavier processing is set according to the actual use.
What does an SDK or API integration include?
The interfaces your application calls, the result it has to handle, the place where a decision is enforced, and the work on both sides. Before production we go through the scenarios: a normal request, a finding, a false finding and an outage.
How does a dedicated deployment work?
We agree the environment, the capacity, who administers it and who is responsible for what. The proposal names the components that run in your environment, their updates and any external dependencies.