Custom Hosting Terms

These Custom Hosting Terms apply only to Cyver Core Subscribers who choose either
Managed Hosting in Azure or an On-Prem deployment, where the Cyver Core application is hosted outside of Cyver’s default
Azure-hosted environment. By default, Cyver Core is hosted and operated within Cyver’s own Azure infrastructure. When a
Subscriber elects to host the application within infrastructure owned or controlled by the Subscriber—whether in the
Subscriber’s Azure cloud subscription or within an on-premises environment—these Custom Hosting Terms apply. Because the
application is operated in infrastructure controlled by the Subscriber, Cyver is unable to provide the same service,
availability, and security guarantees that apply to Cyver-hosted deployments under the standard Terms of Service,
Subscription Agreement, or Premium Service Level Agreement.

DEPLOYMENT SCOPE

Under these deployment models, the Cyver Core application is installed and maintained with Cyver’s involvement, but
operates within infrastructure that is owned and managed by the Subscriber. This includes deployments hosted in the
Subscriber’s Azure tenant as well as on-premises environments operated by the Subscriber.

RESPONSIBILITIES

Cyver Responsibilities Cyver remains responsible for the Cyver Core application itself, including maintaining the
application code and platform, delivering updates and bug fixes, and providing guidance related to capacity planning and
system requirements. Where technically feasible and access is provided, Cyver may perform application-level monitoring
and share relevant monitoring data with the Subscriber. Cyver’s responsibilities do not extend to operating or managing
the Subscriber’s infrastructure. For on-prem deployments, Cyver’s role is limited to providing support and guidance.
Infrastructure and platform operations remain under the Subscriber’s control. Subscriber Responsibilities For all
customer-managed and on-prem deployments, the Subscriber is responsible for:

• Ownership, operation, and management of the hosting environment
• Configuration, operation, and maintenance of infrastructure resources
• Network design, access controls, and identity and permission management
• System performance, availability, and uptime
• Provisioning, operation, and payment of all infrastructure resources
• Security and compliance obligations related to the hosting environment, including applicable policies, controls, and
  configurations

For on-prem deployments, the Subscriber additionally assumes full responsibility for:

• Infrastructure updates and ongoing maintenance
• Monitoring and uptime
• Day-to-day operational management of the environment

The Subscriber agrees to provide and maintain appropriate access to enable Cyver to perform installation, updates, and
maintenance activities. Cyver does not control the hosting environment and cannot guarantee outcomes that depend on
Subscriber-managed infrastructure.  

CHANGES TO PREMIUM SERVICE LEVEL AGREEMENT

Deploying Cyver Core in a Subscriber-managed environment changes how Cyver is able to deliver the Premium Service Level
Agreement. Application availability becomes the responsibility of the Subscriber, except where an outage is caused
directly by a defect in Cyver application code or platform components. SLA provisions related to hosting infrastructure,
availability, and data traffic do not apply under these deployment models, and certain SLA categories, including
Category 10, are not applicable.  

SECURITY AND COMPLIANCE

Cyver cannot independently maintain the security controls required for SOC 2 or similar frameworks when the application
is deployed within infrastructure managed by the Subscriber. Compliance outcomes in these scenarios depend on the
security posture, configuration, and operational practices of the Subscriber’s environment. The Subscriber is
responsible for security controls associated with infrastructure ownership, including physical and facility security,
network security and architecture, infrastructure hardening, vulnerability management, intrusion detection and
prevention, and third-party penetration testing. Cyver will continue to maintain application-level security controls and
internal security practices where access is provided and will align configurations with Cyver standards where feasible.
Overall compliance remains dependent on the Subscriber’s environment.

INFRASTRUCTURE AND RESOURCES

The Subscriber is responsible for providing, maintaining, and paying for all infrastructure resources required to
operate Cyver Core, including compute, storage, networking, and related services. Cyver may provide guidance on
infrastructure sizing and configuration, but does not assume responsibility for resource provisioning or associated
costs. If changes made by the Subscriber negatively impact the application, Cyver may offer assistance under a separate
professional services arrangement.

PRODUCT UPDATES AND ACCESS

Cyver remains responsible for maintaining the Cyver Core application, including updates and fixes. To support this, the
Subscriber agrees to provide appropriate access, including temporary elevated access for installation and a service
account with sufficient permissions to deliver updates and maintenance. If required access is not provided, Cyver may be
unable to deliver updates or support and will not be held responsible for resulting issues. For on-prem deployments,
access to updates, maintenance, and support for Cyver Core shall require an active subscription. In the event of
non-payment or termination, Cyver shall suspend updates, maintenance, and support in accordance with the applicable
Terms of Service.  

INTELLECTUAL PROPERTY AND CONFIDENTIALITY

All intellectual property rights in the Cyver Core application remain with Cyver. The Subscriber is not permitted to
inspect, modify, copy, or reverse-engineer Cyver code except to the limited extent strictly necessary to host and
operate the application, and only in accordance with Cyver’s documentation and guidance. Any unauthorized modification
of the code constitutes a violation of the Terms of Service and is undertaken at the Subscriber’s own risk. The
Subscriber is not permitted to inspect, modify, copy, or reverse-engineer Cyver code. This restriction does not apply to
standard configuration of deployment, environment variables, or infrastructure settings required to operate the
application, as documented by Cyver  

ACCEPTANCE OF TERMS

By choosing a customer-managed or on-prem deployment of Cyver Core, the Subscriber acknowledges and agrees to these
Custom Hosting Terms, which take precedence over any conflicting provisions in the standard Terms of Service,
Subscription Agreement, or Premium Service Level Agreement.