Editions
Editions and scope
Tiers differ by capacity: how many workers, how many controllers, which level of support and which services are included.
What separates the tiers
Lower tiers start with a single control plane and a limited number of workers. Higher tiers carry a larger cluster capacity, a redundant control plane, priority support, the white label option and custom plugin development for the institution. The daily scan allowance rises with the tier.
Features on the roadmap
Central sign-on with SAML and OIDC, directory synchronization, hierarchical organizations and multi-region deployment are on the roadmap and marked as such on the Roadmap page. A planned feature is not a delivery commitment, and a purchase decision should be made on the product as it stands today.
Why there is no price on the site
Cyprob is sold through partners, and the price depends on the scope of the installation, so your partner shares it with you. The structure of the tiers is set out here, and the figure is settled in the conversation.
Common questions
Is the scan engine different between tiers?
No. The engine is the same in every tier. Tiers differ in capacity and services: workers, controllers, daily scan allowance, support level, white label and custom plugin development.
Should roadmap features drive the purchase?
No. Planned features carry no delivery commitment. The decision should rest on what the product does today.
Where do we learn the price?
From your partner. Cyprob is sold through partners and pricing follows the scope of the deployment. The tier structure is public on this page; the number comes in the conversation.