Deployment Options for Partners

Cloud-Hosted (Cyviz Managed)

The cloud-hosted deployment model is the simplest path to getting customers live on Project Green. In this model, Cyviz operates and manages the entire backend infrastructure, including the Monitoring Server, Easy Server, telemetry pipeline, and web dashboard. The customer's on-site agents communicate with the Cyviz cloud over standard HTTPS connections, and all data is stored in Cyviz-managed infrastructure hosted on leading cloud providers.

This model is ideal for customers who want to minimize their IT overhead and avoid the complexity of managing server infrastructure. It is also well-suited for organizations with distributed sites, since all locations report into a single cloud instance with no need for on-premises servers at each site. Partners benefit from faster time-to-value, since there is no infrastructure provisioning step -- once the agents are deployed at the customer's site, data begins flowing immediately.

From a commercial perspective, the cloud-hosted model operates on a subscription basis with per-device pricing. Partners receive their margin on the subscription and are not responsible for infrastructure costs or uptime. Cyviz provides a 99.9% uptime SLA on the cloud-hosted platform, backed by redundant infrastructure and automated failover.

Partners should note that some customers, particularly those in government, healthcare, or financial services, may have data residency or sovereignty requirements that affect their ability to use the cloud-hosted model. In these cases, discuss the available hosting regions with your partner manager, or consider the on-premises or partner-hosted models described below.

Partner-Hosted (Your Infrastructure)

The partner-hosted model allows you to run the Project Green backend on your own infrastructure, whether that is a public cloud account you manage (AWS, Azure, GCP) or a private data center. This model is designed for managed service providers and larger systems integrators who want full control over the deployment environment and the ability to offer monitoring as part of a broader managed services portfolio.

In this model, Cyviz provides the platform as a set of containerized services deployed via Helm charts on Kubernetes. The partner is responsible for provisioning and maintaining the Kubernetes cluster, database instances, and supporting infrastructure. Cyviz provides detailed deployment guides, reference architectures, and ongoing support to ensure that the environment meets performance and security standards.

The partner-hosted model offers several advantages. You control the data -- it lives in your infrastructure and never leaves your environment unless you configure it to. You can integrate the platform with your existing monitoring, alerting, and ticketing tools at the infrastructure level. And you can serve multiple customers from a single deployment using the platform's built-in multi-tenancy, which simplifies operations and improves margins as your customer base grows.

This model requires a higher level of technical capability than the cloud-hosted option. Partners pursuing the partner-hosted model must have at least two technically certified engineers and must complete the deployment certification program. Cyviz provides a dedicated onboarding engagement to assist with the initial setup and validation of the environment.

Licensing for the partner-hosted model is based on a platform fee plus per-device pricing. Partners set their own pricing to end customers, with the flexibility to bundle monitoring with other managed services.

On-Premises (Customer Site)

Some customers require that all monitoring data remain within their own network perimeter. The on-premises deployment model addresses this requirement by placing the entire Project Green stack -- agents, backend services, and dashboard -- on infrastructure located at the customer's site or in the customer's own data center.

The on-premises architecture mirrors the cloud-hosted topology but runs entirely within the customer's environment. The platform is delivered as a set of Docker containers or Helm charts, depending on whether the customer operates a container orchestration platform. For smaller deployments, a single-server Docker Compose configuration is available that can run on a modest virtual machine.

Partners play a critical role in on-premises deployments. You are typically responsible for the initial installation, configuration, and validation, as well as ongoing maintenance and updates. Cyviz provides update packages on a regular release cadence, and partners are responsible for scheduling and applying those updates in coordination with the customer. A dedicated support channel is available for partners to escalate issues encountered during on-premises deployments.

The on-premises model is most common in defense, government, financial services, and healthcare verticals where regulatory or policy requirements mandate local data storage. It is also used by large enterprises with existing infrastructure teams who prefer to manage all software internally. Partners should set clear expectations with customers about the operational responsibilities that come with an on-premises deployment, including infrastructure sizing, backup procedures, and update cadences.

Hybrid Models

In practice, many customer environments do not fit neatly into a single deployment model. The hybrid approach combines elements of cloud-hosted and on-premises deployments to accommodate complex requirements. For example, a customer might run agents and a local data cache on-premises for low-latency alerting, while forwarding aggregated telemetry data to a cloud-hosted instance for long-term analytics and cross-site reporting.

Another common hybrid pattern involves customers with multiple site types. Corporate headquarters and large campuses might use on-premises deployments for full local control, while smaller satellite offices use cloud-connected agents that report directly to a central cloud instance. The platform's multi-tier architecture supports this by allowing agents to communicate with either a local backend or the cloud backend, configurable per site.

Partners offering hybrid deployments should work closely with the customer's IT team and the Cyviz partner engineering team during the design phase. Key decisions include which data flows remain local versus cloud-bound, how authentication and user management are federated across environments, and how alerting and escalation policies are coordinated between local and central instances.

Hybrid deployments carry the most complexity from a support and maintenance perspective, so they are recommended only for partners at the Premium or Elite tier who have the technical depth to manage multi-environment configurations. Cyviz provides reference architectures for the most common hybrid patterns, which can significantly reduce design and deployment time.

Choosing the Right Model for Your Customer

Selecting the appropriate deployment model is one of the most important decisions in the sales and scoping process. The right choice depends on a combination of the customer's regulatory environment, IT maturity, budget, and operational preferences.

Start by assessing the customer's data handling requirements. If they have strict data residency or sovereignty mandates, on-premises or partner-hosted models are likely necessary. If they prioritize simplicity and speed to value, the cloud-hosted model is the best fit. If their requirements are mixed -- for example, local data for some sites and cloud analytics for others -- a hybrid model may be appropriate.

Next, evaluate the customer's IT capacity. Organizations with dedicated infrastructure teams and existing Kubernetes or Docker environments are well-positioned for on-premises or hybrid deployments. Organizations without that capability will benefit from cloud-hosted or partner-hosted options where the infrastructure burden is handled externally.

Finally, consider the commercial model. Cloud-hosted deployments have the lowest upfront cost and the most predictable pricing, which is attractive to customers who prefer operational expenditure over capital expenditure. On-premises deployments may involve higher initial setup costs but can be more cost-effective at scale for large organizations. Partner-hosted deployments give you the most flexibility to package monitoring with your other services and define your own pricing structure.

When in doubt, start the conversation with the cloud-hosted model as the default recommendation and explore alternatives only if the customer raises specific requirements that the cloud model cannot satisfy. This approach simplifies the sales cycle and gets customers to value faster.