On-premises appliance
Place management, evidence, and approved processing inside a customer-controlled environment.
DEPLOYMENT & DATA CONTROL
Deploy where your security data needs to stay.
Design CERYNZA around your environment, data residency, operating model, availability requirements, and permitted AI processing boundary.
DEPLOYMENT OPTIONS
Choose the operating model that fits the boundary.
Availability depends on product edition and validated architecture. Confirm the exact topology before making a deployment commitment.
Private cloud
Design deployment around the customer cloud boundary, identity, networking, and data residency controls.
Virtual appliance
Use virtualized infrastructure where sizing, storage, availability, and operational ownership are defined.
Hybrid deployment
Distribute sensors and collectors while retaining a documented management and evidence path.
CUSTOMER ENVIRONMENT
Make every data path explicit.
The architecture brief should show collection, storage, AI processing, management, response connectors, and trust boundaries.
ARCHITECTURE QUESTIONS
Questions to answer before a pilot.
Do not hide deployment constraints behind “flexible architecture.” Put the answer in the validation document.
Does any log or evidence leave the organization?
Where does AI inference run?
Is customer data used to train a shared model?
Can retention and deletion be configured?
What is supported in an air-gapped environment?
How are MSSP tenants isolated?
What are the HA and disaster-recovery objectives?
How are upgrades signed, staged, and rolled back?
VALIDATION OUTPUT
Leave the architecture review with evidence.
TECHNICAL VALIDATION
Design the deployment before moving the data.
Review your telemetry sources, residency requirements, AI boundary, resilience objectives, and response controls with the CERYNZA team.